My interviews felt designed around practical engineering rather than the usual “memorize patterns” style coding. I had two coding rounds and then a system design round at a senior/staff level. One coding interview focused on finding flaws in existing code, which made it feel closer to real day-to-day work—reading and reasoning about a codebase, not just solving an abstract problem.
The other coding round had an expectation of both design and implementation, so it wasn’t purely “write the algorithm then stop.” Across the questions, I noticed they didn’t read like the standard LeetCode-style topics that many companies stick to, which surprised me in a good way. The overall difficulty felt high, and I didn’t end up getting an offer, but the process itself felt coherent and grounded in practical thinking rather than textbook exercise.
> 1 year
Average Negative United States
The timeline for me was brutal: I went through 6 rounds of interviews plus a case study, and then I waited about a month. I remember the pace shifting around the time of the wait, with the company mentioning a move of the team from Seattle to SF.
When I asked about whether the situation was fair, I wasn’t given a satisfying explanation. The response framed it as if I should think of it as just being rejected, even though I’d already invested through that long process. In the end there wasn’t an offer, and the biggest thing I carried out of it was the mismatch between how far the process went and how suddenly it stopped.
> 1 year
Easy Neutral United States
My process started with a 30-minute call with a hiring recruiter, then about a week later I had a 30-minute screen with the hiring manager. After that…
> 1 year
Average Neutral United States
My first step was a phone screen with the manager that lasted about 75 minutes. It combined technical and behavioral questions so it didn’t feel like …
> 1 year
Difficult Positive Los Angeles, CA
It took me a while to even hear back, roughly two months after applying online. When the recruiter reached out, the first conversation was a screen wh…
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
Candidates typically experience a multi-round interview process that includes initial recruiter calls, technical screens, and behavioral interviews, often spanning several weeks. The timeline can feel lengthy, with some candidates reporting waits of up to a month between rounds.
Interview roundsTimelineRecruiter call
Technical Evaluation Focus
The technical interviews emphasize practical engineering tasks rather than traditional algorithmic challenges, with candidates often engaging in real-world coding scenarios, debugging, and system design discussions. This approach aims to assess problem-solving skills in a collaborative environment.
Practical codingSystem designDebugging
Behavioral Interviews
Behavioral rounds often include questions about teamwork, communication, and cultural fit, but can also feature unexpected or less relevant questions that may catch candidates off guard. Candidates noted a mix of positive and confusing experiences during these discussions.
While many candidates appreciated constructive feedback during technical evaluations, some reported poor communication regarding outcomes, especially after take-home assignments or lengthy processes, which left them feeling unvalued or confused about their status.
FeedbackCommunicationTake-home assignment
Interview Difficulty & Outcome
Overall, candidates found the interview process to be challenging but fair, with a high level of difficulty reported across technical rounds. Despite the rigorous nature, many felt the experience was respectful, though not all received offers, leading to mixed feelings about the outcome.
Interview difficultyRespectful processOutcome
Candidate Preparation Insights
Candidates reflected on their experiences and expressed a desire to better prepare for the behavioral rounds and the unique technical challenges presented, emphasizing the importance of understanding the company's engineering focus and culture.