Talabat Senior Software Engineer, Logistics Interview Experience
Talabat · Senior · Software Engineer
Illustrative example written by Top Tech Transition from typical interview processes, not a candidate's own account.
The dispatch design went well, but they wanted more depth on how I'd measure whether a new assignment algorithm actually helped.
Interview process
Recruiter outreach. Recruiter call, coding screen, then a loop with coding, system design, an experimentation discussion and the hiring manager.
Interview rounds · 5
- 1
Recruiter screen
Background and team fit.
- 2
Technical round
CodingCoding screen.
Q1. Assign orders to riders to minimise total distance, greedy first.
How they answeredGave a greedy nearest-rider approach, then discussed batching orders that go the same way.
- 3
Final / onsite round
System DesignSystem design.
Q1. Design the order-to-rider assignment system.
How they answeredEvent-driven: orders and rider states feed an assignment service per zone that runs every few seconds.
Follow-up questions- How would you roll out a new assignment algorithm safely?
- 4
Final / onsite round
TechnicalExperimentation and metrics.
Q1. How would you test whether a new algorithm reduces delivery time?
How they answeredProposed an A/B test by zone. They pointed out network effects between riders, which I hadn't covered well.
- 5
Final / onsite round
BehavioralHiring manager.
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
For senior roles, be ready to talk about experiments in a marketplace, where one group can affect another.
Company culture
Data-driven culture. Every change is measured.