I applied online and then did an online assessment. After I passed, recruiting invited me to schedule the next interviews, and the whole thing felt pretty organized. I got a scheduling email with prep resources, including an overview video of the interview process plus links to an official interview kit.
My first scheduled round was a 1-hour technical interview with a Software Engineer II on CodePair. The session was recorded for training/quality, and I had the option to opt out. During the interview, AI tools weren’t allowed, and I was told to check with the interviewer if I needed to look anything up. The coding part felt like the usual LeetCode-style set—mixing a couple of algorithmic topics (like heaps and DFS) with some multiple-choice questions earlier in the OA. I didn’t find anything wildly surprising; overall it felt like a straightforward technical evaluation.
2 months ago
Easy Positive United States
I came in through a referral, and the initial call felt more like a conversation than a gatekeeping screen. The process moved quickly overall—within about two and a half weeks I had both a technical coding round and a behavioral interview.
On the coding portion, I was asked two things: find the first non-repeating character in a string, and validate a set of parentheses. Midway through, I realized I’d practiced something very similar on PracHub right before—so the format and patterns felt familiar, and that helped me stay calm.
2 months ago
Average Negative United States
My process started normally enough: I applied online and a recruiter reached out a couple of weeks later to set up a technical phone screen. What made…
2 months ago
Average Positive New York, NY
I was actually in the interview process for the Full Stack Software Engineer Intern role, not the general software engineer track. Early on, I complet…
2 months ago
Average Positive London, England
The process heavily involved the kind of coding challenge that’s become well-known—what I got was the driver-delivery style system problem. I also kep…
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 begins with an online assessment, followed by a technical coding round and then a series of interviews that may include behavioral and system design discussions. The overall timeline is often quick, with candidates receiving timely updates after each stage.
Candidates can expect multiple coding rounds focused on data structures and algorithms, often using platforms like HackerRank or CodePair, with questions that are commonly discussed online. The difficulty level can vary, with some candidates reporting a competitive programming style that demands strong fundamentals.
Coding roundsDSAHackerRank
Use of AI Tools
Some interviews allow the use of AI tools during coding challenges, which can influence how candidates approach problem-solving. However, this practice varies, and candidates should be prepared for both scenarios.
AI usageCoding toolsProblem-solving
Behavioral & Cultural Fit
Behavioral interviews are a part of the process, focusing on candidates' experiences and cultural fit within the company. The atmosphere during these interviews tends to be collaborative rather than adversarial, allowing candidates to express themselves comfortably.
For more senior roles, candidates may encounter system design interviews that assess their ability to architect scalable solutions. These discussions often require a deep understanding of system architecture and trade-offs.
System designArchitectureScalability
Feedback & Outcome
Candidates often report a lack of detailed feedback after rejections, which can leave them uncertain about their performance. However, many express appreciation for the clarity and professionalism of the communication throughout the process.