Delivery Hero logo

Delivery Hero Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 117 interview experiences · FREE TO READ

3.2 Rounds average
Average Typical difficulty
49.6% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Delivery Hero.

Showing 3 of 117
Delivery Hero logo
Delivery Hero

Principal Software Engineer

Engineering · nearly a year ago

Staff Difficult Positive experience Accept offer 5 rounds
Interview process
Technical screen Technical screen Background check Technical screen
Interview formats
System Design Behavioral Coding

It was a thorough and pretty open process, the interviewers were good and competent, they really represented the company and the kind of people who work here. I had 2 system design interviews where we talked about redesigning and monitoring distributed systems for GDPR PII compliance, especially the right to forget, and one interview that was a standard culture fit, focusing on action, response, and outcome. There was also a coding interview, and a fifth one that I can't recall.

Confirmed questions1 question
  • Design and monitor a distributed system for GDPR PII compliance, focusing on the 'right to forget' implementation, particularly when some parts of the system are in semi-autonomous subsidiaries.
Delivery Hero logo
Delivery Hero

Senior Software Engineer

Engineering · nearly a year ago

Senior Average Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen Technical screen Onsite Onsite Onsite Onsite Background check Offer
Interview formats
Technical Coding System Design Behavioral

It was a pretty standard process: first, an HR call (30 minutes). Then, a technical interview with a very easy coding problem (60 minutes). After that, a System Design interview (60 minutes). Following that, a Behavioral interview (60 minutes). Lastly, a 'Bar raiser' interview (60 minutes - think Amazon's Bar raiser concept). The initial interview was quite straightforward, with common technical questions and approaches. The coding problem was extremely light, and we had plenty of extra time for more discussion. I'm not great at system design, and I think I spent too much time on the initial problem definition, leaving little time to go into design specifics. This led to my rejection after waiting over a week, even though I tried to follow best practices like understanding the problem, considering constraints, asking questions, listening to feedback, defining APIs, and drawing diagrams. The biggest issue was the complete lack of feedback, which really soured the experience for me.

Confirmed questions2 questions
  • Solve the Two Sum problem.
  • Could you design a middleware system to connect our supply chain service with various third-party WMS?
Delivery Hero logo
Delivery Hero

Software Engineer

Engineering · nearly a year ago

Mid Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Technical Coding Behavioral System Design

Applied online, got a call after 15 days for HR screening. The interview process involved three 1-hour rounds. The first was a Technical Round: 30 mins for a LeetCode medium problem and 30 mins for technical questions about my experience and CV. Next was the Hiring Manager Round, which focused on projects, past experience, my contributions, and culture fit. Finally, the Bar Raiser Round, with an Engineering Manager from another team. It had 30 mins for problem-solving and 30 mins for real-time scenario-based technical questions.

Confirmed questions4 questions
  • A medium-level string manipulation problem was asked, where you are expected to provide an optimal solution and discuss the approach in detail.
  • Why do you want to join Delivery Hero?
  • Explain the project you are most proud of.

Delivery Hero Software Engineer Interview Questions

Quoted word for word from Delivery Hero interview reports.

How would you remove elements repeated 3+ times in an array without using extra space?

Read reports

Given a user input array and a database array, what should be returned for inserts/updates and removals? For instance, if userInput is [1,2,3] and database is [2,3], what is the output for { insertOrUpdate: [...], remove: [...] }?

Read reports

Write code for string reverse operation and insert a symbol after each word; it was easy.

Read reports

Can you explain how race conditions manifest in Go, and what methods exist to prevent them when goroutines are writing to the same map?

Read reports

Can you evaluate the variable at the end of a chain of nested arrow and normal JS functions?

Read report

Could you write a basic SQL query to match two fields from one table with two fields from another?

Read report

How would you return the correct change for a given currency amount in a supermarket setting?

Read report

In what scenarios would you opt for microservices over a monolith, and vice versa?

Read report

Design and monitor a distributed system for GDPR PII compliance, focusing on the 'right to forget' implementation, particularly when some parts of the system are in semi-autonomous subsidiaries.

Read report

Formats, difficulty and experience

Across all 117 Delivery Hero interview reports.

Interview formats

Technical 30.4%
Coding 27.2%
Behavioral 27.2%
System Design 11.5%
Presentation 1.6%

Interview difficulty

Easy 17.9%
Average 70.9%
Difficult 11.1%

Candidate experience

Negative 33.3%
Neutral 17.1%
Positive 49.6%