Talabat Software Engineer, Backend Interview Experience
Talabat · Mid level · Software Engineer
Illustrative example written by Top Tech Transition from typical interview processes, not a candidate's own account.
They cared a lot about how I'd estimate delivery times, even in the coding round.
Interview process
Applied online. Recruiter screen, a technical screen, then a final loop with coding, system design and a values round.
Interview rounds · 5
- 1
Recruiter screen
Background and why food delivery.
- 2
Technical round
CodingTechnical screen with an engineer.
Q1. Return the top K most ordered dishes from an order log.
How they answeredCounted with a hashmap and used a min-heap of size K.
Follow-up questions- What if the log doesn't fit in memory?
- 3
Final / onsite round
CodingData Structures & AlgorithmsCoding.
Q1. Find the shortest path for a rider who must pick up from two restaurants before delivering.
How they answeredRan Dijkstra from each point and compared the two pickup orders.
- 4
Final / onsite round
System DesignSystem design.
Q1. Design the order tracking page that shows live rider location.
How they answeredWebSockets fed by a location stream, with the rider's position sampled every few seconds and smoothed on the client.
Follow-up questions- How do you handle riders with poor connectivity?
- 5
Final / onsite round
BehavioralValues round.
Q1. Tell me about a time you disagreed with a technical decision.
How they answeredI used a migration where I pushed back on a big-bang cutover, proposed a dual-write phase with a kill switch, and showed the rollback plan. They cared most about how I brought the team along, not who was right.
Follow-up questions- What would you do differently now?
Tips from the candidate
Think about real-world constraints: patchy rider connectivity, peak lunch and dinner hours, and many small cities.
Company culture
Fast-moving, product-minded teams with lots of experimentation.