cswork / libraryOpen practice workspace

Interview guides · XYZ

XYZ Software Engineer Interview Guide

XYZ Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

At XYZ, a Software Engineer is a foundational driver of technical innovation, directly responsible for building, scaling, and maintaining the core services that power our global platforms. Engineers here do not just write code; they design robust systems capable of handling high-throughput traffic, optimize cloud-native architectures, and deliver seamless user experiences. Whether you are working on backend microservices, modern frontend interfaces, or cloud infrastructure, your contributions will directly impact product reliability, performance, and overall business growth. The engineering culture at XYZ emphasizes collaboration, continuous learning, and clean code principles. You will work alongside cross-functional teams of product managers, designers, and system architects to solve complex technical challenges.

This guide is scoped to a Software Engineer candidate at XYZ.

Focus areas

  • Data Structures and Algorithms (DSA)
  • Coding / Programming Questions
  • System Design

The XYZ interview process

XYZ candidates report 5 rounds over 4-6 weeks. The stages below are what candidates describe, not a published process.

Online Assessment

Candidates begin with an online assessment to evaluate their technical skills.

What to demonstrate

  • Candidates begin with an online assessment to evaluate their technical skills
  • Depth in Data Structures and Algorithms (DSA)

How to prepare

  • Answer aloud and timed: Write a function to check if a given string is a palindrome.
  • Answer aloud and timed: Find the length of the longest substring without repeating characters in a string.

Telephonic Screening

A screening round conducted over the phone to discuss qualifications and fit.

What to demonstrate

  • A screening round conducted over the phone to discuss qualifications and fit
  • Depth in Data Structures and Algorithms (DSA)

How to prepare

  • Answer aloud and timed: Design and implement an efficient algorithm to detect cycles in a directed graph.
  • Answer aloud and timed: Given an array of integers, write a program to remove duplicates and find the maximum sum of a subarray.

Technical Rounds

Multiple rounds focusing on coding, system design, and core computer science fundamentals.

What to demonstrate

  • Multiple rounds focusing on coding, system design, and core computer science fundamentals
  • Depth in Data Structures and Algorithms (DSA)

How to prepare

  • Answer aloud and timed: Write a program to sort an array of alphabets or replace all vowels in a string with an asterisk (*).
  • Answer aloud and timed: Explain the four pillars of Object-Oriented Programming (OOP) and provide real-world examples of how they are applied.

Managerial Discussions

Discussions with managerial staff to assess team fit and collaboration skills.

What to demonstrate

  • Discussions with managerial staff to assess team fit and collaboration skills
  • Depth in Data Structures and Algorithms (DSA)

How to prepare

  • Answer aloud and timed: What is the difference between final, finally, and finalize keywords in Java?
  • Answer aloud and timed: Explain Java serialization and the significance of the transient keyword in memory management.

HR Round

Final round to discuss background, expectations, and cultural fit.

What to demonstrate

  • Final round to discuss background, expectations, and cultural fit
  • Depth in Data Structures and Algorithms (DSA)

How to prepare

  • Prepare three examples from your own work, each with a decision you made and an outcome you can quantify.
  • Re-read the description of the hr round above and write down what you would ask to confirm before it.

Where candidates lose points

Master your resume

Be ready to explain every project, tool, and methodology you have listed on your resume. Interviewers will deep dive into your design decisions and your specific contributions.

Think out loud

During coding and system design rounds, talk through your thought process. Interviewers care more about how you analyze and structure a problem than whether you get the syntax perfect on your first try.

Be honest

If you do not know the answer to a question or are unfamiliar with a technology, admit it. Interviewers appreciate honesty and a willingness to learn over a guessed or incorrect answer.

Questions & practice

Write a function to check if a given string is a palindrome.

Medium · Data Structures and Algorithms

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. State the target complexity and say which constraint rules the naive version out.

Follow-up

  • How does this change if the input no longer fits in memory?
  • What is the worst case, and how likely is it on real data?

Find the length of the longest substring without repeating characters in a string.

Medium · Data Structures and Algorithms

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. State the target complexity and say which constraint rules the naive version out.

Follow-up

  • How does this change if the input no longer fits in memory?
  • What is the worst case, and how likely is it on real data?

Given an array of integers, write a program to remove duplicates and find the maximum sum of a subarray.

Medium · Data Structures and Algorithms

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. State the target complexity and say which constraint rules the naive version out.

Follow-up

  • How does this change if the input no longer fits in memory?
  • What is the worst case, and how likely is it on real data?

