Real, anonymous reports from people who interviewed for Software Engineer at Garena, newest first and distilled into what to expect across the loop.
I went through a recruiter-focused conversation where we walked through my background in detail, and the interviewer felt genuinely friendly. After that, I was pulled into a vibecoding session that felt more like a practical collaboration than a purely theoretical test.
My process started with a recruiter conversation that felt quick and easy. We went over general items about my profile, and I didn’t feel like it was an ordeal—just a straightforward early screen. After that, though, I noticed a pattern that made me uneasy: people I knew had similar experiences where the recruiter didn’t reliably follow up after the interview.
The initial recruiter conversation is generally friendly and straightforward, focusing on background and role alignment, but candidates have noted inconsistent follow-up and communication afterward, which can lead to frustration.
Candidates typically undergo a structured technical assessment that includes multiple-choice questions on computer science fundamentals followed by coding problems, often with a focus on data structures and algorithms, and some candidates noted the need for prior practice to meet expectations.
The coding sessions are described as collaborative and practical, with candidates working through requirements documents or live coding problems, which contrasts with traditional leetcode-style interviews, though the time constraints can add pressure.
Later stages often include behavioral interviews and discussions with leadership, focusing on fit and long-term thinking, which can vary in depth and structure, with some candidates feeling these rounds were less challenging than technical ones.
The interview process is generally structured with a clear progression from HR to technical rounds and then to leadership, but candidates have experienced varying timelines, with some noting delays and a lack of timely follow-up after interviews.
While the technical rounds are often described as standard, candidates have reported a high bar for performance, particularly in coding and theoretical questions, leading to a sense of needing extensive preparation to succeed.
