cswork / libraryOpen practice workspace

Interview guides · ZURU

ZURU Software Engineer Interview Guide

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

The 60-second brief

A Software Engineer at ZURU is responsible for driving the technical innovation behind one of the world's fastest-growing consumer goods, robotics, and automation companies. Unlike traditional software companies, ZURU operates at the intersection of physical manufacturing, advanced automation, and high-performance digital platforms. Whether you are working on the sophisticated 3D design software of ZURU Tech, building high-throughput supply chain systems, or developing consumer-facing digital experiences, your code directly impacts physical products and global operations. The role demands a unique combination of core computer science fundamentals, low-level optimization skills, and a strong product-driven mindset. Engineers here do not just write code; they solve complex spatial, logical, and structural problems.

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

Focus areas

  • DSA (Data Structures & Algorithms)
  • Problem Solving
  • Aptitude Testing

The ZURU interview process

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

HR Touchpoint

Initial discussion with the HR team to align on your background, career goals, and cultural fit.

What to demonstrate

  • Initial discussion with the HR team to align on your background, career goals, and cultural fit
  • Depth in DSA (Data Structures & Algorithms)

How to prepare

  • Answer aloud and timed: Explain the difference between let, const, and var in JavaScript, and how hoisting affects them.
  • Answer aloud and timed: What is the difference between a pointer and a reference in C++, and when would you use each?

Automated Screening Tests

Completion of automated tests to assess core analytical and programming capabilities.

What to demonstrate

  • Completion of automated tests to assess core analytical and programming capabilities
  • Depth in DSA (Data Structures & Algorithms)

How to prepare

  • Answer aloud and timed: Explain the core concepts of Object-Oriented Programming (OOP) and how they are implemented in your language of choice.
  • Answer aloud and timed: How does memory allocation work in C++, and what are the best practices for preventing memory leaks?

Core Technical Evaluation

Interactive rounds focusing on your resume, live problem-solving, and scenario-based design.

What to demonstrate

  • Interactive rounds focusing on your resume, live problem-solving, and scenario-based design
  • Depth in DSA (Data Structures & Algorithms)

How to prepare

  • Answer aloud and timed: Explain the lifecycle of a component in modern front-end frameworks and how you optimize rendering performance.
  • Answer aloud and timed: How would you design a database schema for an e-commerce platform, and what indexing strategies would you use to optimize query performance?

Leadership Meeting

Final discussions with senior engineering leadership or founders to assess fit and passion.

What to demonstrate

  • Final discussions with senior engineering leadership or founders to assess fit and passion
  • Depth in DSA (Data Structures & Algorithms)

How to prepare

  • Answer aloud and timed: Explain the difference between an inner join, outer join, and self-join in DBMS, and provide a scenario where a self-join is necessary.
  • Answer aloud and timed: Write a program to reverse a linked list both iteratively and recursively, and explain the space and time complexity of both approaches.

Where candidates lose points

Master your resume

Every project listed on your resume is fair game. Be ready to explain the architecture, the technical challenges, and exactly why you chose one technology over another.

Do not embellish your resume

ZURU interviewers will drill deep into your past projects, and failing to explain the underlying technical details of a project you claimed to own is a major red flag.

Show your logical flow

When solving scenario-based questions, talk through your thought process out loud. Interviewers care more about how you structure your thoughts and handle edge cases than they do about perfect syntax.

Questions & practice

Explain the difference between let, const, and var in JavaScript, and how hoisting affects them.

Medium · Core Programming & Language Fundamentals

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?

What is the difference between a pointer and a reference in C++, and when would you use each?

Medium · Core Programming & Language Fundamentals

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?

Explain the core concepts of Object-Oriented Programming (OOP) and how they are implemented in your language o

Medium · Core Programming & Language Fundamentals

Explain the core concepts of Object-Oriented Programming (OOP) and how they are implemented in your language of choice.

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?

How does memory allocation work in C++, and what are the best practices for preventing memory leaks?

Medium · Core Programming & Language Fundamentals

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?

Explain the lifecycle of a component in modern front-end frameworks and how you optimize rendering performance

Medium · Core Programming & Language Fundamentals

Explain the lifecycle of a component in modern front-end frameworks and how you optimize rendering performance.

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 a program to reverse a linked list both iteratively and recursively, and explain the space and time comp

Medium · Data Structures, Algorithms & DBMS

Write a program to reverse a linked list both iteratively and recursively, and explain the space and time complexity of both approaches.

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?

What is a hash collision, and what are the common techniques used to resolve it?

Medium · Data Structures, Algorithms & DBMS

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?

How would you design a database schema for an e-commerce platform, and what indexing strategies would you use

Medium · Data Structures, Algorithms & DBMS

How would you design a database schema for an e-commerce platform, and what indexing strategies would you use to optimize query performance?

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?

Explain the difference between an inner join, outer join, and self-join in DBMS, and provide a scenario where

Medium · Data Structures, Algorithms & DBMS

Explain the difference between an inner join, outer join, and self-join in DBMS, and provide a scenario where a self-join is necessary.

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?

How would you design a system to track real-time inventory across multiple global warehouses?

Medium · Scenario-Based & System Design

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?

Describe a scenario where you had to refactor a poorly structured codebase. What was your approach, and how di

Medium · Scenario-Based & System Design

Describe a scenario where you had to refactor a poorly structured codebase. What was your approach, and how did you measure success?

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 would you structure a front-end application to ensure clean separation of concerns and optimal state manag

Medium · Scenario-Based & System Design

