Easy zalando interview-process

How do you answer "Why Zalando?"

The 30 second answer

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.

Reported. "Why Zalando?" is named on How We Hire and appears in candidate reports. A 2022 report also mentions "why Germany" and "why Berlin" in a later HR round.

Template. One sentence each:

  1. The pull: what Zalando does that you want to work on. Example: "Search at Zalando has to work across many markets and languages, with near-real-time price and stock and peak events such as Cyber Week."
  2. The fit: the closest thing you have already done. Example: "I have built event-driven ingestion and search features, and I care about p99 latency under load."
  3. The growth: what you want to learn there. Example: "I want to go deeper into retrieval and relevance at that scale."

Make it specific. Use public material and say where it comes from: the job ad, the engineering blog, or a talk. For a search role, Zalando's posts on its Elasticsearch 8 migration, its December 2025 self-inflicted query overload and its MICES 2026 talk on search architecture are good anchors. Present them as things you read, not things you worked on.

Avoid. Generic praise ("a great company"), only the city, only the salary, or anything that sounds like any job would do.

Sources (5)
  1. Zalando Jobs: How We Hire
  2. LeetCode Discuss: Zalando C6 Backend Engineer, Berlin (candidate report, May 2022)
  3. Zalando Engineering: Migrating From Elasticsearch 7.17 to Elasticsearch 8.x (November 2023)
  4. Zalando Engineering: The Day Our Own Queries DoS'ed Us: Inside Zalando Search (December 2025)
  5. MICES 2026: Zalando Search: Architecture Behind Product Discovery (video)