After an initial recruiter-style touchpoint, I was given a take-home assignment with about a week to complete it. The work wasn’t just “get it working”; it needed solid engineering hygiene like clean code and tests, and I ended up spending real time polishing the submission, including documentation, edge cases, and comments so it followed the stated guidelines. When I wrapped it, I didn’t immediately get a detailed debrief—what followed felt more like a gate than a discussion.
I then had a follow-up 1-on-1 tied to the assessment, but despite putting in the effort, I didn’t pass the take-home stage. In my feedback, the coordinator/recruiter messages were frustratingly generic and didn’t clearly map to what I delivered; they said the assignment didn’t meet the criteria even though I believed I had matched the requirements. The whole experience left me with the sense they were looking for something narrower than what was written, and I walked away disappointed because I’d invested days into it.
> 1 year
Average Positive Singapore
My interviews felt unusually clean and decisive. After HR got the ball rolling, I went through a sequence that mixed coding and discussion formats: I remember having a behavioral component alongside live coding and even a few rounds that touched on fit and motivation. The technical part was generally straightforward in tone—questions were approachable, and the interviewers explained what they were looking for rather than trying to trick me.
At one point, I was asked about the fundamentals for the role and how I’d work in a full-stack context, including technologies like Python and React, plus basics around databases and core computer science concepts. Other rounds leaned more on practical programming problems, where I worked through a codility-style task and then continued into live interviews. I also had at least one round that felt less purely technical and more like a department or leadership conversation.
> 1 year
Difficult Positive Singapore
My process started with an HR screening, and then I moved into the core technical part with a take-home that had a week deadline. After submitting tha…
> 1 year
Average Positive Singapore
My path started online and felt very assessment-heavy. I completed a timed online test with a set number of questions, and then I was asked to do an a…
> 1 year
Average Positive United States
My first step was an HR phone call that focused on personality fit and motivation. The conversation went through my background, what I was looking for…
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
Initial HR Screening
The interview process typically begins with a friendly HR screening focused on personality fit, motivation, and background. This stage is low-pressure and serves as an initial assessment of candidate alignment with company values.
HR screeningpersonality fitmotivation
Take-Home Assignment
Candidates are required to complete a take-home assignment with a week to submit, emphasizing clean code, documentation, and edge cases. Feedback on these assignments can be generic, leading to uncertainty about evaluation criteria.
take-home assignmentclean codefeedback
Technical Assessment Rounds
Following the take-home, candidates often participate in technical assessments that may include live coding, practical programming problems, and pairing sessions to extend their submitted work. The focus is on job-relevant skills and practical application.
technical assessmentlive codingpairing session
Assessment Variety
The process may include a variety of assessments, such as timed online tests, cognitive evaluations, and video interviews, which can feel assessment-heavy and structured as digital checkpoints rather than live interactions.
Overall, the interview tone is generally friendly and organized, with interviewers explaining what they are looking for rather than trying to trick candidates. However, the clarity of expectations may vary, leading to surprises in outcomes.
friendly toneorganized structureexpectations
Outcome and Feedback
Candidates often leave the process without an offer, with feedback sometimes lacking specificity, making it difficult to gauge performance and areas for improvement. Many express a desire for clearer evaluation criteria throughout the process.