Candidates report a Grab Software Engineer loop of a recruiter screen, LeetCode- or Codility-style coding, a system design discussion and a manager or culture-fit conversation. Formats vary by team.
$132K
Avg. Base Comp
$172K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Candidates describe a Grab Software Engineer loop that combines algorithm coding, system design and a culture-fit conversation. Most reports begin with a recruiter or HR screen covering background and motivation. Several then describe a Codility-style online assessment or a live coding session with LeetCode-style problems. Problems named include Simplify Path, House Robber, Top K Frequent Elements, interval problems, a largest-sum-subarray problem and a 3Sum-style question adapted to a practical use case. One candidate was instead asked to build an API end to end, from parsing through the UI, in about 30 minutes without code completion, so practice working from a blank project.
System design appears in most reports, and the interviewers probe the reasoning behind your choices, not just the diagram. Reported prompts include a parking lot high-level design, an internal meeting-booking system and a mobile-related design where constraints were added mid-interview. One candidate who received an offer said the depth came from defending tradeoffs. Another said they needed to cover architecture, components and scalability rather than stopping at a basic diagram. A senior candidate found that the design question can depend heavily on the team.
Expect questions about your own projects, including why you chose a stack and which alternatives you rejected. Some interviewers also want you to narrate your logic or trace code by hand before running it. The final conversation is usually with a hiring manager and covers behavior and team fit. Outcomes were mixed, with some candidates receiving offers and others not, so tailor your preparation to the specific team where you can.
Synthesized from 26 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.
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 | |
| Top 3 Users | |
| Weighted Keys | |
| User Experience Percentage | |
| P-value to a Layman | |
| Distance Traveled | |
| Size of Joins | |
| Daily Retention Summary | |
| Raining in Seattle | |
| Maximum Profit | |
| Download Facts | |
| Sum to N | |
| Retailer Data Warehouse | |
| Google Maps Improvement | |
| Type-ahead Search | |
| Type I and II Errors | |
| Third Purchase | |
| Ride-Sharing App Schema | |
| Average Order Value | |
| Groups of Anagrams | |
| Random Weighted Driver | |
| Binary Tree Conversion | |
| Sort Strings | |
| Production Model Monitoring | |
| Justify a Neural Network |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an opening call with a recruiter or HR contact, lasting from roughly 15 to 30 minutes. It typically covers your background, why you are changing jobs and sometimes salary expectations. Prepare a concise story about your most interesting project.
Several candidates describe an online assessment before live interviews, including a three-question Codility test and two medium LeetCode-style problems such as Simplify Path and House Robber. Not every candidate describes this step, so it may depend on team or level. Practice timed problems and aim to pass every test case.
Candidates report live coding with engineers, often LeetCode easy to medium. Topics mentioned include intervals, Top K Frequent Elements and a largest-sum-subarray problem. Some interviewers wanted the thought process narrated or code traced by hand. One candidate was asked to design an API end to end without code completion, so practice working from a blank editor.
Many candidates report a design discussion, with prompts such as a parking lot, an internal meeting-booking system or a mobile-related design. Interviewers may add constraints midway and ask why you made particular choices. Prepare to defend tradeoffs, cover architecture and scalability, and discuss past project decisions.
Final conversations are typically with a hiring manager and are described as relaxed and conversational. Depending on the interviewer, they cover culture fit, behavioral questions and sometimes technical topics. Prepare concrete examples of your specific contributions.
