Delivery Hero software engineer candidates describe a staged loop: recruiter screen, coding, system design, hiring manager and often a bar raiser. Most reports end in rejection, and system design and backend depth come up most.
$108K
Avg. Base Comp
$130K
Avg. Total Comp
3-5 rounds
Typical Rounds
Not reported
Process Length
Candidates describe the Delivery Hero software engineer interview as a staged loop. Most open with a recruiter or HR conversation, then move through coding, system design, a hiring manager discussion and often a bar raiser round. Reported loops usually run from three to five rounds. One senior-track candidate instead had intro questions, Python fundamentals, three coding problems and a system design deep dive packed into a single one-hour interview. One candidate received a written process guide up front, which made the stages easier to anticipate.
Coding is usually described as easy to medium. Examples include finding the maximum element in an array, Two Sum, Jump Game and a LeetCode medium. One candidate took an online assessment with DSA questions before the live rounds.
System design is where outcomes often seem to turn. Reports include designing a simple online food delivery use case and scaling a service from 1k to 10k+ requests. That second prompt covered queues, autoscaling, Redis versus database caching, CDNs and PostgreSQL indexes. One rejected candidate felt system design was the deciding round, and another called it the hardest.
Backend depth recurs. Candidates mention:
Expect to explain your past projects and your own responsibilities in them.
Hiring manager and bar raiser conversations lean on collaboration, motivation and past work. One final round with a principal engineer turned into live coding instead. Most reported outcomes are rejections, often with little feedback.
Synthesized from 18 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 Delivery Hero process.
The process started with a recruiter screening call where they asked about my motivation for joining Delivery Hero, my background, and what the team was actually working on. It was conversational and helped me understand the role better before moving forward.
The engineering manager round was where things got technical. We spent time on behavioral questions and my work experience, then moved into two easy coding challenges. I remember working through the problems and explaining my approach as I coded. After that came the hiring manager interview, which felt heavier on behavioral and situational questions — they wanted to understand how I'd handled specific scenarios in past roles and how I'd approach technical decisions.
The bar raiser round was the most intense. It was rapid-fire from start to finish: quick technical questions testing my fundamentals, then two coding challenges that required solid algorithm knowledge. They asked about Python fundamentals, how I'd approach optimizing a slow API, how I review PRs, and how I handle disagreements on technical direction. There were also questions about deployment practices and what tools I'd used.
One of the second-round interviews involved a LeetCode-style problem — I had an hour to work through it, implement a solution, then discuss complexity and optimizations. I also had to debug and fix some Java code at one point, which tested whether I could read unfamiliar code quickly and spot issues.
What stood out was how much they cared about real-world engineering practices, not just algorithm speed. They wanted to know about my actual experience with deployments, code review philosophy, and how I work in teams. The interviewers were generally friendly and gave me space to think through problems. The whole process took several weeks from initial application to final rounds.
Prep tip from this candidate
Focus on LeetCode medium-level problems, especially string manipulation and array operations, since those came up across multiple rounds. But equally important: prepare concrete examples of how you've optimized APIs, reviewed code in teams, and handled deployment tooling — they ask these in depth and want real stories, not generic answers.
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 Delivery Hero
In which case would you use a bagging algorithm versus a boosting algorithm
| Question | |
|---|---|
| Relational Migration | |
| Clickstream Data | |
| Hurdles In Data Projects | |
| Target Indices | |
| Portfolio Platform Architecture | |
| Concurrent LLM Serving | |
| Slow SQL Query | |
| DDoS Attack Response | |
| Client Solution Pushback | |
| Finding the Maximum Number in a List | |
| Diagnosing Query Speed Degradation | |
| Testing Constraints | |
| Azure Kubernetes Infrastructure | |
| Why Do You Want to Work With Us | |
| Generative AI Privacy | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Longest Streak Users | |
| Rolling Bank Transactions | |
| Upsell Transactions | |
| Top 3 Users | |
| Random SQL Sample | |
| Customer Orders | |
| Prime to N |
Synthesized from candidate reports. Individual experiences may vary.
Candidates describe a recruiter or HR call first, covering background, work experience, the team and the role. One candidate first heard from the hiring manager and then received a written process guide laying out each step.
Coding rounds are described as easy to medium. Examples include finding the maximum element in an array, Two Sum, Jump Game and a LeetCode medium. One candidate took an online assessment with DSA questions first. Interviewers also asked about past projects and the experience on the candidate's CV.
Several candidates report a dedicated system design round. Topics include a simple online food delivery design and scaling a service from 1k to 10k+ requests with queues, caching and PostgreSQL indexes. Candidates mention requirements, trade-offs, performance and scalability as the themes.
Candidates describe a hiring manager round that leans toward collaboration, past work and team fit. In one report it also included a system design question and a LeetCode medium problem alongside the conversation.
Several candidates describe a final bar raiser round. One candidate's round mixed LeetCode, behavioral questions such as what motivates them, and some technical discussion. Another candidate's final round with a principal engineer turned into live coding.
