Careem Senior Software Engineer, Backend (Mobility) Interview Experience
Careem · Senior · Software Engineer
Illustrative example written by Top Tech Transition from typical interview processes, not a candidate's own account.
The system design round was all about matching riders and captains in real time, and they pushed hard on what happens when a city spikes on a Friday night.
Interview process
Recruiter reached out on LinkedIn. After a recruiter call I had a HackerRank assessment, then a virtual onsite with two coding rounds, one system design and one behavioral with the hiring manager. The process felt structured and the interviewers were mostly senior engineers from the mobility team. Relocation to Dubai was discussed early, which I appreciated.
Interview rounds · 5
- 1
Recruiter screen
Thirty minutes on my background, notice period and whether I was open to relocating to Dubai.
- 2
Online assessment
CodingData Structures & Algorithms90-minute HackerRank with two problems, medium difficulty.
Q1. Find the minimum number of meeting rooms needed for a list of intervals.
How they answeredSorted start and end times separately and used two pointers. Passed all tests.
- 3
Final / onsite round
CodingData Structures & AlgorithmsCoding round with a senior engineer.
Q1. Given a stream of driver locations, return the k nearest drivers to a rider.
How they answeredStarted with a heap over distances, then discussed bucketing locations into geohash cells so we only search nearby cells.
Follow-up questions- How would this change if drivers move every few seconds?
- 4
Final / onsite round
System DesignSystem design with a principal engineer.
Q1. Design a ride dispatch system that matches riders to captains.
How they answeredSplit it into location ingestion, a matching service per city, and a trip state machine. Spent most of the time on hot-spot cities and on making matching idempotent when retries happen.
Follow-up questions- How do you handle surge pricing?
- What if the matching service in one city goes down?
- 5
Final / onsite round
BehavioralBehavioral with the hiring 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
Practise one real-time location design end to end. Be ready to talk about scale for the region: many cities, very different traffic patterns, and weekend peaks.
Company culture
Engineering-led, with a lot of ownership per team. People talked about the region and its users a lot, which I liked.