After a recruiter screen, I had an hour-long technical interview with a LeetCode-style coding prompt. It felt like they were checking both whether I could solve the problem and how I reasoned step by step. A few days later, I went into a longer onsite session that ran about four hours, focused heavily on fitting in and also digging into technical thinking.
During that onsite, there was a behavioral/cultural fit component alongside a systems architecture question. What stood out was how interested they were in how I’d design something from the ground up—how I’d break down requirements, choose an approach, and work through tradeoffs while solving the problem. Overall the difficulty felt difficult and the process didn’t end with an offer, but it was clear they wanted a deep, structured way of thinking rather than just getting to a final answer.
> 1 year
Difficult Neutral United States
My process began as a more straightforward technical track: I did a standard on-site that ended up being four rounds. The coding portion ranged from hard to medium, and there were also system design questions mixed in across the interviews. The overall difficulty felt difficult, and by the end I was left with the sense that I’d done a real technical test rather than something casual.
What surprised me most wasn’t the difficulty—it was the silence afterward. After my interviews wrapped, I was effectively ghosted for about two weeks. No clear timeline, no update, and eventually there was no offer. Looking back, the most frustrating part was how long it took to get any closure, even if the decision was ultimately a rejection.
> 1 year
Difficult Positive United States
I went through a fairly direct coding-to-design sequence. First, there was a phone interview with a coding problem. Then I moved into four rounds of v…
> 1 year
Average Neutral Canada
I went through a three-round process that included an HR screen. After I received an email from HR, I scheduled a first phone screen. In the technical…
> 1 year
Difficult Neutral San Jose, CA
I received an interview invitation by email and then connected with the recruiter over Google Meet. The coding part happened in a shared coding pad, 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
Interview Structure & Timeline
The interview process typically starts with an HR screen followed by a technical phone interview, and then moves into a multi-round onsite or virtual interview focused on coding and system design. Candidates reported varying experiences with delays and lack of communication, leading to feelings of frustration and uncertainty about their application status.
HR screenTechnical interviewOnsite rounds
Coding & Technical Challenges
Candidates faced a range of coding problems, primarily LeetCode-style questions, with difficulty levels from medium to hard, often testing algorithmic skills and problem-solving abilities. The technical interviews were structured to assess both the final solution and the candidate's reasoning process throughout the problem-solving steps.
LeetCodeAlgorithmic problemsProblem-solving
System Design & Architecture
The onsite interviews included questions focused on system design and architecture, where candidates were evaluated on their ability to break down requirements, choose approaches, and discuss trade-offs in their designs. This aspect emphasized a structured way of thinking rather than just arriving at a solution.
System designArchitectureTrade-offs
Behavioral & Cultural Fit
Behavioral interviews were incorporated to assess cultural fit, with interviewers interested in candidates' motivations and past experiences. However, the tone of these interactions varied, with some candidates reporting negative or condescending experiences that impacted their overall impression of the company.
Cultural fitBehavioral questionsMotivation
Communication & Feedback
Candidates expressed concerns about the communication style during interviews, with some feeling that feedback was harsh or condescending, while others appreciated supportive guidance. The overall experience was affected by the interviewers' demeanor and the clarity of communication throughout the process.
FeedbackCommunication styleSupportive guidance
Outcome & Reflection
Most candidates did not receive offers, and many reported feelings of being ghosted or left without closure after the interviews. Reflecting on their experiences, candidates wished they had prepared differently or had clearer expectations regarding the interview process and outcomes.