Zalando hires Software Engineers; this guide collects what candidates report about the process.
Recruiter Screening Call
reportedInitial call with a recruiter to assess your background and fit for the role.
What to demonstrate
- Initial call with a recruiter to assess your background and fit for the role
- Depth in System Design
How to prepare
- Be able to walk your CV end to end in two minutes, and say why this company specifically.
- Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.
Online Coding Assessment
reportedComplete a coding assessment, typically via Codility or similar platforms.
What to demonstrate
- Complete a coding assessment, typically via Codility or similar platforms
- Depth in System Design
How to prepare
- Answer aloud and timed: Write a function to compare two application version strings.
- Answer aloud and timed: Discuss the time and space complexity of your chosen data structure for a caching problem.
Technical Rounds
reportedParticipate in a series of technical interviews, including live coding and system design.
What to demonstrate
- Participate in a series of technical interviews
- Including live coding and system design
How to prepare
- Answer aloud and timed: Refactor a provided codebase for better readability and implement missing test cases.
- Answer aloud and timed: Design an inventory management system for a high-traffic e-commerce platform.
General Technical Knowledge Interview
reportedAnswer questions related to your technical knowledge and experience.
What to demonstrate
- Answer questions related to your technical knowledge and experience
- Depth in System Design
How to prepare
- Answer aloud and timed: Explain how you would design a system to collect and process metrics in a Kubernetes environment.
- Answer aloud and timed: Describe the architecture of a payment system, focusing on consistency and reliability.
Meeting with Hiring Manager
reportedFinal discussion with the hiring manager to evaluate your fit for the team.
What to demonstrate
- Final discussion with the hiring manager to evaluate your fit for the team
- Depth in System Design
How to prepare
- Prepare two projects you led end to end, each with the decision you owned and what it cost.
- Have three questions about the team's roadmap and how success is measured in the first six months.
2 candidate reports. Individual accounts describe a particular role and hiring cycle.
Zalando Software Engineer interview: technical depth, system design, and manager debrief
After a recruiter screen, I had an HR call about my experience, salary expectations, and a detailed explanation of the process and interviewers. I then had several technical rounds in a structured but flexible sequence: general technical depth, system design, and behavioral or managerial evaluation. Each technical round lasted about an hour. The questions tied closely to work I had described, inc…
Read full experienceZalando Software Engineer Interview Experience: Mismatch on level and pay
The process soured quickly. I went through complex rounds and was rejected for a mid-level role. To me, the expectations did not match what had been communicated: they seemed to want more experience while offering less pay. The interviewer interactions felt rude and unfriendly, which made it hard to stay motivated. I left upset, with the sense that the company was not acting in good faith about f…
Read full experiencePracHub editorial advice for the preparation topics above.
Ask Questions First
In system design, never start drawing until you have defined the scope. Ask about user volume, data storage requirements, and latency constraints.
Explain Your Trade-offs
There is rarely one "right" answer. If you choose a specific database or algorithm, explain why you chose it over the alternatives.
Focus on Clean Code
Even in a high-pressure live coding environment, prioritize writing readable, modular code. Use descriptive variable names and organize your logic clearly.
Be Honest About Your Stack
If you are asked about a language you haven't used in a while, be honest. Interviewers at Zalando value transparency and are often more interested in your problem-solving process than your rote knowledge of syntax.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Implement a binary search algorithm and explain its time complexity.
Implement a binary search algorithm and explain its time complexity.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- 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?
Solve a sliding window problem to optimize array traversal.
Solve a sliding window problem to optimize array traversal.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- 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 function to compare two application version strings.
Write a function to compare two application version strings.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- 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?
Discuss the time and space complexity of your chosen data structure for a caching problem.
Discuss the time and space complexity of your chosen data structure for a caching problem.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- 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?
Refactor a provided codebase for better readability and implement missing test cases.
Refactor a provided codebase for better readability and implement missing test cases.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- 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?
Walk through the design of a search feature: what are the trade-offs between latency and consistency?
Walk through the design of a search feature: what are the trade-offs between latency and consistency?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- 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 the role of immutability in code and its impact on testability.
Explain the role of immutability in code and its impact on testability.
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- 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 the update path that detects a concurrent edit
resource carries version INT NOT NULL DEFAULT 1. resource_revision holds revision_id, resource_id, version, actor_user_id, change_kind, patch JSONB, request_id, created_at with UNIQUE (resource_id, version). outbox_event holds aggregate_type, aggregate_id, aggregate_version, event_type, payload, status. A PUT carries the version the client read. Write the exact statements for the single transaction that applies the edit, records the revision and enqueues 'resource.updated', and give the handler's branch on zero affected rows. Then say what PostgreSQL 16 does under READ COMMITTED when two of these updates hit one row at once.
Approach
- One transaction, three writes, no network call inside it: UPDATE resource SET title = $3, version = version + 1, updated_at = now() WHERE resource_id = $1 AND tenant_id = $4 AND version = $2; then INSERT the resource_revision row at version $2 + 1; then INSERT the outbox_event row at the same aggregate_version. The event goes to a table rather than a broker because no transaction spans both.
- Branch on the affected-row count before doing anything else. Zero has three causes — stale version, wrong tenant, row gone — so re-read once and map to 409 carrying the current version, or 404 for an id outside the caller's tenant, which also stops the endpoint confirming that another tenant's id exists.
- State the engine behaviour instead of assuming it. Under READ COMMITTED the second UPDATE blocks on the row lock, and when the first commits PostgreSQL re-evaluates the WHERE clause against the newly committed row, so the version predicate now fails and the statement reports zero rows. Under REPEATABLE READ the identical collision raises SQLSTATE 40001 instead, so the handler must fold both shapes into one conflict response.
- Keep UNIQUE (resource_id, version) even though the predicate already serialises writers. It is what makes a lost update unwritable if any other path ever reaches the revision table, and it converts a logic bug into 23505 rather than into a silently missing history row.
Follow-up
- A client sends the version it read ten minutes ago and the resource has moved three versions. What is in your 409 so it can resolve the conflict without a full re-fetch?
- Two editors, two disjoint fields, no overlap. Does your answer still refuse the second write, and should it?
Hold a per-tenant active cap against concurrent creates
A tenant on the standard plan may hold at most 50 resources with status='active'. The create handler runs SELECT count(*) FROM resource WHERE tenant_id = $1 AND status = 'active', compares to 50, then inserts. Two creates arrive 3 ms apart on different instances and the tenant lands at 51. Name the anomaly, say whether PostgreSQL 16 READ COMMITTED or REPEATABLE READ prevents it and why, then give an implementation that holds the cap at READ COMMITTED with the exact statements. Finally, say what changes when the cap is 'at most one running export per tenant' on job_run.
Approach
- Name it: write skew. The two transactions read an overlapping set and write disjoint rows, so there is no row-level conflict for the engine to detect and each commit is individually legal.
- Rule out the levels precisely. READ COMMITTED takes a fresh snapshot per statement and takes no lock on the counted rows, so both see 49. PostgreSQL's REPEATABLE READ is snapshot isolation: it removes non-repeatable reads and phantoms within the snapshot but still admits write skew, because the anomaly is not a re-read of a changed row, it is a read of a set that a concurrent transaction invalidates. Only SERIALIZABLE closes it, by tracking the read dependency and aborting one transaction with SQLSTATE 40001 — a guarantee that exists only if the application re-runs the whole transaction from the read.
- Convert the set predicate into a single-row conflict: keep tenant.active_resource_count and run UPDATE tenant SET active_resource_count = active_resource_count + 1 WHERE tenant_id = $1 AND active_resource_count < 50 in the same transaction as the INSERT. Zero affected rows is the cap, returned as 409. The row lock serialises the decision at any isolation level, and contention is bounded to one tenant's row — which is also the fair-scheduling unit, unlike a global counter that would convoy every tenant behind one row.
- State the cost you just took on: a counter is a second source of truth that can drift, so every path that changes status must adjust it inside the same transaction, and a periodic reconciliation has to exist, with resource_revision as the authority for what the count should have been.
Follow-up
- A resource moves from archived back to active. Which statements change, and what breaks if the counter update and the status change land in different transactions?
- The cap becomes plan-dependent and a plan can change mid-month. Where does the number 50 live, and who reads it?
Design an inventory management system for a high-traffic e-commerce platform.
Design an inventory management system for a high-traffic e-commerce platform.
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- 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 design a system to collect and process metrics in a Kubernetes environment.
Explain how you would design a system to collect and process metrics in a Kubernetes environment.
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- 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 the architecture of a payment system, focusing on consistency and reliability.
Describe the architecture of a payment system, focusing on consistency and reliability.
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- 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 microservices-based system to handle millions of transactions?
How would you structure a microservices-based system to handle millions of transactions?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- 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 difference between an interface and an abstract class in Java or Kotlin.
Explain the difference between an interface and an abstract class in Java or Kotlin.
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Describe the principles of functional programming and how you apply them in your work.
Describe the principles of functional programming and how you apply them in your work.
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- 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 do you manage HTTP requests and status codes in a distributed architecture?
How do you manage HTTP requests and status codes in a distributed architecture?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- 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?
What are the common design patterns you use, and when should they be avoided?
What are the common design patterns you use, and when should they be avoided?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Read latency spikes on a sixty-second sawtooth
The cached listing read path serves about 14k reads/second at an 85% hit rate. p99 sits at 35 ms for 57 seconds, jumps to 900 ms for 3, and repeats. During each spike the primary shows several hundred identical listing queries starting within the same millisecond, all carrying one large tenant's id. Cache entries use a 60-second TTL. Give the mechanism, the ordered checks, the fix, and the correctness hazard your fix must not introduce.
Approach
- Match the period to a configured number before theorising about load. A spike every 60 seconds against a 60-second TTL is an entry expiring, and you confirm it by correlating spike timestamps with the entry's write time rather than with the traffic curve. If the period had matched a cron or a GC interval instead, this is a different investigation.
- Establish the concurrency of the miss. Several hundred identical queries in one millisecond means the miss path has no coalescing: every request that arrives between expiry and repopulation recomputes. The herd size is that key's arrival rate times its recompute time, so at 1.2k reads/second for the hot key and a 250 ms recompute you expect about 300 concurrent misses, which matches what is observed.
- Add single-flight on the miss path so one caller per key recomputes under a short-lived lock while the rest wait for its result. Prefer stale-while-revalidate where the read tolerates it: return the expired value immediately and refresh asynchronously, which removes the latency spike rather than serialising it into a queue of waiters.
- De-synchronise the keys. Write TTLs with jitter, for example 60 seconds plus or minus 10%, so a deploy or a mass invalidation does not align every key on the same second and turn a per-key herd into a fleet-wide one.
Follow-up
- The same sawtooth appears on a key that is invalidated on write rather than expired. Is that the same bug?
- How does your answer change if the recompute takes 4 seconds instead of 250 ms?
Built from the rounds and topics Zalando candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Zalando loop
- Write out the reported sequence: Recruiter Screening Call, Online Coding Assessment, Technical Rounds, General Technical Knowledge Interview, Meeting with Hiring Manager.
- 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.
02Work System Design
- Spend the session on System Design, which Zalando 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.
03Work Live Coding
- Spend the session on Live Coding, which Zalando candidates report being tested on.
- Write one worked example in Live Coding and time yourself on it.
Deliverable: One timed worked example in Live Coding.
04Work Data Structures & Algorithms
- Spend the session on Data Structures & Algorithms, which Zalando candidates report being tested on.
- Write one worked example in Data Structures & Algorithms and time yourself on it.
Deliverable: One timed worked example in Data Structures & Algorithms.
05Answer out loud: Coding and Algorithms
- Answer aloud, timed: Implement a binary search algorithm and explain its time complexity.
- Answer aloud, timed: Solve a sliding window problem to optimize array traversal.
Deliverable: Spoken answers to 2 reported Coding and Algorithms question(s), under time.
06Answer out loud: System Design and Architecture
- Answer aloud, timed: Design an inventory management system for a high-traffic e-commerce platform.
- Answer aloud, timed: Explain how you would design a system to collect and process metrics in a Kubernetes environment.
Deliverable: Spoken answers to 2 reported System Design and Architecture question(s), under time.
07Answer out loud: General Technology and Domain Knowledge
- Answer aloud, timed: Explain the difference between an interface and an abstract class in Java or Kotlin.
- Answer aloud, timed: Describe the principles of functional programming and how you apply them in your work.
Deliverable: Spoken answers to 2 reported General Technology and Domain Knowledge question(s), under time.
Expand any day for tasks and deliverables. Your progress is saved on this device.
Behavioural rounds judge the decision you made and what it cost.
Describe a time you had a conflict with a manager or peer and how you resolved it.
Describe a time you had a conflict with a manager or peer and how you resolved it.
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- 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?
Why do you want to join Zalando specifically, and how does your experience align with our mission?
Why do you want to join Zalando specifically, and how does your experience align with our mission?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- 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?
Tell me about a project where you faced a significant technical failure. What did you learn?
Tell me about a project where you faced a significant technical failure. What did you learn?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- 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 approach mentoring junior engineers or influencing technical decisions in a team?
How do you approach mentoring junior engineers or influencing technical decisions in a team?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- 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?
- 01
Describe a time you had a conflict with a manager or peer and how you resolved it.
- 02
Why do you want to join Zalando specifically, and how does your experience align with our mission?
- 03
Tell me about a project where you faced a significant technical failure. What did you learn?
- 04
How do you approach mentoring junior engineers or influencing technical decisions in a team?
How difficult is the interview process?
Candidates generally describe the difficulty as average to high. The technical depth is significant, but the process is structured to be fair if you are well-prepared in algorithms and system design.
Zalando Software Engineer candidate reports ↗How much time should I spend preparing?
Given the technical rigors, most successful candidates spend several weeks preparing. Focus on solving a variety of LeetCode-style problems and brushing up on system design principles specifically for distributed architectures.
Zalando Software Engineer candidate reports ↗What is the most common reason for rejection?
Often, candidates fail due to a lack of communication during system design (making assumptions instead of asking questions) or an inability to explain the time complexity of their code.
Zalando Software Engineer candidate reports ↗Is the feedback process reliable?
Feedback can be inconsistent. While some candidates receive detailed insights, others experience delays. Stay proactive by following up with your recruiter, but don't let a delay discourage you from continuing your search.
Zalando Software Engineer candidate reports ↗What topics does Zalando test in interviews?
Zalando interviews most often cover Problem Solving, System Design, Stakeholder Communication, SQL, and Python. The exact emphasis depends on the specific role you apply for.
Zalando Software Engineer candidate reports ↗Sources & methodology 3 sources ↗
Official role evidence, timestamped platform data and clearly labeled preparation advice.
- 01Zalando Software Engineer candidate reports ↗
Company-reported rounds, questions and FAQ.
candidate · Accessed 2026-09-22 - 02PracHub Software Engineer practice ↗
PracHub practice material, not company-reported.
platform · Accessed 2026-09-22 - 03PracHub preparation framework ↗
PracHub preparation guidance.
platform · Accessed 2026-09-22
Explore related engineering environments and compare the preparation focus.
XYZ Software Engineer Interview Guide
What XYZ asks Software Engineer candidates, from reported rounds and questions.
Xebia Software Engineer Interview Guide
What Xebia asks Software Engineer candidates, from reported rounds and questions.
Voya Financial Software Engineer Interview Guide
What Voya Financial asks Software Engineer candidates, from reported rounds and questions.
Volvo Trucks Software Engineer Interview Guide
What Volvo Trucks asks Software Engineer candidates, from reported rounds and questions.