Zalando Outlet Software Engineer interview typically runs 6 rounds: coding test, HR interview, hiring manager interview, three technical interviews, and a final HR interview. It usually takes several weeks and is notably long, with slow decision turnaround.
$48K
Avg. Base Comp
$82K
Avg. Total Comp
5-7
Typical Rounds
2-4 weeks
Process Length
Our candidates report that Zalando Outlet is less interested in puzzle-solving theatrics and more interested in whether you can operate across the full engineering stack. The recurring pattern is a mix of medium-difficulty coding, system design, and stack-specific fundamentals like OOP, Java, and SQL. Even when the coding task was described as straightforward, interviewers still wanted candidates to explain their reasoning clearly afterward, which tells us the bar is not just getting to the answer but showing solid engineering judgment.
We’ve also seen that the company leans heavily on broad technical conversation rather than narrow algorithm drills. Multiple candidates mentioned general technical discussions tied to their previous experience, plus questions about project work and how they think through design tradeoffs. That means the strongest signal here is practical depth: being able to connect past work to the role and speak comfortably about the technologies you’ve actually used, not just recite patterns from prep materials.
A second theme is process discipline. Candidates consistently described the experience as structured and organized, but also drawn out, with long waits between steps and decisions. That combination suggests Zalando Outlet is careful about fit and technical consistency, and our candidates who did best were the ones who came across as steady, clear, and credible in conversation rather than overly polished or overly optimized for one type of round.
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 Outlet process.
I had to wait about two weeks for a rejection even though the interviews themselves seemed to go fine, which honestly left a bad impression. The process started with an initial coding test, and if that passed it moved to an HR interview. After that came four technical interviews with senior managers and technical leads, and then there was another HR interview at the end just to share the outcome. It felt like a long process for a software engineering role, and the delay in getting a decision made it even more frustrating.
On the technical side, I was asked medium LeetCode-style coding questions, some system design, and a few general questions. The coding part was manageable if you’re used to interview prep, but it wasn’t just pure algorithms — they also wanted to see how you think about design and broader engineering topics. The overall vibe was more drawn out than difficult, but the waiting and the final rejection after all those rounds made the experience feel pretty poor. My takeaway would be to prepare for both coding and system design, and also be ready for a process that can stretch out longer than expected.
Prep tip from this candidate
Be ready for a long process: coding test first, then HR, then four technical rounds, then another HR closeout. Focus your prep on medium LeetCode problems plus system design, since both came up alongside general engineering questions.
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 Outlet
Strategically resolving misaligned expectations with stakeholders for a successful project outcome
| Question | |
|---|---|
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Random SQL Sample | |
| Closest SAT Scores | |
| P-value to a Layman | |
| Prime to N | |
| Upsell Transactions | |
| Monthly Customer Report | |
| 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 | |
| Top 3 Users | |
| Cyclic Detection |
Synthesized from candidate reports. Individual experiences may vary.
The process typically begins with a recruiter or HR-style call. This conversation covers your background, why you want to join Zalando Outlet, how you heard about the company, and salary expectations. In some cases, the recruiter also gives a high-level overview of the next steps.
Candidates are asked to complete a Codility-style coding assessment with multiple problems. The tasks are usually a mix of easy and medium difficulty, including straightforward coding and data structure questions such as linked list processing.
If the coding test is passed, the next step is often an HR interview. This stage is mostly behavioral and motivational, with discussion of your previous experience and general fit for the role.
Candidates then meet with the hiring manager for a deeper discussion of their background and prior work. This round includes behavioral questions and time for you to ask questions about the team and role.
The final stage consists of multiple technical interviews, often three or four separate rounds with senior managers and technical leads. These interviews cover medium-difficulty coding, system design, and stack-specific technical knowledge such as OOP, Java, SQL, and general engineering concepts.
Some candidates report a final HR conversation at the end of the process to communicate the outcome. This appears to be a closing step rather than an additional evaluation round.