Real, anonymous reports from people who interviewed for Software Engineer at Grab, newest first and distilled into what to expect across the loop.
I remember how structured everything was at the start: a resume shortlisting phase, then an OA that centered on medium DSA problems. After that, there were two technical interviews. The first interview leaned hard into DSA again, with a couple of medium-hard problems, and the second interview mixed resume and technical depth with system design and CS fundamentals.
I started with an HR screening call where the conversation stayed pretty close to what I’d already put on my resume—my background, why I was interested, and a quick self intro. The pacing felt quick and organized, and the tone was friendly and accommodating. After that, I moved into technical rounds back-to-back rather than waiting around for long stretches.
The interview process typically includes an HR screening, followed by multiple technical rounds that may involve coding, system design, and a culture fit discussion. The overall timeline can vary significantly, with some candidates experiencing prolonged waits for feedback or updates.
Candidates can expect a strong emphasis on data structures and algorithms (DSA) during the coding rounds, often featuring LeetCode-style problems that range from easy to medium difficulty. The format tends to be strict, focusing on both correctness and the candidate's thought process under time constraints.
The system design interviews require candidates to demonstrate their understanding of architectural principles and the ability to reason through design choices. Interviewers often expect detailed explanations of components, scalability, and trade-offs involved in the design process.
Later stages typically include behavioral interviews focused on cultural fit and teamwork, where candidates are assessed on their past experiences and how they align with the company's values. These discussions tend to be more conversational and collaborative.
Many candidates report frustrations with the lack of communication and feedback throughout the process, particularly after interviews. Some experience ghosting or delayed responses, leading to a sense of uncertainty and dissatisfaction with the overall experience.
The interview experience is often described as high-pressure, with strict time limits and a focus on precision. Candidates may feel that the format prioritizes outcomes over collaborative problem-solving, which can lead to a stressful atmosphere during technical assessments.