After the recruiter reached out through LinkedIn, everything moved quickly. I ended up scheduling the HR conversation and was interviewed the very next day. The HR screen was friendly and focused on my background—mainly aligning with the engineering role I was interested in and walking through what I had already written on my resume, plus a short self-introduction.
A day or so later, I went into the user-related round. The interview felt accommodating and professional, with clear questions and a warm tone from the interviewer. Overall, the process felt systematic and respectful of my time, even though it didn’t turn into an offer for me. What stood out most was how polished and well-managed the experience felt, from the initial outreach through the scheduling and the actual interviews.
5 months ago
Easy Positive Ho Chi Minh City
My interview experience felt lighter in scope and more “intern-style,” but still technical. I started with coding questions that leaned toward CS fundamentals and practical algorithmic work, including an explicit focus on things like ML algorithms. There was also a live coding component where I had to write and reason through the solution in real time.
Even with the easier overall difficulty, the interviews weren’t just plug-and-play. I got asked multiple questions about my background—past employment and experience came up, along with career growth—and the interviewer treated the conversation as a two-way discussion rather than a single-shot test.
6 months ago
Average Positive Jakarta
My process started with an HR call where we mapped my interest to the kind of engineering work I wanted to do—like frontend, backend, or mobile. That …
7 months ago
Average Positive Bengaluru
The way I got pulled into the interview process felt more like a traditional pipeline. I first went through resume shortlisting, then an OA stage with…
8 months ago
Difficult Positive Petaling Jaya
I went through a sequence that felt intentionally strict and time-constrained, starting with a Codility-style live session where I had to pass all tes…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically starts with a recruiter call, followed by a structured sequence of technical rounds including coding, system design, and behavioral assessments, often culminating in an HR discussion. Candidates noted that the timeline was generally steady, with clear expectations for each stage.
Recruiter callTechnical roundsHR discussion
Coding & Algorithmic Assessment
Candidates experienced live coding sessions focused on data structures and algorithms, often using platforms like Codility or LeetCode-style questions, where they were expected to explain their thought process while coding. The difficulty varied, but many found the coding rounds to be manageable yet still demanding.
Live codingData structuresLeetCode
System Design Interviews
System design interviews were a significant part of the process, requiring candidates to discuss architecture, trade-offs, and real-world applications of their designs. These discussions often went beyond high-level concepts to include specific details relevant to the role.
System designArchitectureTrade-offs
Behavioral & Culture Fit Rounds
Behavioral interviews focused on cultural fit and past experiences, often involving discussions about teamwork, project management, and engineering principles. Candidates were encouraged to articulate their thought processes and decision-making strategies.
Behavioral questionsCultural fitTeamwork
Candidate Experience & Tone
Overall, candidates described the interview environment as professional and respectful, with a mix of accommodating and challenging interactions. However, some reported instances of unclear expectations or judgmental attitudes from interviewers, which affected their experience.
ProfessionalismRespectfulInterview tone
Feedback & Communication
Several candidates expressed frustration with the lack of feedback and closure after interviews, noting that communication could be slow or absent, particularly after technical rounds. This left some feeling uncertain about their performance and the overall process.