After a recruiter call, my process kept stretching. The early conversations didn’t feel totally in sync—one recruiter call had the camera off the whole time, and the schedule ended up getting delayed for weeks. Eventually I got the next round on the calendar and it moved forward, even though I’d already felt some uncertainty about momentum.
The first real technical step was a live coding exercise. The prompt leaned into object-oriented design with an algorithmic angle, and I ended up implementing a hashing-based solution. It wasn’t just “write code and stop”—the way it was framed felt closer to designing an approach for the problem than memorizing a single LeetCode pattern.
3 months ago
Average Negative United States
My experience started with a recruiter screen that quickly soured my confidence in the process. The recruiter called late to our scheduled HR conversation, and I remember it even shifted into a salary discussion when I thought we were just doing standard behavioral topics. I tried to stay responsive, but I got stuck waiting on follow-ups.
After the HR stage, the scheduling and communication became the main problem. I was repeatedly pinged to complete a coding challenge that I hadn’t signed up for yet because I was waiting for the recruiter to clarify next steps, and eventually neither recruiter contact nor the scheduling updates came through the way they said they would. I ended up feeling like I was being left hanging and then fully ghosted.
3 months ago
Average Positive Los Angeles, CA
My interview started with a fairly standard sequence: a recruiter chat, then a hiring-manager conversation, and then a technical round with an enginee…
10 months ago
Average Positive United States
The process began with paperwork before anything else—I had to sign an NDA right before the recruiter first round. That recruiter interview was on Zoo…
10 months ago
Difficult Positive Seoul
My interview process leaned heavily on structured technical evaluation. After the initial recruiter screen, I went into a coding assessment and then a…
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
Recruiter & Initial Communication
Candidates often reported issues with recruiter communication, including delays, lack of follow-up, and disorganization, which contributed to uncertainty about the process. Some found the initial recruiter calls to be casual and focused on background rather than technical skills.
The technical rounds typically involved live coding exercises that emphasized problem-solving, object-oriented design, and secure coding practices, with a mix of algorithmic and practical engineering questions. Candidates noted a collaborative environment during coding sessions, but some experienced challenges due to the interviewers' expectations and communication styles.
Live codingObject-oriented designSecure coding
Onsite Experience
Onsite interviews were generally structured with multiple sessions, including technical and behavioral components, often in a relaxed atmosphere. However, candidates reported feeling overwhelmed by the number of interviews and a lack of clarity on decision-making processes afterward.
Many candidates expressed frustration over the lack of feedback and follow-up after interviews, leaving them uncertain about their performance and the reasons for not receiving offers. This silence contributed to a negative perception of the overall experience.
Lack of feedbackFollow-up issuesCandidate experience
Technical Bar & Expectations
Candidates noted a high technical bar with an emphasis on clean design and engineering judgment, often feeling challenged by the interviewers' reactions to their problem-solving approaches. Some found the expectations to be inconsistent, leading to confusion about what was required to succeed.
Technical barEngineering judgmentProblem-solving
Cultural Fit & Social Dynamics
The interview process included a focus on cultural fit, with some candidates feeling that social interactions were heavily weighted in decision-making. Positive interactions with interviewers contributed to a more comfortable experience, while awkward dynamics could detract from performance.