Grab | Senior Software Engineer | Oct 2023 | Ghosted
Interview Experience
Round 1 DSA round. Got positive feedback 1. Group anagrams 2. Next greater element Second round scheduled. Second round cancelled. Recruiter said he will reschedule. He never rescheduled. Ignored my calls, cut...
Full Details
**
Round 1 DSA round.** Got positive feedback
1. Group anagrams
2. Next greater element
Second round scheduled.
Second round cancelled. Recruiter said he will reschedule.
He never rescheduled. Ignored my calls, cut my calls. He did not reply to my mails.
Grab forgets that their employees are a human being. Even a rejection mail stating that you filled the position or found someone else would work and be a decent, respectful and professional way to end application.
But giving positive feedback, chasing a candidate and then ghosting them shows low ethics. I don\'t want to think what happens once they hire and how they treat employees once they pay them salary. Maybe it is good in the long run.
About This Question
This is a candidate experience report from a grab interview for a swe role (senior level) during the recruiter round reported in 2023.
About Grab Interview Reports
This question was reported by a candidate who interviewed at Grab. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Grab are the higher-signal extractions to take from this report.
For broader preparation context, the Grab interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Grab reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Grab Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Grab reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.