Deliveroo Summary


Deliveroo is a technology company focused on marketing, selling and delivering restaurant meals to the household or office. Its technology platform optimizes food ordering and delivery by integrating web and mobile consumers with restaurant tablet-based point-of-sale order management terminals and logistics optimization algorithm via its delivery driver smartphone software.

HQLondon, GBMap
Employee Ratings
Overall CultureC-More


Deliveroo is headquartered in
London, United Kingdom

Location Map

Latest Updates

Company Growth (employees)

Employees (est.) (Apr 2022)8,200(+3%)
Job Openings452
Website Visits (Mar 2022)9 m(+3%)
Revenue (FY, 2020)£1.2 B(+54%)
Cybersecurity ratingAMore
Header placeholder lorem ipsum dolor sit amet, consectetur adipiscing elit.

Key People/Management at Deliveroo

Deliveroo Office Locations

Deliveroo has offices in London, Los Angeles, Balaclava, Brussel and in 8 other locations

Deliveroo Financials and Metrics

Summary Metrics

Founding Date


Deliveroo total Funding

$1.7 b

Deliveroo latest funding size

$180 m

Time since last funding

a year ago

Deliveroo investors

Index Ventures, Accel Partners, DST Global, T. Rowe Price, General Catalyst, Amazon, Fidelity, 14W, JamJar Investments, Hoxton Ventures, Hummingbird Ventures, Greenoaks Capital, Fidelity Management and Research Company, Felix Capital, Greg Marsh, Bridgepoint, Rancilio Cube, GR Capital, NGP Capital, H14, Entrée Capital, GC Capital, Greyhound Capital, Angel Capital Management, Future Fifty, Greenoaks, Arnaud Bertrand, Durable Capital

Deliveroo's latest funding round in January 2021 was reported to be $180 m. In total, Deliveroo has raised $1.7 b. Deliveroo's latest valuation is reported to be $800 m.

Deliveroo's revenue was reported to be £1.19 b in FY, 2020


Revenue (H1, 2021)£922.5 m
Gross profit (H1, 2021)£284.2 m
Net income (H1, 2021)(£108.7 m)
EBITDA (H1, 2021) (£88 m)
EBIT (H1, 2021) (£107.2 m)
Cash (30-Jun-2021)£1.63 b
EV $5.4 b

GBPFY, 2018FY, 2019FY, 2020
Revenue476.2 m771.8 m1.2 b
Cost of goods sold(369.1 m)(553.9 m)(799.4 m)
Gross profit108.2 m218.3 m395.4 m
R&D expense(12.8 m)(13.3 m)(16 m)
GBPH1, 2021
Revenue922.5 m
Cost of goods sold(639.5 m)
Gross profit284.2 m
R&D expense0
show all

GBPFY, 2018FY, 2019FY, 2020
Cash184.6 m229.8 m379.1 m
Accounts Receivable35.2 m44.8 m51.6 m
Prepaid Expenses10.6 m9.9 m25.7 m
Inventories7.2 m9.6 m8.2 m
GBPH1, 2021
Cash1.6 b
Accounts Receivable103.6 m
Prepaid Expenses0
Inventories14.5 m
show all

GBPFY, 2018FY, 2019FY, 2020
Net Income(257.1 m)(319.9 m)(221.1 m)
Depreciation and Amortization15.8 m29.3 m35.1 m
Accounts Receivable(27.4 m)(18 m)(28.9 m)
Inventories(2 m)(2.4 m)1.4 m
GBPH1, 2021
Net Income(107.2 m)
Depreciation and Amortization19.1 m
Accounts Receivable(13.3 m)
Inventories(6.3 m)
show all

H1, 2021
EV/EBITDA-61.4 x
EV/EBIT-50.4 x
EV/CFO40.3 x
Revenue/Employee151.3 k

Revenue Breakdown

Deliveroo revenue breakdown by business segment: 100.0% from ON-DEMAND FOOD DELIVERY PLATFORM

Deliveroo Operating Metrics

Deliveroo's Active Cities was reported to be 500 in May, 2019.

Apr, 2015Aug, 2016FY, 2016May, 2017Aug, 2017Sep, 2017Nov, 2017Feb, 2018May, 2018Jun, 2018May, 2019
Customers74 k
Drivers45020 k30 k35 k35 k60 k
Restaurants16 k25 k20 k25 k80 k
Active Cities84120140200268500

Deliveroo Acquisitions / Subsidiaries

Company NameDateDeal Size
CultivateJuly 31, 2019
MapleMay 08, 2017
Deliveroo Australia
Deliveroo Belgium SPRL
Deliveroo DMCC
Deliveroo France SAS
Deliveroo Germany GMBH
Deliveroo Hong Kong Limeted
Deliveroo Ireland Limeted
Deliveroo Italy SRL

Deliveroo Hiring Categories

Deliveroo Cybersecurity Score

Cybersecurity ratingPremium dataset



SecurityScorecard logo

Deliveroo Environment, Social & Governance (ESG) Ratings

CSRHub ESG ratingPremium dataset


out of 100

CSRHub logo

Deliveroo Website Traffic

Total Visits per monthSimilarWeb

