Candidate reports point to a 3-4 round Grab Software Engineer process centered on coding, system design, and a manager or culture discussion. Preparation should emphasize clear technical reasoning and defensible tradeoffs.
$157K
Avg. Base Comp
$200K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Grab Software Engineer candidates reported four to five interview steps, although the exact sequence varies by team and level. Accounts describe an introductory or HR conversation, coding assessments or live technical work, system design, and a manager or culture-focused discussion. Some processes included both an online assessment and a later live coding stage, while others moved through a shorter sequence.
Coding formats range from online Codility- or LeetCode-style assessments to live implementation. Reported work included medium-level algorithm questions, explaining the reasoning behind a solution, manually tracing code, and completing test cases under time pressure. One candidate also described a practical API exercise built from a blank project. Practice stating your approach before coding, validating it carefully, and working without code-completion support.
System-design prompts included an internal meeting-booking system, a parking lot, and a mobile-related design. Candidates were asked to explain assumptions, architecture, scalability, and why they selected one approach over alternatives. Interviewers also introduced constraints during one discussion and probed the reasoning behind past project and technology choices.
Manager or culture conversations were described as conversational, with discussion of prior experience, culture fit, and technical judgment depending on the interviewer. Prepare concise project examples that explain your contribution, major decisions, alternatives considered, and problems encountered.
Synthesized from 8 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 Grab process.
The part that caught me off guard was the technical interview: after about 25 minutes of fairly easy fundamentals, including lifecycle questions, I was given roughly 30 minutes to design an API end to end, from parsing through the UI. I had expected something closer to the LeetCode-style algorithms that had been mentioned by HR, so the format felt quite different. There was no code-completion support, and I had to create the files from scratch, which made the time pressure much more noticeable.
The broader process began with my application and a screening step, followed by an online assessment with three Codility questions. After clearing screening, the recruiter communicated the next steps clearly, and my interactions with both the recruiter and engineering team were positive. The technical work was less about a single isolated algorithm than being able to build something practical quickly; another exercise in this process involved building a class-based array operator that could modify an array. There was also a standard conversational component, including “tell me about yourself,” and later discussion around compensation and the company’s “4H” topics.
I ultimately did not receive an offer. My main advice is to practice working from a blank project without editor assistance and be ready to explain an API/design solution across parsing and UI concerns under a short time limit, not just solve algorithm problems.
Prep tip from this candidate
Practice creating a small API/design solution from scratch with no code completion, including parsing and UI considerations, in about 30 minutes. Also prepare for a class-based array-manipulation exercise and the three-question Codility assessment.
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 Grab
In which case would you use a bagging algorithm versus a boosting algorithm
| Question | |
|---|---|
| The Brackets Problem | |
| Rearranging Digits | |
| Swipe Payment API | |
| Your Strengths and Weaknesses | |
| Employee Salaries | |
| Weighted Keys | |
| P-value to a Layman | |
| Top 3 Users | |
| Raining in Seattle | |
| Maximum Profit | |
| Daily Retention Summary | |
| Download Facts | |
| Sum to N | |
| User Experience Percentage | |
| Distance Traveled | |
| Retailer Data Warehouse | |
| Google Maps Improvement | |
| Third Purchase | |
| Average Order Value | |
| Type-ahead Search | |
| Random Weighted Driver | |
| Sort Strings | |
| Production Model Monitoring | |
| Three Zebras | |
| Hurdles In Data Projects | |
| Dijkstra implementation | |
| Christmas Dinner Ingredient Optimization | |
| Success Measurement | |
| Rider Discount |
Synthesized from candidate reports. Individual experiences may vary.
Candidates reported an initial HR, recruiter, CV, or introductory call. Topics included background, qualifications, motivation for changing jobs or joining, salary expectations, and past projects or assignments. Reported screen lengths ranged from roughly 15 to 30 minutes, but timing was not consistent across accounts.
Candidates described Codility- or LeetCode-style assessments and live coding. Reported examples included medium-level algorithm problems, interval-style questions, and array or string work. Interviewers may ask you to explain the approach, complexity, edge cases, and manual validation while implementing; some accounts also describe revising a solution after new requirements.
Several candidates reported a system-design round. Prompts varied, including a payment gateway, an internal meeting-booking system, a parking lot, and a mobile-related design. Discussion covered assumptions, components, scalability, reliability, failures, and the reasoning behind design choices. Project examples may be used to explore similar technical judgment.
Candidates described a final manager or culture-fit conversation that was generally behavioral and conversational. Reported themes included collaboration, ownership, disagreement, motivation, decision-making, and prior experience. Some accounts noted technical questions connected to projects or engineering judgment, so prepare examples with clear context, actions, and tradeoffs.
