LeetCode Experience · Jul 2024 · Singapore

Grab |SDE1|Rejected

1 upvote 128 views 1 reply

Interview Experience

Applied through refferal Education: CS from Tier-3 college Exp: 1.7 cyber security company Round 1 (Phone Screen): Interviwer for Singapore Basic Intro from both sides.straight to coding question Q1.Valid anagram(needed multiple approach) then moved to...

Full Details

Applied through refferal

Education: CS from Tier-3 college
Exp: 1.7 cyber security company

Round 1 (Phone Screen):

Interviwer for Singapore

Basic Intro from both sides.straight to coding question

Q1.Valid anagram(needed multiple approach) then moved to optimised needed to dry run for various testcases

Q2.write a function to check whether the previous string and new string are anagram if yes return true or false
multiple fuction call will be given to isAnagram

String a="listen"

return false as nothing to compare
String b="silent"

return true
String c="abc"

return false

so isAnagram(string str) is called multiple times with each new string.
expected answer based on oops

Recruiter connected for further rounds .He wanted to take the interview same day which was not possible with me,later got rejection mail within few days .

Free preview — 6 questions shown. Unlock all Grab questions →

About This Question

This is a candidate experience report from a grab interview for a swe role during the recruiter round reported in 2024.

It covers the following topics: Strings .

Topics

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.