
Zalando Outlet Data Engineer interviews, as candidates describe them, combine a recruiter or hiring-manager screen with Codility-style Python, Spark and SQL tasks, plus live coding and Airflow or system questions.
$103K
Avg. Base Comp
$140K
Avg. Total Comp
2-6 rounds
Typical Rounds
2-4 weeks
Process Length
Four candidates describe Zalando Outlet data engineering interviews, and none of them received an offer. One withdrew. The reports differ in length and format, so treat them as examples rather than a fixed loop.
The most repeated element is hands-on technical screening. One candidate faced a 155-minute Codility test covering Python, Spark and SQL, with a reported 60% threshold. Another did live Codility problems with the hiring manager watching: one Python question and three SQL questions that leaned on window functions and multi-step aggregations. That candidate scored perfectly and was still rejected, so clear explanation while you code likely matters alongside correctness.
A third candidate described five interviews over about three weeks. They covered a hiring-manager screen, a technical round on data warehouses, PySpark, SQL and distributed processing, a stakeholder conversation, a general technical interview and a coding interview. That candidate also worked through designing an Airflow DAG. Behavioral questions included strengths, weaknesses and why Zalando.
One candidate was also asked about handling gigabytes of data with limited RAM and about terminal operations. Another, interviewing at senior level, was asked about database partitions in a scripted hiring-manager round and found the technical bar tied closely to Zalando's own tooling. One candidate felt the team wanted software-engineering strength alongside data skills. Practice SQL windows, PySpark, orchestration design and memory-conscious Python, and prepare concise answers about your motivations.
Synthesized from 4 candidate 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.
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
Design a secure, real-time, scalable portfolio management system with notifications and caching.
| Question | |
|---|---|
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Stakeholder Communication | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Rolling Bank Transactions | |
| Comments Histogram | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Experiment Validity | |
| Download Facts | |
| Customer Orders | |
| Average Quantity | |
| Random SQL Sample | |
| Manager Team Sizes | |
| Month Over Month | |
| Flight Records | |
| Prime to N | |
| Monthly Customer Report | |
| Paired Products | |
| Upsell Transactions | |
| Top 3 Users | |
| Fill None Values | |
| Recurring Character | |
| Longest Streak Users | |
| Address Schema | |
| Compute Deviation |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an opening call with HR or the hiring manager covering background, interest in the role and company, and some behavioral questions. One described it as a checklist-style skills conversation, another as a 20-30 minute getting-to-know-you call. Expect to explain why Zalando.
Candidates report a coding challenge on Codility. One describes a 155-minute test covering Python, Spark and SQL with a 60% pass threshold, and another passed an online code challenge before later rounds. Practice timed problems on that platform and aim well above the cutoff rather than just passing.
One candidate solved four live Codility questions, one in Python and three in SQL, with the hiring manager watching. The SQL needed window functions and multi-step aggregations. Another candidate reports a separate live coding round. Narrate your reasoning, since a perfect score did not guarantee progression.
Reported technical content includes data warehouses, PySpark, distributed processing, designing an Airflow DAG, terminal operations, system design and processing gigabytes of data with limited RAM. One candidate described the questions as experience-oriented rather than LeetCode-style. Formats may vary by level and team.
One candidate met the hiring manager's manager in a culture and fit conversation, and another described a hiring-manager round with a fixed list of questions, including database partitions. Candidates may also face strengths and weaknesses questions. Prepare thoughtful questions of your own, though one candidate felt there was little room for them.