Write a program to sort an array of alphabets or replace all vowels in a string with an asterisk (*).

Medium · Data Structures and Algorithms

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. State the target complexity and say which constraint rules the naive version out.

Follow-up

  • How does this change if the input no longer fits in memory?
  • What is the worst case, and how likely is it on real data?

Explain Java serialization and the significance of the transient keyword in memory management.

Medium · Core CS Fundamentals (OOP, DBMS, OS)

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. Distinguish a value from a reference to it, and say which one you handed out.

Follow-up

  • What happens if two callers reach this at the same time?
  • Where could this allocate more than you expect?

Write an SQL query utilizing an inner join to fetch matching records from two tables based on a specific scena

Medium · Core CS Fundamentals (OOP, DBMS, OS)

Write an SQL query utilizing an inner join to fetch matching records from two tables based on a specific scenario.

Approach

  1. Name the grain you start from and join outward from it.
  2. Check whether any join is one-to-many before aggregating, or the sums inflate.
  3. Say which index the query would use, and what makes it unusable.
  4. Handle the rows that do not match: that is usually the actual question.

Follow-up

  • How does the query change if that join becomes one-to-many?
  • What happens to this when the table is ten times larger?

Why do you want to join XYZ, and how do your career goals align with our company culture?

Medium · Behavioral & Teamwork

Approach

  1. Name the grain you start from and join outward from it.
  2. Check whether any join is one-to-many before aggregating, or the sums inflate.
  3. Say which index the query would use, and what makes it unusable.
  4. Handle the rows that do not match: that is usually the actual question.

Follow-up

  • How does the query change if that join becomes one-to-many?
  • What happens to this when the table is ten times larger?

Design and implement an efficient algorithm to detect cycles in a directed graph.

Medium · Data Structures and Algorithms

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

Explain the four pillars of Object-Oriented Programming (OOP) and provide real-world examples of how they are

Medium · Core CS Fundamentals (OOP, DBMS, OS)

Explain the four pillars of Object-Oriented Programming (OOP) and provide real-world examples of how they are applied.

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

What is the difference between final, finally, and finalize keywords in Java?

Medium · Core CS Fundamentals (OOP, DBMS, OS)

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

What are the core differences between Client-Side Rendering (CSR) and Server-Side Rendering (SSR), and when wo

Medium · Core CS Fundamentals (OOP, DBMS, OS)

What are the core differences between Client-Side Rendering (CSR) and Server-Side Rendering (SSR), and when would you use each?

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

How would you design a system that scales to support hundreds of thousands of users across the globe? What are

Medium · System Design & Cloud Architecture

How would you design a system that scales to support hundreds of thousands of users across the globe? What are the key architectural trade-offs?

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

How do you optimize the performance and cost of AWS Lambda functions?

Medium · System Design & Cloud Architecture

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

Explain how you would manage state and API integration in a complex React application to avoid prop drilling.

Medium · System Design & Cloud Architecture

Approach

  1. Say who the caller is and what they do when the call fails halfway.
  2. Define the identity of a request so a retry cannot double-apply it.
  3. Separate accepted, pending, failed and confirmed; they are different facts.
  4. Design the error taxonomy before the success shape; callers branch on it.

Follow-up

  • What happens if the caller retries after a timeout?
  • How does a client discover it is on an old version of this contract?

Walk through the request flow of a secure, scalable REST API and explain how you would handle resource allocat

Medium · System Design & Cloud Architecture

Walk through the request flow of a secure, scalable REST API and explain how you would handle resource allocation.

Approach

  1. Say who the caller is and what they do when the call fails halfway.
  2. Define the identity of a request so a retry cannot double-apply it.
  3. Separate accepted, pending, failed and confirmed; they are different facts.
  4. Design the error taxonomy before the success shape; callers branch on it.

Follow-up

  • What happens if the caller retries after a timeout?
  • How does a client discover it is on an old version of this contract?

Listing latency scales with page size, not with filters

Easy · n+1 · latency · query batching

The tenant listing endpoint reads resource filtered by tenant_id and status, ordered by updated_at DESC, and returns each row plus the owner's display name from app_user and the actor of that resource's latest resource_revision. p99 is 55 ms at 10 rows per page and 1.4 s at 200. Database telemetry shows 401 statements per request, each under 1 ms, and nothing in the slow-query log. Diagnose the cause and give the fix, stating the statement count per request and the p99 you expect afterwards.