Deliveroo Online and Social Media Presence

Twitter followers

74.43 k Twitter followers

6 Months

Deliveroo has 74.43 k Twitter Followers. The number of followers has increased 0.42% month over month and increased 1.04% quarter over quarter.

Deliveroo's Trends

Search term - Deliveroo

Twitter Engagement Stats for @deliveroo

  • 39.59 k


  • 249


  • 74.43 k


  • 373

    Tweets last 30 days

  • 5.8

    Avg. likes per Tweet

  • 34.9%

    Tweets with engagement

Deliveroo Technology StackBuildWith Logo

  • ads

    21 products used

    • Appcast
    • AppNexus
      • Atlas
      • Bizo
      • DoubleClick.Net
      • Facebook Custom Audiences
      • Google Floodlight Counter
      • Google Floodlight Sales
      • Google Remarketing
      • Impact
      • Index Exchange
      • LinkedIn Ads
      • Nanigans
      • Rubicon Project
      • SkimLinks
      • Snap Pixel
      • Tapad
      • The Trade Desk
      • Twitter Ads
      • Yahoo Small Business
  • analytics

    39 products used

    • Bing Universal Event Tracking
    • Bizo Insights
    • Branch
      • Braze
      • Dotomi
      • DoubleClick Floodlight
      • Dynatrace
      • Facebook Conversion Tracking
      • Facebook Domain Insights
      • Facebook Pixel
      • Facebook Signal
      • Fastly
      • Global Site Tag
      • Google AdWords Conversion
      • Google Analytics
      • Google Analytics 4
      • Google Analytics Classic
      • Google Analytics Ecommerce
      • Google Analytics Enhanced Ecommerce
      • Google Conversion Linker
      • Google Conversion Tracking
      • Google Universal Analytics
      • Hotjar
      • Hubspot
      • Kameleoon
      • LinkedIn Insights
      • Mixpanel
      • New Relic
      • Pardot
      • Rapleaf
      • Recruitics
      • Salesforce
      • Segment
      • TikTok Conversion Tracking Pixel
      • Twitter Analytics
      • Twitter Conversion Tracking
      • Twitter Website Universal Tag
      • Yahoo Dot
      • Yahoo Web Analytics
  • CDN

    14 products used

    • AJAX Libraries API
    • Amazon S3
    • BootstrapCDN
      • CDN JS
      • Cloudflare
      • CloudFront
      • Content Delivery Network
      • Facebook CDN
      • GStatic Google Static Content
      • jQuery CDN
      • Level3
      • Twitter CDN
      • Vimeo CDN
      • Yahoo Image CDN
  • cdns

    3 products used

    • Amazon CloudFront
    • Amazon S3 CDN
    • Fastly Verified CDN
Learn more on BuiltWith

Deliveroo Company CultureCultureAndCompensation Logo

  • Overall Culture



  • CEO Rating



  • Compensation



Learn more on Comparably

Deliveroo News and Updates

May 13, 2022
Food delivery firm Deliveroo to make India its development hub
_3xOCqLondon-based food delivery aggregator Deliveroo is planning to conduct pilots from India for 11 countries, including Australia and Singapore.
Apr 01, 2022
Europe Online Food Delivery Market Report 2022-2027 Featuring Deliveroo, Just Eat, Delivery Hero, Uber Eats, Dominos, Doordash
_3xOCqDublin, April 01, 2022 (GLOBE NEWSWIRE) -- The "Europe Online Food Delivery Market, Forecast 2022-2027, Industry Trends, Share, Insight, Growth, Impact of COVID-19, Company Analysis" report has been added to's offering. Europe Online Food Delivery Market is project to reach US$ 66.2 Billion by 2027
Mar 10, 2022
UK delivery startup Deliveroo is hiring up to 150 engineers in India
_3xOCqFood delivery startup Deliveroo is opening up an engineering office in Hyderabad, emulating other foreign firms like GoJek, Grab, and Rakuten.
Mar 06, 2022
DoorDash Considered Takeover of Deliveroo, Sunday Times Says
_3xOCqDoorDash Considered Takeover of Deliveroo, Sunday Times Says
Feb 18, 2022
Deliveroo, Just Eat and Uber Restrict London Delivery Amid Storm
_3xOCqFood delivery companies limited their services for several hours in London as Storm Eunice battered the U.K.
Jan 20, 2022
Deliveroo gross transaction value growth in 2021 comes in at top end of guidance
Deliveroo gross transaction value growth in 2021 comes in at top end of guidance

Deliveroo Blogs

