talabat careers and interviews, and how to pass the TDD round.

Updated · Sources at the end

talabat interviews software engineers with a pair-programming round built on test-driven development: you solve a small kata test first with an engineer, then refactor existing code, and talk about how you balance delivery and quality. Candidates describe a system design round where you add a feature to a system that already exists, and a final conversation with a director of engineering. The format follows how talabat says its teams work. Every backend ad says its engineering is based on Extreme Programming, Domain-Driven Design, Lean and Continuous Delivery, with pair and mob programming every day.

talabat started in Kuwait in 2004 and describes itself as the leading food and grocery delivery app in the Middle East and North Africa, in eight countries from the UAE to Egypt and Iraq. Its tech headquarters is at City Walk in Dubai. Delivery Hero owns the majority of it: talabat listed on the Dubai Financial Market on 10 December 2024 after a $2 billion IPO of 20% of its shares, the largest tech IPO in the world that year. Uber's offer for Delivery Hero, recommended by both boards in September 2026, would bring talabat under Uber as well.

Free · 2 minutes · no account

The questions for your exact Talabat role and level.

See the questions Talabat asks ↓Run a free mock interview →

Interviewing at Talabat? Below are the questions candidates report. For the ones your exact role and level will get, paste the posting. Your first mock is free.

01

Who Talabat hires

talabat hires backend, mobile and staff engineers, engineering managers, and data scientists and machine learning engineers, mostly in Dubai, with smaller engineering teams in Cairo. Its backend ads ask for .NET, Go and C#, distributed systems (microservices, event-driven and RESTful services), relational and non-relational databases, a cloud platform, and trunk-based development with continuous delivery. Data and AI hiring runs through an Applied AI Tribe and a global AI hub working on machine learning and LLM systems on Google Cloud and BigQuery. Engineers work in teams grouped into tribes and chapters, so senior and staff ads talk about chapter direction and RFC reviews.

Not sure your resume shows the level Talabat hires at? Check it with a free resume review.

The loops candidates describe share a shape, but the technical rounds change with the job.

  • Track · SWE

    Software engineers

    A recruiter call, the TDD and refactoring pairing round, a system design round on an existing system, and a director of engineering interview. Some candidates report an online coding test first. This is the loop most reports describe and the one this guide covers in most detail.

  • Track · EM

    Engineering managers

    Candidates report five stages, including a pairing session where you refactor an existing block of code and a system design round drawn as diagrams, with a notification system as one reported prompt. The Senior Engineering Manager ad asks for hands-on XP practice, or a strong willingness to learn and lead talabat's approach.

  • Track · Data

    Data science and AI

    Candidates report an HR call, up to three technical rounds on SQL, Python and statistics, and a bar raiser before the offer. Causal inference is reported as a favourite topic, and one final round with a director was a full hour of case study.

02

What is the Talabat interview process?

talabat does not publish its interview stages. Its careers site gives only general tips. The shape below comes from candidate reports on Glassdoor and Blind, seen in search snippets, and a candidate's account of a 2023 senior backend loop in Dubai. Glassdoor puts software engineer hiring at about 21 days on average, against about a month for the company as a whole.

01
Online coding test
Reported in some loops

One senior backend account and some Glassdoor reports start with an online coding challenge before any call. Others go straight to the recruiter. Ask your recruiter whether yours has one.

02
Recruiter call
A video call

Your background, why talabat, and the practical questions every Dubai employer asks early: notice period, visa and relocation, and salary expectations.

03
TDD and refactoring pairing
Live with an engineer, your own language and IDE, screen shared

A small kata solved test first, then a refactoring exercise on existing code. Candidates also report questions on delivery versus quality. One reported kata is a calculator that multiplies without using the multiplication operator. The section below goes through how to take it.

04
System design
Diagrams in a drawing tool of your choice

Candidates describe adding a feature to an existing system more often than designing one from a blank page. Reported prompts include a food or parcel delivery system and a notification system.

05
Director of engineering
The final interview

A mix of technical and non-technical questions: your past experience in depth, how you work, and some more system design. One account calls it a behavioural round with some scripted technical questions.

06
Bar raiser
Reported for data science

Data science candidates report a bar raiser after the technical rounds, as in Delivery Hero's own process. Engineering reports rarely mention one, so ask whether your loop has it.

Data and AI
07
Offer
Through your recruiter

Several candidates report long gaps and rejections with no feedback, including after stages they were told went well. Ask the recruiter for a timeline at each step and follow up in writing.

03

Talabat TDD interview: how to take the pairing round

What candidates report and what talabat's ads ask for

