After a short recruiter call (about 15 minutes), I moved into a technical screen using BlueJeans and CoderPad. They gave me one or two pretty general algorithmic problems and I coded through the solution live with the interviewer on the call, picking the language I wanted. At the end, there were a few “surprise” technical questions that were simpler but still sharp—things like naming data structures and talking through time complexity for an algorithm.
The process then became a full loop, grouped into four interviews. One focused on technical/coding, another leaned into cross-functional collaboration, a third was troubleshooting, and the last one was more general around career expectations. What stood out was how much support the recruiter provided as the rounds approached—lots of help and prompts for practice across all four conversations. I still ended up doing an extra coding interview because the hiring manager wanted to be extra sure after the full loop.
> 1 year
Average Neutral United States
I had an in-person 90-minute interview with an engineer after reaching out through a recruiter. The interview itself went through that full length, and when the wait ended, they told me a few days later that I wasn’t selected. It wasn’t described in detail, but the pacing made it feel like the decision was based on how the full conversation went rather than anything that could be quickly clarified afterward.
> 1 year
Easy Positive United States
I interviewed in a live coding format where it felt like we jumped straight into the work. The interviewer introduced themselves and then we went righ…
> 1 year
Average Neutral Menlo Park, CA
I went through an interview process that felt centered on coding and structured enough to leave me wondering what they expected. In one coding round, …
> 1 year
Average Neutral United States
My process started with an online coding exercise after I sent my resume, with a one-hour window. The prompt was centered on linked list work—things l…
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
Recruiter Interaction & Support
Candidates generally found the recruiter to be supportive and communicative throughout the process, providing helpful prompts and practice resources ahead of interviews. However, some candidates experienced long delays or lack of follow-up, leading to frustration.
Recruiter supportCommunicationFollow-up
Technical Coding Screen
The initial technical screen typically involved live coding on platforms like CoderPad, focusing on algorithmic problems and data structures, with candidates expected to explain their thought process and handle follow-up questions about their solutions.
Live codingData structuresAlgorithmic problems
Interview Loop Structure
The interview process usually consisted of multiple rounds, often including a mix of technical, behavioral, and collaborative discussions, with some candidates experiencing an additional coding round for further assessment after the main loop.
Interviews heavily emphasized data structures, with many candidates reporting questions related to linked lists, trees, and other fundamental concepts, often requiring detailed explanations and debugging during the coding sessions.
Linked listsData structuresDebugging
Onsite Interview Experience
Candidates who reached the onsite stage reported a more intense experience with multiple back-to-back interviews covering a wide range of topics, including system design and networking, which often felt unpredictable and challenging.
Onsite interviewsSystem designNetworking
Overall Difficulty & Feedback
The overall difficulty of the process was perceived as high, with candidates often unsure if they met expectations; feedback was sometimes vague, leaving candidates unclear about their performance and outcomes.