May 03, 2022
1 Year @ Deliveroo as a Backend Engineer
Table of Contents Probation (first 3 months) Post-probation Going on-call Interviewing Leading a project What I’ve learned Everyone is willing to help Autonomy is a great thing It’s okay to fail Probation (first 3 months) My first week was an interesting one. This was the first new job I had started in this ‘new normal’ post-COVID-19 era. Being sent a work laptop by post and meeting my new colleagues virtually was a new experience. I logged in to find my calendar pre-populated with a myriad of training sessions across the first two weeks. I’ll admit, it was a little overwhelming. But it was reassuring to know that I was not the only one in this position. There were about 15-20 other people who had joined in the same week, each in varying positions in engineering, and many who had become familiar faces. The sessions ranged from engineering principles to designing systems at scale. I have to say, I was thoroughly impressed with the level of detail each training session had with comprehensive documentation to go with it. The latter part being a rare thing to see in an industry like ours, at least from my previous experience. Free time in-between training allowed me to learn Go. Coming from a Java background, the differences were not too huge. C-based languages largely read the same. Although I had to get my mind out of the Object-Oriented Programming paradigm mindset as Go has no such concept. Having ‘grown-up’ with Java since university, this was a big pill to swallow. But, as the kids say, ‘we move’. I didn’t waste time meeting my new team in the Consumer org. My new joiner buddy messaged me on Slack on my first day to introduce himself and the team. He was very helpful to get me settled in. He explained how our focus was to move our menus out of our monolith application into a microservice to allow for easier management and faster loading times. Despite the team having this goal, everyone seemed to work autonomously. Even though I had joined 3 months into the project with most of the groundwork already complete, we still had the freedom to do what we felt needed to be done. Post-probation I think this is where the real challenge began. After my probationary period, you’re expected to start taking on more responsibility. Going on-call This is something I was dreading. This was the first time I had to do anything like this in a job. Having seen from a distance how this has been done in other jobs, I figured it would be stressful. Thankfully Deliveroo has a process to ease engineers into the on-call rota. It starts with a training session (one when you join and another after probation to refresh your memory), shadowing (you follow and observe someone else on-call), reverse-shadowing (someone observes you), then you start on your own. I had to skip the shadowing part as the on-call schedule was quite tight. Thankfully my reverse-shadow shift didn’t go too badly. I was paged a handful of times (if that) and everyone else on shift was very helpful too. Up to this point, I had only worked on one service, so overseeing 6 other services I had never even touched or heard of before was quite daunting. But if you’re an experienced enough engineer, you’ll know the basic tools to look at when investigating an issue. On-call documentation (we call these Playbooks), DataDog logs, and other engineers are all the things you’ll need when looking into problems. Eventually some internal team changes led to me setting up a new, smaller rota specifically for the menus service. This meant my team only had to manage 1 service rather than 7, which has made a big difference. I feel that this change allowed my team to own the health of the service more than before. We know the ins and outs of the service which allows us to diagnose problems and also create solutions far quicker. Interviewing Now this is something I’m still getting to grips with. This was also another task I was anxious about doing. I had never interviewed anyone for a role until joining Deliveroo. What if I assess the candidate incorrectly? What if I gave the candidate a bad experience? These were the kind of questions that were running through my head. But at the same time, I was excited to finally be on the other side of the table (or screen). But I’m sure you’ve guessed by now that, like going on-call, there is a process to get you started. A 2-hour in-depth training session is done to go through what is expected of you as an interviewer and what you should be doing and thinking. Then, you shadow another engineer and reverse-shadow afterwards. I like to think of these as having two engineers interviewing a candidate rather than having one interviewer and another watching. Admittedly, during my own interview process I found the architecture portion challenging. But having been on the other side, I’ve come to understand how I could have done better. There is no one right answer. There are many ways to approach and solve a problem. One of the main things we look for is how you are conveying the solution to the problem as well as the solution itself. Leading a project This was something I was really looking forward to. One of the things that attracted me to work at Deliveroo was career development. Having the opportunity to move closer to a senior engineering position, I knew that performing senior responsibilities would include taking the lead in projects. Towards the end of 2021, I worked on a new promotion to entice consumers to order groceries on our platform. This involved scoping out what needed to be done, diving into services I had never worked on before and learning more about the business domain (mainly how we calculate fees for the basket at checkout and how we advertise promotions and offers in the restaurant list). Thankfully the teams who worked on these respective areas were more than happy to offer help and advise on the best approach which made the job much easier. I definitely learned time management in this project. I had a number of different tasks to do. Writing technical design documents, hosting weekly sync meetings, helping other engineers understand and work through issues they had found. It was very involved and challenging as I had to be on top of everything. Juggling that and other personal commitments, I pulled through. What I’ve learned Everyone is willing to help There are two core values that Deliveroo holds. We succeed as a team & we never say it’s not my job. These values could not be any more accurate. We have a plethora of Slack channels to ask any kind of questions you may have. From how the restaurant list works to how you pronounce the word “scone” (yes, seriously!). Even when you’re looking through code in a repository you’ve never seen or come across before, I’ve found that there will always be someone willing to help in any way possible. Whether that be sending code snippets or having a full-on deep dive session. Autonomy is a great thing One aspect I probably admire the most is having the autonomy to do what you want. Now yes, your team may have their goals and priorities. But if you want to experiment with a new feature you are free to start a discussion on how to do so. If you want to try out a new Go library because you think it’ll help write code quicker, you are free to do so. If you want to set daily Slack alerts to remind your team of planned calendar events for the day, you are free to do so! It’s okay to fail This is something I have to keep reminding myself on a regular basis. And in fact, this is probably one of my life mantras. It is okay to fail. This is how we grow. In the project I worked on to create a new grocery promotion towards the end of 2021, we managed to go live by the end of the year. But there were many many setbacks along the way. But that was okay. I knew at the time that whatever went wrong during the project I’d do everything in my power to make sure it doesn’t happen again for future projects I work on. We love to run experiments here and sometimes they don’t work out the way we expect them to. But again, that’s okay. We reflect on our findings, take learnings from them and move forward. This is the kind of attitude every person should have in any function they work in. This is how we evolve to be a better version of ourselves. I can say for sure that I’ve surpassed my own expectations in the last year.
Feb 09, 2022
Like many others, I’ve just re-joined Deliveroo. Here’s why.
The grass just wasn’t greener. There really is no guarantee that a new role will be a better fit than your last one. When you’re interviewing, both yourself and the company are trying to make a big decision based on very limited information. Some of these things you’ll likely be assessing are both difficult to gauge and incredibly important, like, say, company culture or your relationship with your manager. There’s always a chance you’ll make the wrong call, and this’ll be even more true the more you liked your previous role as the bar will be even higher. For me, I had really enjoyed my two and half years at Deliveroo, but now it was the height of the second national lockdown and I was feeling a little uninspired. I was craving some novelty: the opportunity to solve new problems with new people in a new industry really appealed. So I made the jump. But you can guess the outcome: I just wasn’t happier. I’ve changed and have learnt more about what’s important to me. I once moved to a garden-flat because I really wanted outdoor space, only to realise that my previous top-floor flat was wonderfully private and serene, and it turns out that that was much more important to my happiness than the garden was. I’m sure you’ve had similar experiences! We’re really not great at seeing all of the things that contribute to how well we’ll fit into a place - many of them are intangible and so subtle we’ll take them for granted and only notice them when they’re gone. This is the same with where we work too. When I left Deliveroo, I was looking for a couple of specific things Deliveroo couldn’t offer: I wanted to try out fin-tech, and I wanted to move to a smaller company where I could dabble in management without fully relinquishing being an individual contributor (at Deliveroo, you have to choose a specific development track). A few months into my new role, I realised that I was less interested in both fin-tech and management than I expected. On top of that, I realised what was most important for my happiness and growth: a kind, friendly culture as well as a broad and challenging range of potential problems to solve. Deliveroo has both of these in droves - I had just taken them for granted at the time! We’re all still learning, and it’s likely that we’ll continuously update what’s important to us as we progress through our careers. Deliveroo had changed too, and I was really excited about where they were going. It wasn’t just me doing the changing. In the year since I had left, Deliveroo had done so too. Here’s just a few of the changes that I was really excited about. Firstly, they launched Deliveroo Hop, an on-demand grocery service. If you’ve used something similar, you’ll know that this is an awesome proposition and the opportunity for the company here is just absolutely huge. I was confident that Deliveroo would be able to leverage all their experience and expertise to create something really incredible here. Then there’s further expansion in two other initiatives which I was already very enthusiastic about: Editions (delivery-only kitchens) and Signature (white label platform for partners). These are challenging, fairly involved initiatives and they have a real tangible impact on both customers and partners. For example, if like me you’ve tucked into a House Black Daal from Dishoom while curled up on your sofa, you’ll have Editions to thank for that! Finally, there was just so much new talent who I was keen to collaborate with and learn from. The new Chief Product & Technology Officer Devesh Mishra joined at the end of 2021, bringing with him 16 years of experience solving some of Amazon’s most difficult problems. And then there’s the Data Science team in particular which has now grown to 160 people, one of the biggest in Europe (and it’s still growing!). These are just a few of the changes I was personally excited about, but there really is so much happening at Deliveroo - from new products and features, to solving complex logistical problems, to driving user-generated content - that I really could have chosen many others too. All things considered, Deliveroo is the right place for me to thrive and grow. So the grass wasn’t greener, and it’d been a year of big changes. After deciding to leave my previous company, the big question was “where next?”. I always had Deliveroo on my mind. But being in London, I was spoiled with lots of great tech companies full of inspiring people, many of whom I had the pleasure of meeting and discussing a potential future with. I took the time to really reflect on what wasn’t working for me in my recent role. I outlined what’s now a non-negotiable and what’s just a nice-to-have. As I mentioned above, what was most important now was a supportive culture led by kind leadership and an interesting problem space where I could challenge myself and grow. I looked at each company with fresh eyes, and although there were some other great companies who were also a potentially solid fit, I knew Deliveroo ticked every box: I spent two and half years there after all and experienced it first hand. I felt incredibly positive that I could fix some of the former (inevitable) niggles as well as lean into the things I really enjoyed in my previous stint. My last experience at Deliveroo was great, but I knew that this time it could be even better. Woah - isn’t this a step back though? Not at all. We’re only human, we don’t get everything right all the time - and for me, Deliveroo is the best place for me to be right now, and there’s still so much more for me to learn here. On top of that, the past two years have been incredibly tough for all of us. We were locked down for much of it, and like me, you probably felt more disconnected from your work and colleagues whilst also being cut off from the things that enriched you outside of work. This isn’t an ideal environment to be making big decisions in, so there’s especially no shame in getting it wrong and wanting to course-correct. The worst you’ll get is a few raised eyebrows, but they’ll drop soon enough. And even if they didn’t, what’s a few raised eyebrows compared to getting to work in an environment where you know you’ll thrive and be happy? If this has resonated with you and you’re interested in coming back to Deliveroo as well - do reach out to your former manager or somebody else in your management team. For Data Science, this’ll be Mahana Mansfield or Ela Osterberger. If you’d spent a meaningful amount of time at Deliveroo previously and are aiming for the same level, it’ll likely just be a series of informal conversations about where you’ll best fit in and be happiest (amongst the other important bits). If you’re feeling a little more ambitious and want to level-up, expect a light-weight expedited interview process. We’re really excited to hear from you again!
Feb 04, 2022
My first few months as a data scientist at Deliveroo
Kia Ora! I’m Florence, a Senior Data Scientist at Deliveroo. Originally from New Zealand, I moved to London eight years ago and have been working in data ever since. I joined Deliveroo at the end of last year and want to share what I’ve learnt and been up to since. Why I joined Deliveroo My interest in Deliveroo can be summarised into three parts; my enjoyment of eating and getting to think about food all day, the complexity of the business model, and the advanced approach to data needed to remain competitive as a company. The first reason is pretty self explanatory, I am yet to prove to myself that I can cook but I certainly enjoy eating good quality and varied meals throughout the week. Starting my career in the food tech and delivery tech industry at Ocado showed me what a fascinating industry it is, it also confirmed that nothing makes you more hungry than thinking about food all day! I really enjoy being able to see different business models from the inside and learn the subtleties of how they actually work, so the three sided marketplace of Deliveroo really fascinated me. The three sides are the customers (which I was a bit too familiar with from my ordering habits), the riders and delivery, and finally the partners (restaurants and grocers). How all three of these interact adds plenty of additional complexity to any simple analysis. For example if you wanted to run an experiment where a customer could choose to have their bread substituted for a similar loaf you’d need to consider all sorts of things that you’d never think about as a customer: 1. How the customer interacts and chooses this within the app, 2. How the grocery partner would choose what a suitable substitute would be based on stock availability, 3. What would happen if the customer rejected the substitute to the rider on delivery. I couldn’t wait to get stuck in and understand the levers to drive growth at each of these stages. Here’s a taste of some more questions and discussions that I have enjoyed being a part of throughout my career working in this industry. What items are most frequently bought with pasta? Cheese or pasta sauce are obvious answers, but how about red wine or basil? How does having eco-friendly delivery options affect the customers likelihood to choose certain delivery slots? How should premium brands, such as Le Creuset and Dishoom, interact with the changing landscape of online delivery and startup brands? These types of relatable questions intrigue me and made me very keen to be back analysing. All of the above require very complex and nuanced data points to understand what truly happens. Having spent the last few years focusing on analytics engineering, I was excited for where I could add value and contribute. I had actually interviewed at Deliveroo in 2017 when it was much smaller and split across many small offices, but at that point I didn’t have the specific data science background that they were looking for, and so after specialising and learning another business model I thought I’d come see what it was all about once again. My first few weeks There are many highlights to pick from - joining a new and ever-growing team, presenting to Directors, joining Deliveroo’s first hybrid hackathon, as well as teaching and writing a doc on testing clickstream data in Kibana. However the two examples I really want to share in detail are the Deliveroo Tech Academy and my visit to the Islington Deliveroo Editions site. The first two weeks of joining are spent in the (currently virtual) Deliveroo Tech Academy along with any other engineering, product and design new starters. The first day kicked off with computer setup, a general introduction to the organisation and a discussion on DEI (diversity, equity and inclusion) from Busi Sizani, our Head of Global DEI. The following days covered more technical topics, such as how to run cross-geographical experiments, deploying releases with feature flags, details into mobile app development and incident management. Having two weeks to absorb information with no expectations of contributing to project work is a conscious decision at Deliveroo and felt very person-centered, where the focus was on individual development and getting a good grounding in the company. It also meant that at the end of the two weeks everyone was super keen and raring to go. Following the tech onboarding I officially joined my team, which is the team focusing on Deliveroo’s grocery efforts, and I was given my first project! The grocery team is a fairly new area for Deliveroo compared to the more mature restaurant side of the business, which means that there is a huge amount yet to be built and understood, so being comfortable with the unknown is essential - luckily that is exactly how I like to work. As mentioned above, I am no chef but that doesn’t stop me from watching cooking YouTube videos and being super keen to sign up to visit a Deliveroo Editions site. Editions are hubs where we host collections of restaurants, all specially designed for delivery. This meant for a few hours I got to don my chef’s hat, mask, apron and be given a grand tour of how numerous restaurants run out of a creatively built neighbourhood warehouse. My two favourite learnings from my visit were that to be an Editions restaurant you need to have 5 stars on the food hygiene rating scheme, and that the site managers use analyses and reports made by data scientists to ensure all the restaurants under their site are performing at the expected level across all our key metrics - it was great to hear the experiences of other colleagues using data science outputs outside of the main product teams. To top it all off, at the end of the day I was able to choose a takeaway meal from any restaurant within that site - delish. What was surprising Historically, I have been guilty of looking jealously at a larger tech companies and thinking that all the data and workflows would be fully polished and pristine, but I quickly found out that to cope with its enormous growth Deliveroo has been in “scale and survive mode” where everything being implemented tidily and with best practice wasn’t the highest priority. This has meant that people from all ranges of backgrounds, whether that be a startup or an established business have a huge amount to contribute and bring learnings from elsewhere. Another thing that hasn’t necessarily surprised me, but has been reassuring is that despite growing the data science team from 45 to 150 people in one year the “scaling with kindness at front of mind” pursuit has certainly been achieved. The team has been so curious, kind and welcoming. I think having the majority of people join remotely has also helped create the “we’re all in the same boat, and know that a friendly face at the end of the screen really helps”. Autonomy and trust is really important to me When I am interviewing for a new job, a question I try to ask each new person I meet is “can you share a time you had an idea that you believed in and were given the freedom to explore?” Something that has always been very important to me is to have trust and autonomy to dream big and suggest ideas instead of purely relying on senior management to dictate the path forward. Those interviewing me provided an assortment of examples, and in my first few weeks there was an area of opportunity to improve my team’s understanding of clickstream data between Segment into Kibana and then on into Snowflake in a more efficient and realtime way. This was an area I have a lot of experience in and so I jumped at the opportunity to help upskilling with the team and creating documentation to share around the wider business. Another example that has been supported is adding additional latency type metrics as a monitoring metric across variants in an experiment, this is an area I have previously found incredibly valuable and results in large business value.During various discussions I understood the opportunity in more detail and connected dots of people interested in this across the business and am looking forward to having a look at it this year. My favourite data insight so far As I’m sure many people do, I like to tell myself that I make unique choices and am individual in my food tastes, however when I joined I was able to look at the most popular items from my favourite local Greek restaurant. Little did I know, despite having thousands of meal options available, my favourite lamb and tzatziki wrap wasn’t so unique afterall. In fact, it was one of their most ordered items! Not so original, but that doesn’t change how yummy it is. One thing I want someone thinking of applying to know It can be hard within the data and tech world to find organisations which value the individual contributor (IC) career path equally to the manager career path, let alone at all. This was a huge factor in my decision to join - Deliveroo actively encourages and supports the Data Science IC career progression all the way up to director level. This means that there are very senior ICs leading the way with complex analyses and providing upskilling opportunities for more junior colleagues. I really feel that my desire to “code more than sit in meetings” and keep up to date with my analytical abilities will be possible and supported without question. If this is the kind of career path you are looking for, I would definitely encourage you to apply. Come join us!
Jan 19, 2022
The Emergence and Evolution of Analytics Engineering at Deliveroo
What is Analytics Engineering at Deliveroo? Analytics Engineering, for those less familiar with the term, is a relative newcomer to the many technical disciplines that deal with data and/or engineering. The need for a role that intersected data engineering, analytics and data science materialised in the last 5 years or so, on the back of the emergence of cloud data warehousing, self-service BI tools and data pipeline services. Leveraging this new and powerful “modern data stack”, analytics engineers are tasked with transforming raw data from multiple sources into well-modelled and reliable datasets that can be used to make better, faster analytically-driven business decisions. As a result, it also requires a deep understanding of downstream data use-cases and requirements, as well an ability to work alongside software engineers where the provenance of data is of concern. What additional, peripheral responsibilities that belong to the role depend on how exactly the analytics engineering discipline is deployed within the organisation, and we’ll talk about some of those that apply at Deliveroo. Early Challenges Countless tech-focused companies have had to reckon with the dramatic advancement in data tooling and services over the past few years, whether building from scratch or migrating from legacy stacks. Although there are numerous common themes to all of those journeys, each still has its own story to tell, with its own unique challenges. Deliveroo’s journey and path to modern analytics engineering has been particularly interesting to me, for a couple of reasons. Firstly, Deliveroo’s genesis, and its emergence as a definitive food delivery company, almost perfectly coincided with the emergence and maturing of the modern data stack. In 2013, when Deliveroo delivered its first order, on-premise data stacks were well and truly on their way out, but the “platforms” replacing them were still in relative infancy. In 2016, when Deliveroo’s growth (and subsequently our hunger for data) were sky-rocketing, we took an early bet on two emergent tools that remain in our stack to this day - Snowflake & Looker. Despite this early adoption, there was no established playbook for realising the full potential of what these tools unlocked. We dove head first into areas like modern data modelling strategies, self-serve analytics, streaming ingestion and virtual warehouse management at a time when understanding and experience were scarce. What’s more, our scale meant we were pushing these tools to their limit in those early days (we definitely still do, though less often), which made the challenge even more compelling. Ever-present alongside these technical obstacles though have been organisational and process challenges. From staying aligned with stakeholder and partner organisations that are constantly changing around us, to trying to define data domains in a three sided marketplace that is highly intertwined, to preparing for an IPO, to perpetually trying to balance velocity and scalability, we’ve needed to remain flexible, whilst constantly striving for more maturity and refinement. Hiring the right people for this type of environment, and empowering them to have impact in the right organisational setting was therefore critical. This has been a problem of a perpetually unfolding scale. Scale Breeds Specialisation The first hires in any start-up are almost always generalists, and this is no different for the first data hires. As Deliveroo’s first analyst, I would be the seed for what would become BI, a team then responsible for analysis and reporting, and by extension data transformations. Our first couple of data scientists, long before they did any actual data science, built our first analytics database and ELT pipeline. We had everything we needed for a little while, without the need for data-focused engineers. It wasn’t long though before we made our first data engineering hires. They took on the responsibilities of data ingestion, warehouse management and transformation pipelines, whilst the growing BI remained as effective owners of the data itself, and the insights we yielded from it. Around the time we passed around 1000 scripts in our twice daily SQL transformations pipeline, we spun up an “infrastructure” team within BI to specialise in said pipeline. There were two final and important factors that elevated the need for what we now know as our Analytics Engineering team beyond doubt. BI was merged into a rapidly growing data science org, and it was becoming quickly evident that our commitment to put data science and analytics at the centre of everything we did was increasingly out-pacing our ability to maintain and build adequate, reliable data sets. The evolution of what was data engineering into a data services team that owned and maintained our Kafka deployment created a vacuum around our analytics platform tools. Thus Analytics Engineering at Deliveroo was born. After an initial period of operating as a small, nimble team focused on both analytics and data engineering concepts, the team started to forge an identity towards the back end of 2021. Analytics Engineering in Full Bloom The last six months or so for the team have been transformative (pun intended), and 2022 is shaping up to be a landmark year for the discipline within Deliveroo. We’ll be tackling projects related to every corner of the data space, and hope to write about them all throughout the year. To achieve all of these goals, we’ll need more highly skilled engineers, and we’ve made a great start by growing from a couple of full-time analytics engineers in the summer of 2021 to now more than twenty (and we’re not stopping there). This newfound scale has enabled us to implement some key organisational and strategic changes that empower us to reach the next level of impact, by introducing another layer of specialisation within the team. The first and most important of these is a move towards domain-focused pods of analytics engineers. Deliveroo’s data estate is vast and complex, and it has been many years since anyone has been able to have even a reasonable grasp on all of our data, across restaurants, rider, consumer, finance and more. These pods will start by embedding within the corresponding data science teams, which is where a lot of the domain knowledge and relationships that we wish to inherit reside. We’ll gradually break free of this dependency as the team grows in size and influence, becoming an independent entity that partners directly with engineers, product managers and business stakeholders from their area of focus. The deployment of specialised analytics engineers will result in higher quality data being available for data scientists, machine learning engineers and business users, and will unburden data scientists from this kind of work. The impact, particularly for data science, is thus two-fold: more time to deliver higher quality insights. To ensure the highest chance of success for this model, we’ve split the team in two, and spun up an Analytics Platform team. This team will focus on all of the “platforms” that host and process and surface the data that domain-focused analytics engineers are responsible for. Snowflake, Looker and Prefect (our orchestration layer) are at the heart of this analytics platform stack, and alongside data integrations, and strong working knowledge of our Kafka streaming platform, the skillset is more akin to a classic data engineer. What’s more, Analytics Platform are also now part of a newly-formed data platform group, consisting of a well-established experimentation platform team, and a newly forged machine learning platform team. A Constantly Evolving Challenge As has been the case since day one at Deliveroo, we’ll no doubt have to continue to evolve our technical and strategic thinking in step with the internal needs of the business. The organisational model and processes that fit now may not fit us in 12 months time, and that is a reality we’ve learnt to live with. What’s more, the analytics engineering discipline itself is changing at a rapid pace. The playbook for organisational models and the underlying tech stack is constantly under revision, driven forward by competing vendors, and an ever-expanding community of analytics engineers (many of which we take constant inspiration from!). Whilst we attempt to scale up to one of the largest Analytics Engineering teams in existence though, we’ll yet again come across new challenges seldom tackled elsewhere, and we wouldn’t have it any other way.
Jan 14, 2022
How to prepare for the Deliveroo Architecture Interview
At Deliveroo we are constantly trying to figure out the best way to run our interviews with the aim of finding talented engineers while also making the process as enjoyable and interesting as possible. One of the trickiest interviews to prepare for, if you haven’t done one before, is the backend Architecture/System Design interview. Why do we have an Architecture Interview? There’s a lot going on in the system behind Deliveroo’s apps: There are hundreds of services worked on by dozens of engineering teams and they all need to work seamlessly together to get that burger to you at 7pm on a Friday. This means it’s really important that our engineers can reason about and design complicated interacting systems that can handle the scale Deliveroo operates at. How do I prepare? Many companies have an Architecture Interview as part of their hiring process and it’s typically one of the most open-ended in terms of scope. Having run many of these interviews myself I’ve put together the following list of tips that will hopefully help you show your best self in the interview, based on the ways in which I’ve seen candidates (who perhaps haven’t done many Architecture interviews before) struggle. Although these tips are obviously based on Deliveroo’s Architecture Interview they will mostly apply to other companies hiring processes as well, so let’s get to it: There’s no single right answer In the interview we’ll be asking you to design a new system from scratch. The requirements for the system will be deliberately open ended and so there will not be a “correct solution”. So, don’t worry about trying to find a trick or technology that’ll make it trivial and feel free to explain what technologies you think might be suitable, and where the trade-offs are, before picking one to use in your implementation. We’re really looking to see how you go about turning a fuzzy project brief into a solid technical plan. Use what you know As you may know (or may not know, that’s fine too!) at Deliveroo we have a service-oriented architecture. You might have worked on a similar system in the past, or you might not, either way don’t feel like you should use a particular type of architecture (remember there’s no right answer). In my experience, the candidates who use architectures, languages and technologies that they have the most production experience with, whatever they are, tend to do the best. Ideally use technologies you are comfortable with (you could mention though that you think X technology might be better suited because of Y, but you’ve never used it, so are sticking to something you know). Start with an overview and then iterate It’s usually best to go for an iterative approach rather than trying to write down the perfect solution straight away (that’s probably impossible anyway). Sketch out all the core components you think you’ll need to get a minimal working system first, and then iterate and go into more detail (and add more components as needed). Given how broad the systems tend to be, it’s easy to spend a lot of time going in depth in one particular area, but we only have about 45 minutes, so we can’t cover everything! Your interviewer might interrupt and move you on occasionally, but don’t see that as a bad thing: they know the areas they want more detail in, and where the juicy problems are (you can always ask them if they want you to elaborate before you go into more detail). Scaling How your design works at high scale will be important, but it’s also fine to start with a design that will work great (and consistently) at low scale first and then to adapt it later to make it scale. This can be a good approach if a scalable solution doesn’t spring to mind immediately and it’s better to start somewhere (you can always point out that you know component X won’t scale, but you are going to talk about what to use instead later). (For remote interviews) Make sure you are comfortable using a virtual whiteboard tool For onsite interviews we would generally do this interview on a whiteboard or good old pen and paper, but Architecture interviews - as well as a lot of life - are a little different at the moment. For remote interviews, you’ll be asked to share your screen while you design your system. You can use whatever tool you like, and it’s a good idea to get used to drawing boxes, lines and text with it before your interview. Some tools are not the most intuitive if you haven’t used them before, so knowing the tool well will mean you have one less thing to think about during the interview. Some tools we’ve seen used a lot are and Make sure you have also granted your browser all the necessary permissions to share your screen (you can create your own meeting at to test out presenting), so you can spend your time focusing on the interview, rather than fighting with technology! Try designing some systems The best way to practice is by doing. Grab a pen and paper (or a virtual whiteboard) and have a go at designing a web-based system/service you are familiar with. Start simple, drawing out the core components and models you’d need, then think about how increasing the load on the system might make parts of your design struggle. You could, for example, design a social media site, a theatre booking system or even a food delivery service! Whilst not everyone will have access to them, asking more experienced people you know to take you through a mock interview is also a great way of putting yourself on the spot and testing out what you do and don’t know. At the end of the day, there’s no perfect way to prepare - every company runs their system design interviews differently, and your experience with one may not be the same as another. But if you understand why this topic is important to us as an engineering team, and plan your preparation accordingly, you’ll be setting yourself up for success.
Nov 11, 2021
Roo talks series: Why Culture Matters in your Data science team?
Like most companies, Deliveroo has a set of values. However, we can probably all think of examples of companies that have values buried somewhere on their intranet pages but no one else really bothers with. And often the data science team has its own culture, right? And that might be different from the company culture. Not at Deliveroo. In this session, I want to take you through some examples of what it is like working in Data Science at Deliveroo. I’m going to share with you real examples of work done by our brilliant team and I’m going to talk about how we live our values and why they matter to me…and why values should matter to you Enjoy! Link to video Speakers: Richard Smithies

