Careem Software Engineer interviews typically combine an HR or recruiter screen, one or two live coding rounds with medium-difficulty DSA problems, a system design or role-specific technical round, and a hiring manager or bar raiser round focused on fit.
$122K
Avg. Base Comp
$143K
Avg. Total Comp
Not reported
Typical Rounds
4 weeks
Process Length
Across the candidate reports here, the Careem Software Engineer pipeline generally opens with a recruiter or HR screening call, sometimes paired with an online assessment or a short set of multiple-choice technical questions. From there, candidates typically face one or two live coding interviews built around LeetCode-medium problems — reported examples include a building-sunlight array question, a longest-palindrome problem, and, in one report, graph traversal. Several reports describe a distinct system design or role-specific technical round layered on top of coding: one candidate was asked about Kubernetes service types and a catalogue API design, another walked through ride-hailing search and driver-tracking architecture, and others got Twitter-like or food-ordering system design prompts. A hiring manager round commonly follows, mixing behavioral questions about motivation and what you want in your next role with, in some cases, CS fundamentals like databases and networking. Several candidates also describe a final bar raiser round that leans more subjective, assessing cultural fit and scenario-based judgment rather than pure technical skill. The number of stages varies noticeably between candidates, from a phone screen plus a three-interview virtual onsite to longer loops with a written assessment, several technical rounds, and separate hiring manager and bar raiser conversations. The two candidates who gave an explicit timeline each described roughly four weeks to a month end to end, and one reported gaps of two weeks or more between rounds. Outcomes in these reports skew toward rejections or declined offers, and a few candidates noted slow or minimal feedback after the process, so it's worth preparing both technically and for a process that may take real patience.
Synthesized from 7 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Careem process.
The process was a bit longer than I expected and started with a TA reaching out, then a general phone screening that was mostly technical and included around 10 MCQs. After that I moved into a virtual onsite with three interviews: Technical Expertise, Coding, and Managerial. The technical part leaned more toward role-specific knowledge than deep algorithm tricks, and I was asked about the different types of services in Kubernetes and when to use them. That set the tone pretty well, because the rest of the process felt like a mix of practical engineering knowledge and standard problem solving rather than anything overly exotic.
The coding round was in the usual LeetCode medium range. I got a building-sunlight style array problem where you have to count how many buildings can receive sunlight from the left, and another question around finding the length of the longest palindrome. There was also a system design-style prompt to design a catalogue API, which made the onsite feel fairly balanced between coding and design. The managerial round was honestly the weakest part of the experience for me. The interviewer was late, didn’t seem fully engaged, and ended the conversation early, which made it feel pretty biased and rushed. Overall, I’d say the process was manageable if you’re comfortable with medium DSA questions, basic Kubernetes concepts, and a bit of API design. I ended up not getting an offer, so I’d go in expecting a solid technical bar and a manager round that may not be very interactive.
Prep tip from this candidate
Focus on LeetCode-medium style coding problems like array scanning and palindrome-related questions, and be ready to explain Kubernetes service types and when each one is used. It also helps to practice a simple API design prompt like a catalogue service, since that came up in the onsite.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Careem
Design a data warehouse for a new online retailer
| Question | |
|---|---|
| Daily Retention Summary | |
| Target Value Search | |
| Your Strengths and Weaknesses | |
| Fast Food Database | |
| Visible Buildings | |
| Length Of Longest Palindrome | |
| Employee Salaries | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Monthly Customer Report | |
| Top 3 Users | |
| Raining in Seattle | |
| P-value to a Layman | |
| Weighted Keys | |
| Payments Received | |
| User Experience Percentage | |
| Last Transaction | |
| Distance Traveled | |
| Duplicate Rows | |
| Google Maps Improvement | |
| Bagging vs Boosting | |
| Employee Salaries (ETL Error) | |
| Ad Comments | |
| Size of Joins | |
| Sum to N | |
| Maximum Profit |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial outreach from a recruiter or TA, often followed by a phone screening that covers background and experience. In at least one case this screen included roughly 10 technical multiple-choice questions, while others describe it as a more standard HR conversation about past projects and situational questions.
Some candidates took a written or online assessment with a handful of problem-solving questions before live interviews, including one written test held at a university. Candidates describe these as straightforward DSA fundamentals rather than unusual or highly difficult problems.
Most candidates went through one or two live coding rounds focused on data structures and algorithms, with one report describing technical rounds of about an hour each. Reported problems include array-based questions (counting buildings that receive sunlight, summing without indices), finding the longest palindrome, and graph traversal, with interviewers evaluating approach, edge-case handling, and optimization rather than requiring exotic tricks.
Several candidates describe a separate round centered on system design or specialized engineering knowledge — examples include designing a catalogue API, a Twitter-like system, a food-ordering platform, or ride-hailing search and driver-tracking infrastructure. One candidate was also asked about Kubernetes service types, suggesting this round can lean toward practical infrastructure knowledge as much as abstract design.
A hiring manager round commonly follows the technical stages, where candidates discuss their motivation for joining and what they want in their next role. In one report this round also tested core CS fundamentals like databases and networking rather than staying purely behavioral; another candidate found this round poorly run, describing a late and disengaged interviewer, so experiences here appear to vary.
Several candidates describe a bar raiser round as the last step, focused on behavioral and scenario-based questions about handling challenges, work attitude, and overall fit. Candidates characterize this round as more subjective than the technical stages, and one candidate was rejected without specific feedback despite feeling good about the technical rounds.
