Delivery Hero interview, decoded.

Updated · Sources at the end

Delivery Hero hires engineers through a published five-stage process that ends with a bar raiser: a senior engineer or manager from a different part of the company, there to hold every hire to the same standard. Before that come a recruiter call, a coding interview the company describes as closer to pair programming than an exam, a system design round with a senior engineer from the team, and a hiring manager conversation. The company says the whole process usually takes four to six weeks.

Delivery Hero is based in Berlin and runs local food and grocery delivery brands in about 70 countries, including foodpanda, Glovo, talabat, PedidosYa, foodora and Baemin. In July 2026 Uber offered to buy it for €41.50 a share, and the boards recommended the offer in September; Uber has committed to keep the Berlin headquarters and make no changes to the Berlin workforce until at least 2029, and expects the deal to close in the second half of 2027.

Free · 2 minutes · no account

The questions for your exact Delivery Hero role and level.

See the questions Delivery Hero asks ↓Run a free mock interview →

Interviewing at Delivery Hero? Below are the questions candidates report. For the ones your exact role and level will get, paste the posting. Your first mock is free.

01

Who Delivery Hero hires

This guide follows the software engineer path at the Berlin headquarters, from graduates to senior engineers and engineering managers. Backend roles lean on Go and Python, with mobile, data and machine learning teams alongside. Graduates join a tech graduate program in Berlin and are expected in the Mitte office at least twice a week. The same stages apply across engineering roles; the technical content follows the team.

02

What is the Delivery Hero interview process?

Delivery Hero publishes its process on its careers site, and its tech blog adds detail for engineers. The company says it usually takes four to six weeks from application to offer, and that engineering interviews run by video within a two-to-three-week window. The details below mark what the company says and what candidates report.

01
Talent acquisition call
30–45 minutes, video

An introductory conversation about your background, your motivation and what you are looking for next. Be ready to say which team or domain you want, since the loop is run by the team you applied to.

02
Coding interview
Live, with engineers from the team

The company describes it as closer to pair programming than to an exam, and advises not rushing into code: describe the problem and your plan out loud first. Candidates report practical problems in their own language, and a 2026 account describes Python fundamentals, APIs and concurrency in the technical rounds.

03
System design
With a senior, staff or principal engineer

Design questions set in the business: ordering, rider assignment, location data and payments at the scale of dozens of markets. Candidates report questions on APIs, databases and concurrency tied to real engineering scenarios.

04
Hiring manager
30–60 minutes

Your potential manager goes through your experience in detail. The company also lists a collaboration stage of 45 to 90 minutes with the partners you would work with daily, on communication and working style.

05
Bar raiser
Final interview, video

A senior engineer or manager from a different part of the organisation, so hires meet the same standard across Delivery Hero. Reported topics go deep: memory management, database internals and optimising services under heavy load.

06
Offer
Through your recruiter

Your recruiter takes you through the offer and a start date.

03

Delivery Hero system design: questions set in food delivery

The problems its interviewers work on

The system design round is run by a senior, staff or principal engineer from the team you applied to, and the problems come from the business: many local brands on shared platforms, in dozens of countries, at lunchtime and dinnertime peaks. Candidates report questions tied to real engineering scenarios rather than abstract puzzles.

  • Order placement and tracking: Design the path from checkout to delivered: the order service, restaurant confirmation, courier assignment and live status. Say where you need strong consistency (payment, assignment) and where eventual is fine (tracking).
  • Courier assignment: Match orders to nearby couriers: indexing locations, keeping one active assignment per courier, and handling a courier who goes offline. Name the trade-off between the fastest match and the fairest one.
  • One platform, many brands: Delivery Hero runs local brands across about 70 countries. Say how you would share one platform while each market keeps its own menus, payments and rules.
  • Peak load: Plan for lunchtime spikes: caching menus, queueing writes, and degrading gracefully when a downstream service slows down.

Delivery Hero's tech blog describes its own architecture work; reading a few posts gives you the vocabulary its interviewers use.

04

What Delivery Hero screens for

The careers site says what it wants from candidates in a few plain lines, and they shape how to answer.

  • How you think over memorised answers: the company says it cares more about your reasoning than a recalled solution
  • Honesty about gaps: it says it is not looking for perfection, and asks candidates to say when they do not know something
  • Talking through the problem before coding, which its tech blog gives as the first piece of advice
  • Working well with the people around you, the subject of its collaboration stage
  • The same bar across a large group: the bar raiser exists to hold every team to it
05

Delivery Hero interview questions

Candidate-reported themes

Candidates have reported the themes of the technical rounds rather than full questions, and Delivery Hero does not publish its questions. The practice set below follows those reports and the company's own description of each stage.

