Zalando interview process and recruiter screen 10 questions in 3 chapters

Zalando's own post lists five stages: a call with a talent acquisition partner, a hiring-manager interview, then coding, system design and general tech interviews of about an hour each. It says the process usually takes two to three weeks and varies by team. Candidates also report an online coding test for some roles and a bar raiser from another team.

Coding is usually described as LeetCode medium rather than hard, with discussion of complexity and trade-offs once the code works. System design prompts reported publicly are classic ones such as payments, inventory, booking, a URL shortener or a crawler, plus REST API contracts. No public report describes a search-specific design question. The repeated lesson is to ask about scale before designing.

It is a short, mostly non-technical call with a talent acquisition partner: your background and motivation, why Zalando, what you expect from the role, salary expectations and logistics, then the next steps. Prepare a ninety-second introduction, one project story with a measurable result, a specific reason for Zalando, a researched salary range, and a few questions about the process.

Give a reason only Zalando can satisfy, not a reason any company in the city satisfies. Connect one public fact about the team's problems, such as search at large scale across many markets, to what you have done and what you want to learn next. Keep it to three sentences, and avoid salary, location or visa as the main reason, even if they matter.

Use present, past, future in about ninety seconds. Present: your current role and the problems you own. Past: one or two earlier roles with one concrete, honest result each. Future: why this role is the logical next step. End by inviting a question rather than continuing. Strengths should be shown by those examples, not listed as adjectives.

Pick a project with real stakes where you made the key decisions. Use STAR, but spend most of the time on the actions: the options you weighed, why you chose one, and what went wrong. Close with a measured result and what you would change. Keep it under two minutes on a recruiter call and offer to go deeper with the engineers.

Research the market for the level first, then ask which level and band the role is planned at. If they still want a number, give a researched range for base salary, say you are flexible on the mix with bonus, equity and relocation support, and ask what the total package includes. Never quote a number you would be unhappy to receive.

Answer logistics in one clear sentence each. Say where you are based, whether you need relocation or a work permit, and your realistic start date including any notice period. Ask how Zalando supports relocation. Its How We Hire page says People Services helps with visa and accommodation after the contract is signed. Mention the working language you use and any you are learning.

The hiring manager wants to know how you approach new projects, collaborate across teams, and handle wins and setbacks, and How We Hire says they also review how you match Zalando's values. Those values are the Founding Mindset: customer focus, entrepreneurial mindset, speed and empowerment. Prepare one story for each, with a real decision and its outcome.

Ask what you need to plan the next stages. Which rounds follow, in what order and how long? Is there an online coding test, and which languages are allowed? Which level is the role planned at? Who is the hiring manager, and what does success look like in the first months? What relocation support is offered? One or two questions about the team's current challenges show interest.