My process started with a recruiter call, then it moved pretty quickly into multiple technical rounds: a technical screen, two live coding rounds, a system design discussion, and a behavioral/hiring manager conversation. The overall structure felt like it was testing both implementation and how I reasoned about bigger design tradeoffs, not just whether I could get to a working answer.
In the coding portion, I ran into algorithm questions that leaned on data structures and complexity—one round centered on graphs, and I also had to think through system-level architecture. A theme across the sessions was that they wanted clear reasoning about time and space, and I could feel the difficulty ranging from intermediate to hard. There was also a platform-combination vibe to the technical work where I wasn’t only coding algorithms in isolation; I had to understand how the platform pieces fit together.
7 months ago
Difficult Neutral New York, NY
After my CV got through, I ended up going only as far as a technical screening and it felt brutal. The question was very LeetCode-style and it was with someone currently on the team. I remember thinking I had to be extremely sharp to make it through, because the problem didn’t leave much room for struggling.
The bigger issue wasn’t just the difficulty—it was the experience around the session. In one of the screens the interviewer was late by more than five minutes and didn’t really engage, including not responding when I tried to clarify definitions. In the other experience, the recruiter coordination was what really soured the process: even after the virtual onsite, a scheduled follow-up phone call was set for a late hour in my timezone and never happened, and I never got a timely response to follow-ups. On top of that, the onsite setup was chaotic, with multiple participants given different meeting links, so I lost interview time just trying to find the right room.
7 months ago
Average Neutral London, England
Right after my CV was accepted, I got a CodeSignal-style assessment with a clear prompt: label Tetris blocks by assigning different values to differen…
> 1 year
Average Neutral San Francisco, CA
My interviews were pretty concentrated technically: first a shorter screen, then a longer live coding round where I mostly had to drive the process. I…
> 1 year
Average Negative Tokyo
My interview loop took more than a month and felt disorganized from the start. I went through a first coding round, then a second online coding interv…
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 a recruiter call, followed by a technical screen and multiple technical rounds, including coding, system design, and behavioral interviews. The overall timeline can range from a few weeks to over a month, with some candidates experiencing disorganization and delays.
Recruiter callTechnical screenInterview timeline
Technical Assessments
Candidates often face a series of technical assessments that include live coding challenges, online assessments, and take-home projects, focusing on data structures, algorithms, and system design. The difficulty level is generally high, with many candidates reporting a mix of easy to hard questions across different rounds.
Live codingOnline assessmentData structures
Behavioral Interviews
Behavioral interviews are a component of the process, often occurring towards the end of the interview loop, where candidates are assessed on their past experiences and fit within the company culture. The interviews generally aim to be supportive, but the level of engagement from interviewers can vary.
BehavioralCultural fitSTAR method
Communication & Coordination
Several candidates reported issues with communication and coordination throughout the interview process, including delays in scheduling, lack of timely feedback, and unresponsive recruiters. These factors contributed to a frustrating experience, overshadowing the technical evaluations.
Communication issuesRecruiter responsivenessScheduling delays
Interview Difficulty & Pressure
Candidates described the overall difficulty of the interviews as high, with a strong emphasis on performance under time constraints. Many felt that the pressure to deliver correct solutions quickly was a significant aspect of the experience, impacting their performance and confidence.
Time pressureDifficulty levelPerformance under stress
Candidate Reflections
Many candidates reflected on their experiences, wishing they had better prepared for the specific types of questions asked, particularly around algorithms and system design. Some noted that they felt the evaluation criteria were not always clear or aligned with their performance.