Behavioural & motivation

  • Tell me about a system you owned that had to keep working under heavy load.Listening forA real system · What went wrong · The result
  • Describe a time you disagreed with a partner team about a technical decision.Listening forWhat was at stake · How they worked it out · The outcome
  • Why Delivery Hero, and why now?Listening forSpecificity · Connection · Research

Technical

  • Practice: implement a rate limiter that allows each restaurant at most N order updates per minute, talking through your plan first.Coding as pair programmingA practical problem worked through with an engineer, explained before codedListening forPlan first · Working code · Pairs well
  • Practice: two couriers accept the same order at the same moment. How do you make sure only one gets it?Backend fundamentalsAPIs, databases and concurrency, reported in 2026 technical roundsListening forSees the race · A sound fix · Failure cases
  • Practice: a service's p99 latency doubles at lunchtime peak. Walk through how you find the cause.Deep dive for the bar raiserReported topics: memory management, database internals, services under heavy loadListening forA method · Real depth · Fix and prevent

These are the reported themes — your loop is role-specific. Paste the actual posting and Calibrd predicts the questions for that exact role and level.

Predict my Delivery Hero questions →
06

Pay

IC1 · Levels.fyi, Berlin€63.6K median
IC3 · Levels.fyi, Berlin€108K median
IC4 · Levels.fyi, Berlin€137K median

Levels.fyi puts the median software engineer total pay in the Berlin area at €117K, from about €63K at IC1 to €166K at IC5 (read 29 September 2026). Packages combine base salary, a bonus and shares. The Uber offer of €41.50 a share in cash is pending until at least the end of the acceptance period on 5 November 2026 and closing in the second half of 2027, so ask how existing share grants would be treated. Calibrd benchmarks an offer against your level and location in the report.

07

How to prepare for a Delivery Hero interview

  1. Talk before you code. The company's first piece of advice for the coding round is to describe the problem and your plan out loud.
  2. Practise one delivery system design end to end: order, restaurant, courier assignment and tracking.
  3. Prepare for depth in the bar raiser: memory, database internals and services under load, beyond your team's own stack.
  4. Say when you don't know. The careers site says it is not looking for perfection and asks for honesty.
  5. Ask about the Uber deal: which brand and market your team serves, and how the takeover changes its roadmap and your share grant.
  6. Plan for Berlin. Graduates are expected in the Mitte office at least twice a week; ask your recruiter what applies to your team.

This guide covers Delivery Hero's engineering and research hiring. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

Also interviewing at Vinted, Allegro or Criteo? Their guides follow the same format, from the first screen to the offer.

Knowing the questions isn’t the same as answering them out loud. Run a Delivery Hero mock: spoken answers, coached on the spot. Your first mock is free.

Run a Delivery Hero mock →
08

FAQ & sources

What is Delivery Hero's interview process?

Delivery Hero publishes its process on its careers site, and its tech blog adds detail for engineers. The stages, in order: Talent acquisition call; Coding interview; System design; Hiring manager; Bar raiser; Offer.

What does Delivery Hero look for in candidates?

The careers site says what it wants from candidates in a few plain lines, and they shape how to answer. How you think over memorised answers; Honesty about gaps; Talking through the problem before coding, which its tech blog gives as the first piece of advice; Working well with the people around you, the subject of its collaboration stage.

What questions does Delivery Hero ask in interviews?

Candidates have reported the themes of the technical rounds rather than full questions, and Delivery Hero does not publish its questions. Technical themes: Coding as pair programming; Backend fundamentals; Deep dive for the bar raiser.

What system design questions does Delivery Hero ask?

The system design round is run by a senior, staff or principal engineer from the team you applied to, and the problems come from the business: many local brands on shared platforms, in dozens of countries, at lunchtime and dinnertime peaks. Candidates report questions tied to real engineering scenarios rather than abstract puzzles. Covered on this page: Order placement and tracking; Courier assignment; One platform, many brands; Peak load.

How do I prepare for a Delivery Hero interview?

Talk before you code. The company's first piece of advice for the coding round is to describe the problem and your plan out loud. Practise one delivery system design end to end: order, restaurant, courier assignment and tracking.

Prep for a real Delivery Hero role

Practise your Delivery Hero interview, out loud.

Paste a real Delivery Hero posting and Calibrd predicts the questions for that role and level, benchmarks the pay, and flags the gaps an interviewer will probe in your CV — then listens to your spoken answers and coaches them. Your first mock is free.

Free to start · No card · Encrypted at rest, never used to train AI, remove anytime

Two weeks out?

Email me the Delivery Hero prep checklist

The round that decides it, the questions they ask, and what to do before, in one email. Nothing else unless you sign up.

Delivery Hero Interview: Bar Raiser, Coding, Pay — Calibrd