Zalando, headquartered in Berlin, is one of Europe's largest online fashion and lifestyle platforms. Its careers blog describes the software engineering interview in unusual detail, from the length of each round to the problem-solving method it recommends, which makes it one of the easier European loops to prepare for precisely. This page covers what Zalando builds and who it hires, the process candidates commonly report, the technical depth the teams care about, representative problem types, what interviewers score, and a three-week prep plan.
What Zalando builds and who it hires
Zalando's engineering blog covers its systems openly. It built Skipper, an open-source HTTP router and Kubernetes ingress controller that handles edge traffic, and in 2026 described adding client-side load balancing for internal fan-out traffic at about a million requests per second. It also built Nakadi, an event streaming platform used by hundreds of teams and now archived as an open-source project, publishes RESTful API and event guidelines, runs a Tech Radar for technology choices, and runs many PostgreSQL databases on Kubernetes.
- Back-end engineers: catalogue, checkout, logistics and partner services, often in Java, Kotlin or Scala.
- Front-end and mobile engineers: the shop, the app and internal tools.
- Data and machine learning engineers: recommendations, sizing and search.
- Platform engineers: Kubernetes, routing, databases and developer experience.
What the process tends to look like
| Stage | What happens | How to prepare |
|---|---|---|
| Talent acquisition call | About 30 minutes on your background, the role and the process | Read the engineering blog and the Tech Radar for your area |
| Technical screen | A one-hour live coding interview; some candidates first receive an online coding test, often reported on Codility | Practical coding in your interview language, explained aloud |
| Final loop | A system design and architecture interview and a general technical interview, each about an hour, plus a hiring manager conversation | One design in the company's domain and two strong behavioral stories |
Processes differ by team, level and office and change over time, so treat this as the common shape candidates report and confirm the specifics with your recruiter.
The five rounds Zalando describes
Coding interview. Zalando says you write code for sample problems in a live environment, then discuss structure, data structure choices and runtime and memory complexity. It recommends the REACTO method: repeat the problem, give examples, describe an approach, code it, test it and optimize.
System design and architecture. You get a short problem and design a system with several components. Zalando lists architecture, scalability, technology choices, resilience, operational excellence and security as what it looks at, so cover monitoring and failure, not just boxes.
General tech interview. Engineers from the team discuss your past projects, your role and what you learned, along with design patterns, operations and computer science fundamentals.
Timeline. Zalando says the process usually takes two to three weeks depending on availability, and can include an extra coding challenge or task for some roles.
Representative problem types
These are the kinds of problems candidates describe, not a leaked question list. Practice the category, not the exact question.
- Design the product catalogue and search for a fashion shop.
- Design a checkout that reserves stock without overselling during a sale.
- Route requests to services with retries and timeouts.
- Implement a sliding-window rate or count.
- Design event publishing between teams with schema changes over time.
- Explain how you would roll out a change safely across many services.
- Medium LeetCode-style problems, explained with complexity.
What interviewers score
- Working code: a solution that runs, handles edge cases and is readable by the next engineer.
- Practical judgment: the trade-offs you name and the simplest design that meets the requirement.
- Product sense: understanding who the user is and what failure looks like for them.
- Ownership: examples where you shipped, measured and fixed things yourself.
The behavioral side
Technical rounds decide most outcomes, but every Zalando loop also asks about how you work. Prepare a short story for each of these, with a result and what you learned:
- Something you shipped end to end. Cover the user problem, your decisions, what you measured and what you would change.
- A disagreement with a teammate. Show how you made the decision on evidence and kept the relationship.
- Why this company? Connect its product and engineering problems to the work you want to do next.
Structures and sample answers for the common questions are in our software engineer behavioral answers guide.
A three-week prep plan
- Week 1: practical coding: build small features against an API, parse and transform data, and write tests, in the language you will interview in.
- Week 2: system design for the company's domain, plus two behavioral stories about shipping and fixing something under pressure.
- Week 3: timed mixed problems, a mock interview every other day, and research into the product and its engineering blog.
For practice lists, use LeetCode company-tagged questions; compare the European style of Booking.com and Spotify; and for design rounds, read system design building blocks.
Where CoPilot Interview fits
Most of a Zalando loop is spoken: you explain an approach, defend a trade-off and talk through your past work. CoPilot Interview is an AI interview assistant whose free AI mock interview builds technical and behavioral questions from your résumé and the job description, reads them aloud and scores each spoken answer out of ten, so you can rehearse the explanation as well as the code. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Online assessments and many coding rounds forbid outside help, so practice beforehand and follow your employer's rules on the day.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
What programming language should I use in a Zalando interview?
Use your strongest language for coding rounds. Many Zalando back-end teams use Java, Kotlin or Scala, and the job description tells you what the team uses.
Does Zalando send an online assessment?
Zalando describes a live coding interview as the core step and says some roles add a coding challenge or task; candidates often report an online test on Codility before the live rounds. Ask your recruiter.
What is the REACTO method Zalando recommends?
It is a structure for coding interviews: Repeat the question in your own words, give Examples, describe your Approach, Code it, Test it against your examples and edge cases, then Optimize. It keeps you talking through your reasoning, which is what Zalando's coding round assesses.
How should I prepare for Zalando coding questions?
Practice practical problems under time limits, build small features against an API in your interview language, and prepare one system design in Zalando's domain. Explain every solution out loud, because follow-up questions about trade-offs matter as much as the first answer.
Can I use AI tools in a Zalando interview?
Only if the instructions you receive say so. Online assessments and live coding rounds generally forbid outside help, and some companies now state their AI policy in the invitation. Use AI to practice beforehand, and follow your employer's rules.
Practice this interview before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview