Delivery Hero, headquartered in Berlin, runs food and grocery delivery brands across Asia, Europe, Latin America and the Middle East, including Talabat, PedidosYa, HungerStation, Glovo and Baemin. Its engineering interviews follow the published shape of its hiring process, with coding and design questions that often come back to logistics: getting the right rider to the right restaurant at the right time. This page covers what Delivery Hero builds and who it hires, the process candidates commonly report, the technical depth the teams care about, representative problem types, what interviewers score, and a three-week prep plan.
What Delivery Hero builds and who it hires
Engineers build ordering and restaurant systems, quick-commerce stores and the logistics platform. A Berlin job posting describes a dispatch service that connects riders and vendors to millions of customers every day, and others list logistics teams working in Kotlin, Java and Go on routing and optimisation. An AWS case study describes Delivery Hero using Amazon EventBridge Scheduler to manage rider operations. Because the group runs several regional tech platforms, the stack and the loop can differ between brands.
- Back-end engineers: ordering, payments, vendor and logistics services in Go, Java, Kotlin or Python.
- Logistics and optimisation engineers: dispatch, routing and delivery-time estimates.
- Mobile engineers: customer, rider and vendor apps.
- Data and machine learning engineers: forecasting, ranking and pricing.
What the process tends to look like
| Stage | What happens | How to prepare |
|---|---|---|
| Talent acquisition call | 30 to 45 minutes on your background, motivation and the steps ahead | Ask which brand and platform the team works on |
| Technical screen | A technical assessment tied to the role; candidates commonly describe a 60-minute live coding round with an easy to medium problem | Practical coding in your interview language, explained aloud |
| Final loop | System design, often a delivery-shaped problem, plus hiring manager, collaboration and final interviews | One design in the company's domain and two strong behavioral stories |
Processes differ by team, level and office and change over time, so treat this as the common shape candidates report and confirm the specifics with your recruiter.
Logistics systems and the published process
The stages Delivery Hero publishes. Its careers site lists a talent acquisition call, a technical assessment, a hiring manager interview, a collaboration round of 45 to 90 minutes with day-to-day partners, and a final interview, usually over four to six weeks, with the order varying by team.
Dispatch and assignment. The core logistics problem is matching riders to orders as both move. Be ready to discuss batching orders, when to notify a rider relative to food readiness, and what to do when an assignment goes wrong.
Estimates and time. Delivery-time estimates combine restaurant preparation, rider travel and waiting. A good answer separates the components, explains how you would measure error and how the estimate updates during delivery.
Back-end fundamentals. Candidates also describe questions on APIs, databases and concurrency in their main language, so revise transactions, indexing and safe concurrent updates.
Representative problem types
These are the kinds of problems candidates describe, not a leaked question list. Practice the category, not the exact question.
- Design a simple online food delivery system end to end.
- Assign riders to orders to minimise lateness.
- Estimate delivery time and update it as the order progresses.
- Track rider locations and find the nearest available riders.
- Design order status updates for customer, rider and restaurant apps.
- Handle a restaurant that rejects an order after payment.
- Easy to medium array, hash map and heap problems.
What interviewers score
- Working code: a solution that runs, handles edge cases and is readable by the next engineer.
- Practical judgment: the trade-offs you name and the simplest design that meets the requirement.
- Product sense: understanding who the user is and what failure looks like for them.
- Ownership: examples where you shipped, measured and fixed things yourself.
The behavioral side
Technical rounds decide most outcomes, but every Delivery Hero loop also asks about how you work. Prepare a short story for each of these, with a result and what you learned:
- Something you shipped end to end. Cover the user problem, your decisions, what you measured and what you would change.
- A disagreement with a teammate. Show how you made the decision on evidence and kept the relationship.
- Why this company? Connect its product and engineering problems to the work you want to do next.
Structures and sample answers for the common questions are in our software engineer behavioral answers guide.
A three-week prep plan
- Week 1: practical coding: build small features against an API, parse and transform data, and write tests, in the language you will interview in.
- Week 2: system design for the company's domain, plus two behavioral stories about shipping and fixing something under pressure.
- Week 3: timed mixed problems, a mock interview every other day, and research into the product and its engineering blog.
For practice lists, use LeetCode company-tagged questions; compare the European style of Booking.com and Spotify; and for design rounds, read system design building blocks.
Where CoPilot Interview fits
Most of a Delivery Hero loop is spoken: you explain an approach, defend a trade-off and talk through your past work. CoPilot Interview is an AI interview assistant whose free AI mock interview builds technical and behavioral questions from your résumé and the job description, reads them aloud and scores each spoken answer out of ten, so you can rehearse the explanation as well as the code. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Online assessments and many coding rounds forbid outside help, so practice beforehand and follow your employer's rules on the day.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
What programming language should I use in a Delivery Hero interview?
Use your strongest mainstream language. Logistics and back-end teams commonly use Go, Java, Kotlin or Python; the job description tells you which.
Does Delivery Hero send an online assessment?
Delivery Hero describes a technical assessment that reflects the role, with expectations and time estimates shared in advance. Depending on the team that can be a live coding round or a task, so ask your recruiter.
What are Delivery Hero's leadership principles used for in interviews?
Delivery Hero says it hires for craft excellence and for its leadership principles, so the hiring manager, collaboration and final rounds look for behaviour that matches them. Read the principles on its careers site and prepare one story for each that fits your experience.
How should I prepare for Delivery Hero coding questions?
Practice practical problems under time limits, build small features against an API in your interview language, and prepare one system design in Delivery Hero's domain. Explain every solution out loud, because follow-up questions about trade-offs matter as much as the first answer.
Can I use AI tools in a Delivery Hero interview?
Only if the instructions you receive say so. Online assessments and live coding rounds generally forbid outside help, and some companies now state their AI policy in the invitation. Use AI to practice beforehand, and follow your employer's rules.
Practice this interview before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview