Careem Software Engineer II (Food) Interview Experience
Careem · Mid level · Software Engineer
Illustrative example written by Top Tech Transition from typical interview processes, not a candidate's own account.
I cleared the coding but my low-level design for a restaurant menu service wasn't structured enough for them.
Interview process
Applied through the careers page. Recruiter call, an online assessment, then a loop with coding, low-level design and a culture round. Feedback came within a week and was specific, which helped.
Interview rounds · 5
- 1
Recruiter screen
Background and expected salary in AED.
- 2
Online assessment
CodingTwo problems on HackerRank in 75 minutes.
Q1. Group anagrams from a list of words.
How they answeredHashmap keyed by sorted characters. Straightforward.
- 3
Final / onsite round
CodingData Structures & AlgorithmsCoding round.
Q1. Merge overlapping delivery time windows.
How they answeredSort by start and merge. Then extended it to return the free gaps.
- 4
Final / onsite round
Low Level DesignLow-level design.
Q1. Design the classes for a restaurant menu with items, add-ons and availability by time of day.
How they answeredI jumped into classes too early. The interviewer wanted entities, relationships and how availability rules would be evaluated before any code.
Follow-up questions- How would you support a menu change without redeploying?
- 5
Final / onsite round
BehavioralCulture and values conversation.
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 mid-level they really test low-level design. Practise modelling a domain on paper before writing classes.
Company culture
Friendly interviewers, clear process, quick feedback.