My process had a simple shape: a recruiter screener, a hiring-manager conversation, and then a technical round. The hiring-manager round was anchored in my resume, and I got questions that asked me to walk through how I handled specific problems—how I’d resolved them and what I did to improve performance after the fact.
After that, the next step was a technical interview stage focused on evaluating my skills rather than expanding on my background. It felt like they were trying to connect my past work to the kind of engineering decisions I’d be making day to day.
4 months ago
Average Positive United States
After a recruiter phone screen, about a week later I went into a coding assessment with a set of prompts that felt pretty hands-on. The next stage was a behavioral conversation with directors, where the questions were more about how I’d worked through real situations rather than trick puzzles. If I passed that, the process moved into an onsite session that was structured like a longer technical work block.
Onsite, I had a frontend portion built around Vue, where I implemented a small feature set for a simple todo flow—adding tasks, marking them complete with a checkbox, and filtering by task name. Then I switched to a backend portion where I had to get unit tests to pass. It was very test-driven: I worked through three unit tests that involved pulling data from a database, iterating through results, and processing the data through API calls. Overall it felt practical and focused on correctness.
5 months ago
Average Neutral Bengaluru
I applied through a LinkedIn referral and then had to repeat parts of the application flow, including filling out an application form again. Shortly a…
6 months ago
Difficult Neutral Hong Kong
My process included a written test that was run by remote control during a Zoom session with an interviewer. That setup was genuinely tricky because o…
7 months ago
Average Positive Australia
My process felt structured and thorough, and the people I spoke with were generally nice. I started with a phone screen, then moved into a first techn…
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 screen, followed by a technical assessment, and then multiple interview rounds that can include behavioral and technical discussions. Candidates noted that the timeline can be tight, with quick transitions between stages, which may lead to a sense of urgency.
Candidates faced a variety of technical assessments, often emphasizing core computer science fundamentals, Java proficiency, and problem-solving skills under time constraints. The assessments included coding challenges and theoretical questions related to data structures, algorithms, and system design.
JavaData structuresCoding challenges
Behavioral & Cultural Fit
Behavioral interviews were common, focusing on past experiences and interpersonal skills rather than purely technical knowledge. Candidates reported that these discussions often centered on how they handle real-world situations and their alignment with company values.
Behavioral questionsCultural fitPast experiences
Technical Depth & Complexity
The technical interviews often required a deep understanding of concepts such as OOP, multithreading, and database management, with some candidates feeling that the expectations were quite high. Specific niche knowledge was also a common theme in technical discussions.
OOPMultithreadingDatabase management
Interview Environment & Communication
Candidates reported mixed experiences regarding the interview environment, with some noting that the atmosphere could feel disorganized or impersonal, particularly in remote settings. Clear communication from HR was also highlighted as a significant factor affecting overall experience.
Many candidates expressed disappointment in the lack of feedback following interviews, especially after investing significant time in the process. The outcomes often left candidates feeling uncertain about their performance and the reasons behind the final decisions.