My journey for this role moved quickly through a recruiter call and then straight into a structured coding round. After the initial recruiter conversation (around 30 minutes), about a week later I did a “common coding” interview that mixed an explanation segment and a take-home component.
The take-home portion had a noticeable pacing: roughly 30 minutes were spent discussing the problem first. The prompt wasn’t something I could trace to LeetCode or HackerRank. After that, I had about 60 minutes for the take-home coding portion. I was able to complete only one of the two questions within the time limit, but I still explained my thinking on the second question, and my approach was correct based on what I understood.
5 months ago
Difficult Positive Oakland, CA
My process started with a Codesignal OA, and then I went into a technical screen, followed by a recruiter call. After that, the final stage was an onsite. Across the interviews, the tone felt difficult but not impossible, and I remember the expectation was that I could handle classic data structures and algorithms.
On the onsite, the final-round interviews included a behavioral component that was pretty typical situational questioning. The coding exercises focused heavily on traditional DSA, and a major theme was that I had to be able to explain runtime thoroughly, not just arrive at an answer. Some interviewers were nice, but a few came across as indifferent and didn’t offer much help if I got stuck or asked clarifying questions.
8 months ago
Average Positive Oakland, CA
I went through the new grad-style flow where the first step was an emailed take-home OA link. It wasn’t a LeetCode link; it gave me roughly 1–2 hours …
9 months ago
Average Positive United States
My process started like a lot of coding-heavy screens: a recruiter-like warmup didn’t stand out much, and then I hit a technical conversation that wen…
9 months ago
Average Neutral San Francisco, CA
After applying, I got pushed into a technical interview that was almost entirely about explaining problem-solving out loud. There weren’t behavioral q…
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 culminates in a lengthy onsite that can last several hours. Candidates should expect a structured flow with multiple rounds, often taking several weeks to complete.
Recruiter callTechnical screenOnsite
Coding Challenges & Technical Rounds
Candidates will face a mix of coding challenges that emphasize data structures and algorithms, often requiring runtime analysis and justification of solutions. Expect to encounter both live coding and take-home assignments, with a focus on medium to hard difficulty levels.
Data structuresAlgorithmsRuntime analysis
Behavioral Components
Behavioral interviews are included, often featuring situational questions that assess cultural fit and problem-solving approaches. Candidates should prepare to discuss their experiences and how they align with the company's values.
Interviewers place a strong emphasis on candidates' ability to explain their thought processes and justify their coding decisions, particularly regarding time complexity. Clear communication is crucial throughout the interview.
CommunicationJustificationTime complexity
Interview Environment & Tone
The overall tone of interviews tends to be friendly and supportive, although some candidates report mixed experiences with interviewer engagement. Expect a collaborative atmosphere, but be prepared for varying levels of interviewer responsiveness.
Candidates often report a lack of feedback following interviews, which can leave them feeling uncertain about their performance. It's advisable to seek feedback proactively, though responses may vary.