The talabat TDD round is a live pairing session with an engineer. You share your screen and work in the language and IDE you choose. Candidates describe a small kata solved test first, a refactoring exercise on existing code, and questions about delivery versus quality. One candidate on Blind reported the interviewer arriving late, spending about 30 minutes on behavioural questions, and leaving 30 minutes to solve, test, optimise and then debug a different problem. Plan for a tight hour.

  • Set up before the call: Have a project open with a test runner that already passes one trivial test, in the language you know best. Minutes spent installing a test framework are minutes the kata doesn't get.
  • Write the failing test first, every time: Say the cycle out loud: a failing test, the simplest code that passes it, then refactor. For the multiplication kata, start with multiplying by zero, then by one, then two positive numbers, then a negative. The interviewer is watching the order you work in as much as the answer.
  • Keep the steps small: Add one case at a time and let the tests push the design. A jump straight to the general solution with tests written afterwards looks like code with tests, which is the opposite of what the round checks.
  • Refactor only on green: When the refactoring exercise starts, pin the current behaviour with tests first, then change the code in small moves and run the tests after each. Name what you are fixing: a long method, duplicated logic, an unclear name.
  • Treat the interviewer as your pair: talabat's teams pair every day, so this is also a check on how you work with someone. Ask questions, take hints, and switch between driving and navigating if they offer. Say when you are unsure.
  • Watch the clock: If the session starts late or the opening questions run long, ask early how the time will be split. Get to a first passing test quickly, so you have working, tested code to show even if the optimisation and debugging parts get squeezed.
  • Have a view on delivery and quality: Candidates report questions on this in the same round. talabat's ads say quality enables speed and call the trade-off a flawed idea. Prepare a real example where tests, small batches or pairing let you ship faster.

Candidates describe the kata and refactoring parts in different orders, and some engineering manager loops do only the refactoring. Ask your recruiter what the round includes and how long it is.

The rest of the loop depends on your role. Pick it, or paste the posting, and Calibrd predicts the rounds and questions you are likely to get at Talabat.

Predict my Talabat questions →
04

Talabat system design: adding to a system that already exists

Reported prompts and how to take each

Candidates describe the system design round as extending an existing system more often than designing one from scratch, with diagrams drawn in a tool you choose. One candidate felt the interviewers wanted a set structure they did not give, so lay out your answer in clear steps: requirements, the current system, the change, data, scale, and rollout.

  • Add a feature to an existing system: Ask how the system works today before drawing anything. Show which services change, which stay as they are, and how you would ship the change in small steps behind a flag.
  • A food or parcel delivery system: Cover the order, the restaurant or store confirming it, rider assignment and live tracking. Say where you need strong consistency (payment, one rider per order) and where eventual consistency is fine (tracking).
  • A notification system: Reported for engineering managers. Cover the channels (push, SMS, email), a queue between the senders and the providers, retries, user preferences and rate limits, so customers are not flooded at peak.
  • One feature that works in eight countries: talabat runs one app across the UAE, Kuwait, Qatar, Bahrain, Oman, Jordan, Egypt and Iraq. Say how a feature handles different currencies, payment methods, languages (Arabic and English) and local rules.

talabat's ads mention Domain-Driven Design and event-driven microservices, so use bounded contexts and events in your answer where they fit.

05

What Talabat screens for

talabat publishes three values, and its engineering ads describe the way teams work in some detail. The pairing round tests the second part directly.

  • Experience first: customers, partners and colleagues at the heart of what you do
  • Make it happen: commit, raise the bar and recover quickly from mistakes
  • Together we grow: valuing diversity, giving feedback and supporting each other
  • Quality enables speed: the ads call the speed-versus-quality trade-off a flawed idea, so expect to defend tests and refactoring as the fast route
  • Shorter feedback loops and small batches, through trunk-based development, continuous delivery and pairing
  • Product-minded engineers who understand the business and the customer, so fewer hand-overs are needed
06

Talabat interview questions

Candidate-reported themes

Candidates report the format of the rounds more often than full questions. The questions here follow those reports and what talabat's own job ads say it looks for.

Behavioural & motivation

  • Why talabat?Listening for: Specificity · Connection · Research
  • Tell me about a time you had to choose between shipping fast and keeping the quality high.Listening for: A real trade-off · How they kept quality · What happened
  • Tell me about a time you paired or worked in a mob on a hard problem.Listening for: How they worked · Listening · The outcome
  • Engineering managers: how would you bring TDD to a team that writes few tests today?Listening for: A small start · Bringing people along · How they'd know
  • What are your salary expectations?Listening for: Preparation · Anchor · Composure

