I went through a new-grad style loop that felt oddly opaque. It was OA first, then a phone screen, and finally a voice interview. The bar was hard to read, because I didn’t feel like I was getting consistent signals about what would “count.”
During the phone step, my submitted code wasn’t even fully functional, yet I still made it through. By the time I reached the voice interview, my code and explanations felt solid—I didn’t think I made any mistakes, even verbally. Still, I ended up rejected, and that mismatch between how it felt and the final decision was what stuck with me most.
5 months ago
Average Negative United States
My process started with a phone interview that the recruiter scheduled, then kept moving around. They shifted it earlier than the original time, then pushed it later multiple times, always with less than a day’s notice.
What really threw me off was that the day of the interview came, but the recruiter no-showed without notifying me. I was left hanging and, after that, the process simply didn’t feel reliable at all.
6 months ago
Average Positive Vietnam
I moved through a pretty tight three-round sequence: an OA, then an HR chat, and then a final round. The timeline felt fast and the recruiter side fel…
6 months ago
Easy Neutral United States
My interviews focused mostly on general problem-solving, with algorithmic design questions rather than classic LeetCode-style problems. The overall vi…
7 months ago
Average Positive New York, NY
My path started with an OA on CodeSignal, which was straightforward enough to complete. After that, I had a technical interview and then a final round…
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 begins with a recruiter screen, followed by an online assessment (OA), and then progresses through multiple technical rounds, often culminating in a final onsite or deep dive interview. Candidates noted variations in the number of rounds and the pacing, with some describing a tight sequence while others experienced delays and disorganization.
Recruiter screenOnline assessmentTechnical rounds
Technical Assessment Focus
Technical interviews often include coding questions that emphasize problem-solving and algorithmic design rather than traditional LeetCode-style problems. Candidates should be prepared for a mix of coding challenges and system design discussions, with some interviews requiring a deep dive into previous projects.
Coding questionsSystem designAlgorithmic design
Behavioral Interviews
Behavioral interviews are a key component of the process, often occurring alongside technical assessments. Candidates should be ready to discuss their experiences and approach to collaboration, as these conversations are designed to evaluate cultural fit and communication skills.
Behavioral questionsCultural fitCollaboration
Candidate Experience & Engagement
Candidates reported mixed experiences regarding interviewer engagement, with some feeling that interviewers were disinterested or distracted. A positive interaction can significantly impact a candidate's perception of the process, so candidates should be prepared to navigate varying levels of interviewer enthusiasm.
Many candidates expressed frustration over a lack of feedback after interviews, which left them feeling uncertain about their performance and the outcome. It's advisable for candidates to seek clarity on the feedback process and to express their interest in receiving constructive criticism.
FeedbackClosurePost-interview communication
Overall Difficulty & Expectations
The overall difficulty of the interviews varied, with some candidates feeling the bar was unclear or inconsistent. Candidates should prepare for a rigorous evaluation but also be aware that the perceived difficulty may not always align with the final decision.