After a recruiter chat, I joined what felt like a pretty standard software engineering screen. It was essentially a LeetCode-style question, and the format was straightforward enough that I didn’t expect it to go the way it did.
I froze up during the interview and couldn’t get past the initial part of the screen. The interviewer was still kind and supportive, but I didn’t make it through about 20 minutes in, which at the time felt like a fairly normal cutoff.
3 months ago
Difficult Neutral United States
I started with a phone screening where the conversation focused on my experience and what I was looking for, mostly as a credibility check. After that, I had a video call with a software engineer.
During the technical conversation, I was asked a coding question involving nested dictionaries. The overall tone felt focused and practical, and the question itself was the main event.
6 months ago
Average Positive San Francisco, CA
My recruiter outreach kicked things off, and after a recruiter screen I moved into a coding round. The coding was LeetCode-style and medium in difficu…
7 months ago
Average Negative United States
I interviewed through recruiter and HR steps as part of the process, and what stayed with me wasn’t the technical evaluation—it was a conversation abo…
10 months ago
Average Positive United States
I came in via a referral, and the process started with a team match. The interview loop was fairly structured and step-by-step: first a 30-minute phon…
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
Initial Screening & Technical Assessment
The interview process typically begins with a recruiter screen followed by a technical assessment, often in the form of a LeetCode-style coding question. Candidates should be prepared for a focused, time-constrained environment where performance on this initial assessment can heavily influence progression.
Recruiter screenLeetCodeCoding assessment
Technical Interview Structure
Subsequent technical interviews often include a mix of coding tasks, system design discussions, and behavioral questions, with a strong emphasis on practical problem-solving and real-world applications. Candidates should expect to articulate their thought process and handle edge cases during these discussions.
System designBehavioral questionsReal-world applications
Interview Logistics & Scheduling
Candidates have reported mixed experiences with scheduling, including delays and cancellations that can lead to frustration and uncertainty about the process. Being proactive and flexible with scheduling can help mitigate some of these issues.
Scheduling delaysCancellationsFlexibility
Behavioral & Values Fit
Behavioral interviews often focus on cultural fit and alignment with company values, using a 'tell me about a time' format. Candidates should prepare specific examples that demonstrate their alignment with the company's mission and values.
Cultural fitValues alignmentSTAR method
Candidate Experience & Support
Overall candidate experience varies, with some reporting supportive interviewers and clear communication throughout the process, while others have encountered negative signals, particularly regarding accommodations. Candidates should be prepared for varying levels of empathy and support.
Many candidates noted a lack of feedback following interviews, which can lead to confusion about their performance. Candidates should be aware that even strong performances may not guarantee offers, and they may need to seek feedback proactively.
FeedbackOutcome uncertaintyProactive communication