Technical

  • Multiply two integers without using the * operator, writing each test before the code that makes it pass.The TDD kata: Reported: a calculator that multiplies two numbers without using the multiplication operator, solved test firstListening for: Tests first · Small steps · Refactor on green
  • Practice: a 150-line method calculates the delivery fee with nested if statements for city, distance, time of day and promotions. How do you make it safe to change?Refactoring existing code: Reported for engineers and engineering managers: improving an existing block of code. A practice question in that styleListening for: Tests before changes · Names the problems · Small, safe moves
  • Practice: talabat wants customers to schedule an order for later today. How do you add this to the existing ordering system?System design on an existing system: Reported: adding a feature to a system that already exists, plus a food or parcel delivery system and a notification systemListening for: Starts from what exists · A sound change · Safe rollout
  • Practice: talabat cut delivery fees in one city for a month. How do you measure the effect on orders?Data science: causal inference: Reported as a favourite topic in data science final rounds, with SQL, Python and statistics earlier. A practice question in that styleListening for: A fair comparison · What could fool you · A decision

These are the reported themes, and your loop is role-specific. Paste the actual posting and Calibrd predicts the questions for that exact role and level. How the questions are predicted →

Predict my Talabat questions →
07

Pay

This guide shows no pay table: talabat's job ads publish no salaries, and the Levels.fyi pages for talabat could not be read directly on 16 October 2026. Its search listing showed software engineer total pay in Dubai from about AED 240K a year at Software Engineer I to about AED 500K at Senior Software Engineer, tax-free. The Dubai market guide has pay bands for the wider city. Calibrd benchmarks the pay on any posting you scan against its level and location.

08

How to prepare for a Talabat interview

  1. Practise three or four classic TDD katas out loud (FizzBuzz, Roman numerals, the bowling game, string calculator) in the language you will use.
  2. Set up a project with a working test runner before the pairing round starts.
  3. Practise refactoring messy code under tests: pin the behaviour first, then change it in small steps.
  4. Prepare one story about shipping fast without lowering quality, with numbers.
  5. Practise a system design answer that starts from an existing system and adds one feature.
  6. Read talabat's three values and the engineering culture paragraph in its job ads before the director round.
  7. Have your notice period, visa situation and salary expectations ready for the first call.
  8. Ask the recruiter for the timeline at each stage and follow up in writing; candidates report long silences.

This guide covers talabat's engineering hiring in Dubai, with notes on its engineering manager and data science loops. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

Also interviewing at Careem, noon or Tabby? Their guides follow the same format, from the first screen to the offer.

Knowing the questions isn’t the same as answering them out loud. Run a Talabat mock: spoken answers, coached on the spot. Your first mock is free.

Run a Talabat mock →
09

FAQ & sources

What is Talabat's interview process?

talabat does not publish its interview stages. The stages, in order: Online coding test; Recruiter call; TDD and refactoring pairing; System design; Director of engineering; Bar raiser; Offer.

What does Talabat look for in candidates?

talabat publishes three values, and its engineering ads describe the way teams work in some detail. Experience first; Make it happen; Together we grow; Quality enables speed.

What questions does Talabat ask in interviews?

Candidates report the format of the rounds more often than full questions. Technical themes: The TDD kata; Refactoring existing code; System design on an existing system; Data science: causal inference.

What is the talabat TDD interview?

The talabat TDD round is a live pairing session with an engineer. You share your screen and work in the language and IDE you choose. Covered on this page: Set up before the call; Write the failing test first, every time; Keep the steps small; Refactor only on green; Treat the interviewer as your pair; Watch the clock; Have a view on delivery and quality.

What system design questions does talabat ask?

Candidates describe the system design round as extending an existing system more often than designing one from scratch, with diagrams drawn in a tool you choose. One candidate felt the interviewers wanted a set structure they did not give, so lay out your answer in clear steps: requirements, the current system, the change, data, scale, and rollout. Covered on this page: Add a feature to an existing system; A food or parcel delivery system; A notification system; One feature that works in eight countries.

How do I prepare for a Talabat interview?

Practise three or four classic TDD katas out loud (FizzBuzz, Roman numerals, the bowling game, string calculator) in the language you will use. Set up a project with a working test runner before the pairing round starts.

Prep for a real Talabat role

Practise your Talabat interview, out loud.

Paste a real Talabat posting and Calibrd predicts the questions for that role and level, benchmarks the pay, and flags the gaps an interviewer will probe in your resume — then listens to your spoken answers and coaches them. Your first mock is free.

Free to start · No card · Encrypted at rest, never used to train AI, remove anytime

Two weeks out?

Email me the Talabat prep checklist

The round that decides it, the questions they ask, and what to do before, in one email. Nothing else unless you sign up.

talabat Careers and Interview: TDD Pairing Round — Calibrd