My process ended almost immediately. After the initial intro call, the recruiter came across as defensive and sarcastic, and honestly they leaned on jargon in a way that didn’t feel constructive. I left that conversation not wanting to continue.
That initial impression wasn’t just minor friction—it felt like a genuine mismatch in professionalism, and I decided to opt out rather than carry on. Looking back, what stuck with me was how little trust I could build from that first interaction.
> 1 year
Average Positive Seattle, WA
I started with a recruiter conversation that immediately set a clear tone for the rest of the process. They didn’t just talk about the role in vague terms; they communicated expectations and timelines up front, and every step after that felt similarly organized. I appreciated that I always knew what was coming next and why.
> 1 year
Easy Negative United States
Right at the beginning, the scheduling experience was a mess. After I got a first call scheduled, the recruiter flaked on the initial meeting, and the…
> 1 year
Difficult Positive United States
After the earlier rounds, I hit a take-home coding stage that had a very tight deadline—roughly a day—and it was supposed to be answered live in front…
> 1 year
Average Positive Bangalore Rural
My interview experience was fully online and moved through a pretty straightforward sequence. After an initial screening round, I got into a coding ro…
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 Recruiter Interaction
Candidates experienced a mixed bag during the initial recruiter conversations, with some feeling that the recruiter was defensive and unprofessional, while others appreciated clear communication about expectations and timelines. This initial interaction sets the tone for the rest of the process.
RecruiterExpectationsProfessionalism
Scheduling & Communication Issues
Several candidates reported significant scheduling problems, including missed calls and lack of follow-up, which contributed to a sense of unreliability in the process. This can lead to frustration and uncertainty about the next steps.
SchedulingCommunicationReliability
Coding & Technical Rounds
The interview process includes multiple coding sessions, often requiring candidates to solve problems live, which can be intense and demanding. Candidates should be prepared for hands-on coding challenges that test their ability to produce executable code under pressure.
CodingTechnicalLive Coding
System Design Interviews
Candidates can expect to engage in system design discussions that start with basic architecture and evolve into considerations for scaling and trade-offs. This round assesses both technical knowledge and strategic thinking.
System DesignArchitectureScaling
Behavioral & Values Interviews
Interviews often include discussions focused on behavioral aspects and alignment with company values, which can vary in depth and format. Candidates should be ready to articulate their experiences and how they align with the company's culture.
BehavioralValuesCulture Fit
Feedback & Communication Post-Interview
Candidates frequently expressed dissatisfaction with the lack of constructive feedback and communication after interviews, particularly in cases of rejection. It is advisable to seek clarity and follow up for feedback to improve future applications.