Approach

  1. Read the counters before forming a theory. 401 statements for 200 rows is one driver query plus two per row, and sub-millisecond execution with an empty slow-query log rules out a bad plan. The time is round trips, which is why it is invisible in every per-query metric and scales with rows returned rather than with filter selectivity.
  2. Name the two per-row statements from their normalised text: a single-row app_user lookup by user_id, and a resource_revision lookup by resource_id ordered by version DESC LIMIT 1. Confirm by dropping those two response fields and watching the statement count fall to one. That locates the calls in the serialisation layer, not the repository.
  3. Check that the arithmetic accounts for the whole gap. Measure one round trip to the replica in isolation; 400 trips at roughly 3 ms of network plus 0.2 ms of execution is about 1.3 s on top of a 55 ms baseline, which matches. If the multiplication had fallen short, the N+1 would only be part of the story and you would keep looking.
  4. Batch both lookups. Collect owner_user_ids and resource_ids from the driver query, then issue WHERE tenant_id = $1 AND user_id = ANY($2) for the users, and PostgreSQL's SELECT DISTINCT ON (resource_id) ... WHERE resource_id = ANY($2) ORDER BY resource_id, version DESC for the latest revision, which the UNIQUE (resource_id, version) index serves directly. On an engine without DISTINCT ON, use a lateral join or a row_number window. Three statements per request at any page size.

Follow-up

  • The page size is capped at 200 today. What breaks first if it is raised to 2,000, and is it still this bug?
  • How do you stop the next N+1 from reaching production, given that no individual query is slow and the endpoint's tests pass?

Suggested practice checklist

Built from the rounds and topics XYZ candidates report.

Day 1 — Map the XYZ loop

  • Write out the reported sequence: Online Assessment, Telephonic Screening, Technical Rounds, Managerial Discussions, HR Round.
  • For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.

Deliverable: A one-page map of the 5 reported rounds, with the weakest marked.

Day 2 — Work Data Structures and Algorithms (DSA)

  • Spend the session on Data Structures and Algorithms (DSA), which XYZ candidates report being tested on.
  • Write one worked example in Data Structures and Algorithms (DSA) and time yourself on it.

Deliverable: One timed worked example in Data Structures and Algorithms (DSA).

Day 3 — Work Coding / Programming Questions

  • Spend the session on Coding / Programming Questions, which XYZ candidates report being tested on.
  • Write one worked example in Coding / Programming Questions and time yourself on it.

Deliverable: One timed worked example in Coding / Programming Questions.

Day 4 — Work System Design

  • Spend the session on System Design, which XYZ candidates report being tested on.
  • Write one worked example in System Design and time yourself on it.

Deliverable: One timed worked example in System Design.

Day 5 — Answer out loud: Data Structures and Algorithms

  • Answer aloud, timed: Write a function to check if a given string is a palindrome.
  • Answer aloud, timed: Find the length of the longest substring without repeating characters in a string.

Deliverable: Spoken answers to 2 reported Data Structures and Algorithms question(s), under time.

Day 6 — Answer out loud: Core CS Fundamentals (OOP, DBMS, OS)

  • Answer aloud, timed: Explain the four pillars of Object-Oriented Programming (OOP) and provide real-world examples of how they are applied.
  • Answer aloud, timed: What is the difference between final, finally, and finalize keywords in Java?

Deliverable: Spoken answers to 2 reported Core CS Fundamentals (OOP, DBMS, OS) question(s), under time.

Day 7 — Answer out loud: System Design & Cloud Architecture

  • Answer aloud, timed: How would you design a system that scales to support hundreds of thousands of users across the globe? What are the key architectural trade-offs?
  • Answer aloud, timed: How do you optimize the performance and cost of AWS Lambda functions?

Deliverable: Spoken answers to 2 reported System Design & Cloud Architecture question(s), under time.

Behavioural preparation

Behavioural rounds judge the decision you made and what it cost.

Tell me about your development journey and your specific roles and responsibilities in your current or past pr

Medium · Behavioral & Teamwork

Tell me about your development journey and your specific roles and responsibilities in your current or past projects.

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

Describe a difficult phase or critical situation in a past project and how you resolved it using the STAR (Sit

Medium · Behavioral & Teamwork

Describe a difficult phase or critical situation in a past project and how you resolved it using the STAR (Situation, Task, Action, Result) method.

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

How do you handle work-life balance and manage competing priorities when working under tight deadlines?

Medium · Behavioral & Teamwork

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?