After a recruiter screen on Microsoft Teams, I moved into a pretty standard series of follow-ups that felt heavily shaped around my background and resume. The recruiter walked through the role and reviewed my resume, and the questions stayed focused on basics like what I’d done before and what I could bring to the team.
The next part of my process leaned even more into “tell me about yourself / what’s on your resume”-type discussion. I ended up doing multiple interviews that were mostly straightforward behavioral and background questions, and I also had an on-site element where the final conversation with a director was framed more as an opportunity for me to ask things back. Even when the conversations were friendly and the interviewers seemed knowledgeable, the overall bar didn’t feel like it turned into an intense coding gauntlet.
7 months ago
Average Neutral United States
My interviews were relatively compact and centered on gauging fit through a couple of technical conversations grounded in my resume. I started with an initial screening round that was more of an interest gauge, then moved into a deeper dive afterward. Both of those were with system engineers and lasted about thirty minutes each, with the questions tied closely to what I’d already worked on.
When I later went through another similar flow, it began with a recruiter screen and then moved into technical discussions with two software engineers. The technical questions were directly linked to my C++ and data structures knowledge, and I had another technical round afterward that I didn’t make it through—so the process stopped right as the difficulty was escalating. In another interview sequence, the recruiter call went well and the engineer interview focused on resume and experiences, then included basic system design prompts and even a straightforward verbal coding question.
10 months ago
Easy Positive United States
My interview started with HR and then moved directly into leadership-style conversations. I had an initial HR interview to kick things off, then a hir…
> 1 year
Average Neutral United States
My process followed a pretty layered path that combined behavioral, technical, and some design/system thinking. I started with a recruiter conversatio…
> 1 year
Average Positive United States
My process stretched out with a lot of back-and-forth scheduling, and that made it feel more arduous than it needed to be. I went through a multi-stag…
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 & Flow
The interview process typically begins with an HR screen, followed by a series of technical and managerial interviews. Candidates noted that a clear sequence helped them feel more comfortable and informed throughout the process.
Technical interviews often include coding questions, system design prompts, and discussions related to candidates' resumes, with a mix of straightforward and challenging problems. Some candidates reported unexpected question formats that felt misaligned with their expectations.
Behavioral interviews are common and focus on candidates' past experiences and cultural fit, often using a conversational style. This aspect is generally perceived as friendly but can vary in intensity and depth across different interviewers.
Candidates frequently experienced delays and lack of clarity in communication throughout the interview process, leading to frustration. Many reported receiving generic rejections without personalized feedback, which affected their overall impression of the company.
Communication delaysFeedbackRejection process
Scheduling Challenges
Scheduling and coordination issues were a common theme, with candidates facing multiple reschedules and unclear timelines. These logistical challenges often detracted from the overall interview experience, regardless of the interview content.
While many candidates found the interviewers to be knowledgeable and friendly, the overall experience was mixed due to inconsistencies in process execution and follow-through. Positive interactions were often overshadowed by logistical frustrations and lack of closure.