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 right into coding on a shared CoderPad session, with me writing the code while the conversation moved along. They left some time at the end for my own questions, and I also manually tested my solution instead of just assuming it would work.
Across my experience, the coding focus was strongly tied to data structures—linked-list style questions came up, with follow-ups that checked whether I really understood the details. The overall feel was more about doing the work in the moment and explaining as I went, rather than a lot of abstract discussion. I didn’t end up with an offer, but the interview didn’t feel adversarial; it felt straightforward, and the evaluation hinged on getting the implementation right with the follow-ups.
> 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…
> 1 year
Average Positive Mountain View, CA
I was approached by WhatsApp to interview through an on-campus round. Since I wasn’t available on campus, I arranged a Skype interview a couple of day…
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.