Zalando Se Software Engineer interview typically runs 4-5 rounds: HR, coding challenge, technical deep dive, system design, and managerial/final technical. It usually takes a few days to a few weeks and is fairly structured but can feel impersonal.
$97K
Avg. Base Comp
$133K
Avg. Total Comp
4-6
Typical Rounds
2-4 weeks
Process Length
We’ve seen Zalando screen for engineers who can move comfortably between day-to-day implementation details and broader system thinking. Across candidate reports, the recurring signal is practical technical fluency: one person was pressed on Java project experience, performance requirements, and Kafka message ordering, while another was pushed immediately into TypeScript fundamentals, immutability, and live refactoring. That tells us the team is less interested in polished theory than in whether you can explain how your code behaves under real constraints and make sound tradeoffs on the spot.
A second pattern is that the company seems to care a lot about how you reason across the stack and across teams. Multiple candidates described architecture-heavy discussions, microservices concepts, and questions about how they’d interact with other groups, which suggests they’re looking for engineers who can operate beyond a single ticket or feature. We also noticed that behavioral evaluation is not treated as a formality: candidates who did best had concrete stories ready and could connect their past work to why they wanted Zalando. The non-obvious make-or-break factor here is clarity under pressure — several people noted that interviewers were not especially warm, and in one case the feedback was bluntly that only the final answer mattered. In other words, at Zalando, being right is important, but being precise, structured, and grounded in real engineering decisions matters just as much.
Synthetized from 3 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Zalando Se process.
The process felt pretty standard on paper, but in practice it was very impersonal and a bit frustrating. I started with an HR round, then moved into a coding challenge, followed by a technical deep dive where they went through the technologies I’d used and the working concepts behind microservices. After that there was a managerial round focused on company fit and behavioral questions. The whole thing was spread across a few rounds, and the interviews themselves were mostly generic rather than very role-specific.
The technical part was centered on practical engineering basics. I was asked about a Java project I had worked on, how I would ensure an application meets performance requirements, and how to make sure message order is preserved in Kafka. Nothing was especially exotic, but they did expect you to explain the concepts clearly and connect them to real work you’ve done. The coding test was part of the second round, and the overall difficulty was moderate rather than algorithm-heavy. What stood out most was the attitude of the interviewers: one of them joined late and seemed tired and unfocused, and another round felt very absent and uninterested. I never got a formal rejection and in another the feedback took about two weeks to come back after a basic questionnaire. I didn’t get an offer from this process, and the main takeaway for me was that you should be ready for straightforward Java, microservices, and Kafka questions, but also be prepared for a process that may feel slow and impersonal.
Prep tip from this candidate
Be ready to talk through a real Java project in detail, plus practical microservices topics like Kafka message ordering and application performance requirements. I’d also prepare for a coding test in the second round and keep your explanations concise, since the technical deep dive seemed to focus on clear working knowledge rather than tricky algorithms.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Zalando Se
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Top Three Salaries | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Closest SAT Scores | |
| Random SQL Sample | |
| Prime to N | |
| Upsell Transactions | |
| P-value to a Layman | |
| Monthly Customer Report | |
| Top 3 Users | |
| Address Schema | |
| Download Facts | |
| Permutation Palindrome | |
| Average Quantity | |
| Size of Joins | |
| Manager Team Sizes | |
| Month Over Month | |
| Get Top N Frequent Words | |
| Flight Records | |
| Paired Products | |
| Google Maps Improvement | |
| Cyclic Detection | |
| Fill None Values | |
| Type-ahead Search | |
| Longest Streak Users |
Synthesized from candidate reports. Individual experiences may vary.
The process often starts with an HR conversation about your background, motivation for applying, and why you want to join Zalando. In some cases this round is also used to set expectations for the rest of the process and may include basic fit questions.
Candidates then move into a technical round that can include a live coding exercise or a coding challenge. Reported topics include JavaScript-to-TypeScript refactoring, TypeScript fundamentals like types, interfaces, and generics, and practical coding concerns such as immutability and conditional updates.
This round focuses on the technologies you've used and the concepts behind them, especially core engineering basics. Interviewers asked about Java projects, performance requirements, microservices, and Kafka, including how to preserve message order.
Some candidates are asked to work through a system design problem by choosing between a couple of design options and explaining their approach. The discussion can become architecture-heavy and may include how you would interact with other teams.
A managerial interview follows in many processes and is centered on company fit and behavioral questions. Expect 'tell me about a time when...' prompts, motivation questions, and discussion of how you work with others.
The final round can be a broader technical discussion with engineers and may feel more intense than earlier stages. Candidates reported a mix of architectural questions and questions about cross-team collaboration, after which a decision is made.