Deliveroo, the London-based food and grocery delivery company, has been owned by DoorDash since October 2, 2025 and still operates under its own brand. Its careers site publishes a detailed interview guide for backend and full-stack engineers, including a 90-minute HackerRank screen and an explicit ban on AI tools in every stage. This page covers what Deliveroo 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 Deliveroo builds and who it hires
Deliveroo's engineers build the consumer, rider and restaurant apps, the marketplace that matches orders to riders, and the logistics behind it. Its engineering blog describes migrating the Tier 1 dispatcher, the service that assigns riders to orders, from Ruby to Rust piece by piece; in one of its larger zones, dispatch time dropped from about four seconds to 0.8 seconds. The company started as a Ruby on Rails monolith with PostgreSQL and Redis, and job posts now list Go, Ruby, Python, Scala and Rust for backend work and Swift or Kotlin for mobile, with an internal server-driven UI framework called RooBlocks.
- Backend and full-stack engineers: ordering, payments, the marketplace and logistics services.
- Mobile engineers: consumer, rider and restaurant apps in Swift and Kotlin.
- Frontend engineers: web ordering and internal tools.
- Machine learning engineers: dispatch, delivery-time estimates, ranking and pricing.
What the process tends to look like
| Stage | What happens | How to prepare |
|---|---|---|
| HackerRank screen | Backend: 90 minutes, starting with 15 multiple-choice questions in 20 minutes on testing, system design, microservices, REST APIs and problem solving, then algorithms and a REST API coding task; sections cannot be revisited. Full-stack: a React challenge and a REST API task | A warm-up HackerRank task and timed practice in your strongest language |
| Coding interview | Either a take-home submitted at least 48 hours ahead, walked through and extended live with two or three small tasks, or a 50-minute live pair-coding session in HackerRank | Tests for happy and failure paths; narrate your thinking |
| Architecture interview | About 45 minutes designing a system from a product brief: requirements, scale, reliability, failure modes and trade-offs, sketched in a tool such as Excalidraw | One delivery-shaped design practiced aloud |
| Behavioural and team allocation | Questions on past challenges tied to Deliveroo's values; successful candidates are then allocated to teams | STAR stories on communication, leadership and decisions |
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 Deliveroo's published guide
No AI, anywhere. Deliveroo's guide says AI-generated take-home submissions are rejected and that live coding, the live extensions and the architecture interview must be done without tools such as ChatGPT or Copilot. It says the company uses AI tools extensively internally but wants to see your unaided performance.
Dispatch and the marketplace. The core problem is matching riders to orders as both move, while restaurants prepare food at different speeds. Be ready to discuss batching, re-assigning when a rider is delayed, and keeping the dispatcher fast as a zone grows. Our proximity service design covers finding nearby riders.
Sudden load. Candidates describe design questions about coping with sudden spikes, which fits a business with dinner-time peaks and promotions. Cover queueing, caching, autoscaling and protecting downstream services.
Practical APIs. Both the screen and the coding round include REST API work, so practice building and testing small endpoints quickly. Our HackerRank assessment guide explains the platform.
Representative problem types
These are the kinds of problems candidates describe, not a leaked question list. Practice the category, not the exact question.
- Build or extend a small REST API with validation and tests.
- Assign riders to orders to minimise lateness, then handle a rider dropping out.
- Design a voucher or promotion service that caps redemptions under heavy load.
- Estimate delivery time from preparation, travel and waiting, and update it live.
- Design order status updates for customer, rider and restaurant apps.
- Find the nearest available riders to a restaurant.
- Medium algorithm problems on arrays, hash maps, heaps and graphs.
What interviewers score
- Working, tested code: happy and failure paths covered in the screen and the coding round.
- Thinking out loud: clarifying questions and trade-offs explained, which Deliveroo's guide asks for directly.
- Design under real constraints: scale, reliability and failure modes worked out from a product brief.
- Values in action: behavioural answers with a clear situation, action and result.
The behavioral side
Technical rounds decide most outcomes, but every Deliveroo 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: HackerRank pace: three timed 90-minute practice sets that combine multiple-choice questions on testing, microservices and REST with an algorithm problem and a small REST API task. Our HackerRank assessment guide has the platform details.
- Week 2: the coding round: build a small REST service with tests for happy and failure paths, then have a friend add two requirements live while you narrate. Decide early whether you prefer the take-home or the live pair format.
- Week 3: architecture and behaviour: two delivery designs, dispatch and order status, each done aloud in 45 minutes, STAR stories tied to Deliveroo's values, and all practice without AI tools.
For practice lists, use LeetCode company-tagged questions; compare the parent company's loop at DoorDash and another delivery loop at Delivery Hero; and for design rounds, read system design building blocks.
Where CoPilot Interview fits
Most of a Deliveroo 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 Deliveroo interview?
Any mainstream language: Deliveroo describes its HackerRank problems as language agnostic, and the take-home runs in your own environment. Backend teams use Go, Ruby, Python, Scala and Rust, so any of those also fits the team.
Does Deliveroo send an online assessment?
Yes, for backend and full-stack roles: a 90-minute HackerRank screen described on Deliveroo's careers site, checked on November 12, 2026. Other roles follow their own guides; for Android, for example, the screen is a take-home challenge.
Has the DoorDash acquisition changed Deliveroo's interviews?
DoorDash completed the acquisition on October 2, 2025, and Deliveroo continues to operate under its own brand. As of November 12, 2026, Deliveroo's careers site still publishes its own interview guides, so follow the one for your role and confirm any changes with your recruiter.
How should I prepare for Deliveroo coding questions?
Follow Deliveroo's published guide: practice 90-minute HackerRank sets that mix multiple-choice questions and REST API coding, build and extend a small tested API, rehearse a 45-minute architecture design from a product brief, and prepare STAR stories tied to the company's values. Do all of it without AI tools, because every stage forbids them.
Can I use AI tools in a Deliveroo 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