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

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.
ResultRejected
Timespan4 weeks
DifficultyMedium
Rounds5

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

    Recruiter screen

    Background and expected salary in AED.

  2. 2

    Online assessment

    Coding

    Two problems on HackerRank in 75 minutes.

    1. Q1. Group anagrams from a list of words.
      How they answered

      Hashmap keyed by sorted characters. Straightforward.

  3. 3

    Final / onsite round

    CodingData Structures & Algorithms

    Coding round.

    1. Q1. Merge overlapping delivery time windows.
      How they answered

      Sort by start and merge. Then extended it to return the free gaps.

  4. 4

    Final / onsite round

    Low Level Design

    Low-level design.

    1. Q1. Design the classes for a restaurant menu with items, add-ons and availability by time of day.
      How they answered

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

    Final / onsite round

    Behavioral

    Culture and values conversation.

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

Details

CompanyCareem
RoleSoftware Engineer
LevelMid level
LocationUAE
InterviewedSep 2026
Questions asked4