After a recruiter call, I had about a week before the next step, which was a technical screen. It was a live coding session on Coderpad where I worked through a LeetCode-style problem. The platform feel was very “solve it live while the clock is running,” and I remember focusing hard on getting to a correct solution rather than trying to make it fancy.
Then I moved to a hiring manager round that lasted around an hour. That conversation was anchored in my background—what I had worked on and how I approached the kind of project they were hiring for. The questions were tied to my current experience and the specifics of the work I’d already described.
4 months ago
Easy Negative United States
My experience started with a hiring manager conversation, and it immediately felt off. I was asked to walk through my experience, but as soon as I began describing projects she wanted a different project from my resume. I tried to adjust, but she came across impatient and kept interrupting instead of letting me finish.
As the call went on, I felt increasingly uncomfortable—like I was losing my footing mid-answer and being pushed to talk only on very specific prompts. The vibe was irritated the whole time, not collaborative. By the end, I was already convinced I wouldn’t want to work under someone who spoke to candidates that way, even though I still answered questions.
5 months ago
Average Positive Palo Alto, CA
I went through a fairly structured sequence for a fullstack role. After the earlier steps, the process included a frontend-focused round, then a hirin…
8 months ago
I went through a compact two-round process for a Senior Software Engineer role, and it ultimately ended in a rejection. The first step was an online a…
8 months ago
Average Neutral San Francisco, CA
My first interaction was an AI-based round that felt jarringly different from a normal recruiter screen. The timer was set to 20 minutes, and it cut m…
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 then moves into multiple rounds including hiring manager discussions and onsite interviews, which may involve a mix of technical and behavioral assessments.
Recruiter callTechnical screenOnsite interviews
Technical / Coding Screen
Candidates can expect a live coding session, often using platforms like CoderPad or CodeSignal, where they will solve LeetCode-style problems under time constraints, focusing on correctness and coding style.
Live codingLeetCodeTime constraints
Behavioral & Values
Behavioral interviews are common, focusing on candidates' past experiences and how they align with the company's values, with some interviewers emphasizing collaborative discussions over strict questioning.
Expect rounds that assess low-level design (LLD) and high-level design (HLD) skills, where candidates may be asked to think through system architecture and design principles, often with specific language constraints.
System designLow-level designArchitecture
Interview Environment & Communication
Candidates reported varying experiences with interviewer engagement and communication clarity, with some feeling rushed or disrespected, which impacted their overall impression of the process.
Feedback can be inconsistent, with some candidates receiving prompt and detailed responses while others felt left in the dark after interviews, leading to a lack of closure regarding their performance.