Top Tech Transition ₹9 Masterclass

Real Interview Experiences

Learn what to expect, straight from candidates who've been through it at top tech companies.

1346 interviews325 companies432 offers
Loading experiences…

Browse by company

Browse by role

← Back to all experiences

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.
ResultRejected
Timespan5 weeks
DifficultyDifficult
Rounds5

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. 1

    Recruiter screen

    Background and team fit.

  2. 2

    Technical round

    Coding

    Coding screen.

    1. Q1. Assign orders to riders to minimise total distance, greedy first.
      How they answered

      Gave a greedy nearest-rider approach, then discussed batching orders that go the same way.

  3. 3

    Final / onsite round

    System Design

    System design.

    1. Q1. Design the order-to-rider assignment system.
      How they answered

      Event-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. 4

    Final / onsite round

    Technical

    Experimentation and metrics.

    1. Q1. How would you test whether a new algorithm reduces delivery time?
      How they answered

      Proposed an A/B test by zone. They pointed out network effects between riders, which I hadn't covered well.

  5. 5

    Final / onsite round

    Behavioral

    Hiring manager.

    1. Q1. Tell me about a time you disagreed with a technical decision.
      How they answered

      I 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.

Details

CompanyTalabat
RoleSoftware Engineer
LevelSenior
LocationUAE
InterviewedSep 2026
Questions asked4