You may also be interested in Related companies

Bengaluru, IN
11086  -9decrease
Swiggy is a company which offers an on-demand food delivery platform designed to provide food from neighborhood restaurants to the customers.
View company
Toronto, CA
Thriver (formerly known as Platterz) owns and operates an online meal ordering marketplace for ordering large and shareable meals for offices.
View company
Chicago, US
2722  28increase
GrubHub provides an online and mobile platform for restaurant pick-up and delivery orders.
View company
Richmond Hill, CA
CMEOW is a company which provides consumer food services.
View company
When was Deliveroo founded?
Deliveroo was founded in 2012.
Who are Deliveroo key executives?
Deliveroo's key executives are Adam Miller, Will Shu and Caleb Merkl.
How many employees does Deliveroo have?
Deliveroo has 8,200 employees.
What is Deliveroo revenue?
Latest Deliveroo annual revenue is £1.19 b.
What is Deliveroo revenue per employee?
Latest Deliveroo revenue per employee is £218.14 k.
Who are Deliveroo competitors?
Competitors of Deliveroo include touch2success, Uber Eats and GrubHub.
Where is Deliveroo headquarters?
Deliveroo headquarters is located at 1 Cousin Lane , London.
Where are Deliveroo offices?
Deliveroo has offices in London, Los Angeles, Balaclava, Brussel and 10 other locations
How many offices does Deliveroo have?
Deliveroo has 15 offices.

Craft real-time company insights

Learn about Craft real-time company insights

Receive alerts for 300+ data fields across thousands of companies

Footer menu