How would you structure a front-end application to ensure clean separation of concerns and optimal state management?

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 detect and resolve deadlocks in a multi-threaded database environment?

Medium · Data Structures, Algorithms & DBMS

Approach

  1. Establish what changed and when, before forming any theory.
  2. Pick a bisection that eliminates candidates whichever way it turns out.
  3. Check the instrumentation before believing the symptom.
  4. Separate the trigger from the cause; the deploy is rarely the bug.

Follow-up

  • What would you look at first, and what would it rule out?
  • How would you tell a cause from a coincidence here?

Suggested practice checklist

Built from the rounds and topics ZURU candidates report.

Day 1 — Map the ZURU loop

  • Write out the reported sequence: HR Touchpoint, Automated Screening Tests, Core Technical Evaluation, Leadership Meeting.
  • 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 4 reported rounds, with the weakest marked.

Day 2 — Work DSA (Data Structures & Algorithms)

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

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

Day 3 — Work Problem Solving

  • Spend the session on Problem Solving, which ZURU candidates report being tested on.
  • Write one worked example in Problem Solving and time yourself on it.

Deliverable: One timed worked example in Problem Solving.

Day 4 — Work Aptitude Testing

  • Spend the session on Aptitude Testing, which ZURU candidates report being tested on.
  • Write one worked example in Aptitude Testing and time yourself on it.

Deliverable: One timed worked example in Aptitude Testing.

Day 5 — Answer out loud: Core Programming & Language Fundamentals

  • Answer aloud, timed: Explain the difference between let, const, and var in JavaScript, and how hoisting affects them.
  • Answer aloud, timed: What is the difference between a pointer and a reference in C++, and when would you use each?

Deliverable: Spoken answers to 2 reported Core Programming & Language Fundamentals question(s), under time.

Day 6 — Answer out loud: Data Structures, Algorithms & DBMS

  • Answer aloud, timed: How would you design a database schema for an e-commerce platform, and what indexing strategies would you use to optimize query performance?
  • Answer aloud, timed: Explain the difference between an inner join, outer join, and self-join in DBMS, and provide a scenario where a self-join is necessary.

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

Day 7 — Answer out loud: Scenario-Based & System Design

  • Answer aloud, timed: Walk through the design and implementation of a complete program simulating an ATM machine. How do you handle concurrent transactions and state management?
  • Answer aloud, timed: How would you design a system to track real-time inventory across multiple global warehouses?

Deliverable: Spoken answers to 2 reported Scenario-Based & System Design question(s), under time.

Behavioural preparation

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

Walk through the design and implementation of a complete program simulating an ATM machine. How do you handle

Medium · Scenario-Based & System Design

Walk through the design and implementation of a complete program simulating an ATM machine. How do you handle concurrent transactions and state management?

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?

Reverse your own decision and price the reversal

Medium · reversibility · measurement · migrations

Describe a technical decision you made and later reversed. Pick one that cost something: a service you split and merged back, a cache you added and removed, an index you created that pushed the planner onto a worse plan, a projection you rebuilt from scratch. State what you believed when you decided, the measurement that changed your mind, how long the wrong version ran in production, and what the reversal cost in migrations, dual writes, and a deprecation window for callers you did not own.

Approach

  1. State the original rationale without irony, in the version you would still defend given what was known then. If it is not defensible, the story is about carelessness rather than judgement, and a different example serves you better.
  2. Give the measurement that moved with a before and after: the p99 that did not improve, the cache hit rate that sat at 40%, the plan that flipped to a sequential scan once the table passed a size you can name.
  3. Cost the reversal in steps, not adjectives: expand-and-contract deploys, the dual-write window, the callers who had to be notified, the rows already written in the wrong shape that had to be backfilled or abandoned.
  4. Distinguish reversal from rewrite by naming what you kept. Most good reversals preserve the schema or the interface and undo one decision inside it, which is also why they were affordable.

Follow-up

  • What in that decision was irreversible, and did you know it was irreversible when you made it?
  • How did you tell the people who had already built on top of the original decision?

Narrate an outage you owned from page to postmortem

Hard · incident response · blast radius · postmortems

Pick an incident you personally drove, ideally one where writes were affected rather than reads. In six to eight minutes: state the symptom as it first appeared on a dashboard, the blast radius you established before you knew the cause, the mitigation you applied and when, the mechanism you eventually proved, and the follow-up that would prevent a repeat. Bring numbers: error rate, tenants affected, minutes to mitigate, minutes to resolve. If you cannot name what you measured, choose a different incident.

Approach

  1. Open on the signal rather than the cause: which metric at which percentile moved, on which service, at what time, so the listener follows the same evidence you had rather than a conclusion you already reached.
  2. Separate mitigation from diagnosis out loud. State what you did to stop the bleeding (flag off, shed traffic, drain a lease, roll back a deploy) and say plainly that you did it before the mechanism was known, because those are two jobs with different deadlines.
  3. Establish blast radius in countable terms: how many tenants, how many writes, and crucially whether the effect was loss or only delay. An append-only revision table or a pending outbox row means the change survived and the projection was merely behind, which is a repair rather than a data-loss incident.
  4. Prove the mechanism instead of asserting it. Name the trace span that grew, the plan that flipped to a sequential scan, the lease that expired, plus one alternative you ruled out and the signal that stayed flat while you ruled it out.

Follow-up

  • What would you do differently in the first five minutes, given the same dashboard and no more information?
  • Which follow-up action did you deliberately not take, and why was dropping it the right call?