What stood out immediately was how long the process took. Each interviewer had their own separate call, so even though each conversation was standard-length, the overall interview experience stretched longer than I was used to. Despite that, I found it to be a reasonably cooperative and satisfactory process.
Across those interviewer calls, the focus stayed on the role and my fit for it. When I had questions—especially about what the work actually looked like and how the team operated—I felt like the interviewers were willing to engage and clarify instead of shutting me down.
9 months ago
Average Negative Austin, TX
I only got as far as the scheduling stage, and it was discouraging from the start. I was asked to provide my availability for an interview, and I replied immediately, then followed up since nothing happened.
After waiting, I effectively got ghosted—no response—and then weeks later I received a rejection without ever making it into an interview. The timeline and silence were what made it stick with me. I expected at least a clear communication loop, and instead it felt like I’d been left hanging until the end of the process.
> 1 year
Average Positive Gurgaon, Haryana
My process started with a phone reachout, and then the interviews fell into a pretty clear three-round rhythm. In the first technical round, I worked …
> 1 year
Average Positive San Francisco, CA
I went through a layered process that started with HR and then moved deeper into technical depth. First, the recruiter reached out, then I had a manag…
> 1 year
Average Positive United States
The recruiter stage set the tempo for a longer process. After initial outreach and coordination, I ended up going through multiple rounds of technical…
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 involves multiple rounds, starting with a recruiter screen followed by technical interviews that can extend over several weeks, leading to a full-day on-site session for some candidates. Candidates noted that the overall timeline can feel drawn out, with some experiencing significant delays in communication after interviews.
Multi-stageLong processDelayed communication
Technical Evaluation
Candidates faced a variety of technical assessments, including data structures, algorithms, and language-specific questions (primarily in Python, Java, and JavaScript), often in a live coding format. The difficulty level was generally described as medium, with a focus on practical problem-solving rather than theoretical trivia.
Coding testsData structuresAlgorithms
Behavioral & Fit Assessment
Interviews often included discussions about past projects and experiences, with interviewers seeking to gauge cultural fit and communication skills. Some candidates felt that the focus on personality and fit was as important as technical skills, particularly in early stages.
Candidate experiences varied widely in terms of the interview environment, with some describing a friendly and supportive atmosphere, while others reported feeling interrogated or unprofessional treatment. This inconsistency impacted overall candidate impressions of the company.
ProfessionalismInterview toneCandidate experience
Communication & Follow-up
Many candidates expressed frustration with the lack of clear communication throughout the process, particularly after interviews, leading to feelings of uncertainty and discouragement. Instances of ghosting or delayed responses were common, affecting candidates' perceptions of the company's professionalism.
Poor communicationGhostingUncertainty
Logistics & Coordination Issues
Several candidates encountered logistical challenges, including scheduling conflicts and miscommunication about interview formats or expectations, which contributed to a sense of disorganization in the hiring process. This was particularly noted during on-site interviews and travel arrangements.