My experience started with a recruiter interaction that didn’t move as quickly or clearly as it should have. After an initial phone interview, it took almost three weeks to schedule the next round. With no updates and no response, I had to send follow-up emails just to get a schedule, and even then the recruiter replied with it almost a week later. I also felt like I wasn’t given enough information about what to expect for the first round.
When the next interview happened, there was a communication disconnect with the interviewer, and the technical exercise felt mismatched. I was handed a Java application to debug even though I was applying as a JavaScript developer. The scheduled hour ran long to about an hour and a half, and it was stressful mainly because I didn’t feel properly guided ahead of time.
> 1 year
Difficult Positive Dallas, TX
After I was referred after a director of engineering reviewed my profile, the process started with an HR conversation about my current career and interest. Not long after that, I had a LeetCode-style medium problem scheduled as a coding round.
Once that was done, I moved into three back-to-back technical rounds: system design, a debugging/coding focused round, and another LeetCode hard challenge. The topics felt very range-y—less about a single trick and more about how I thought through problems when the stakes were higher. After the technical portion, there was a behavioral round, and then the decision.
> 1 year
Average Positive United States
My process felt pretty organized from the start. I had an initial tech screen that lasted about an hour, and then I went through a virtual onsite with…
> 1 year
Difficult Positive Canada
The process felt smooth overall, mostly because the recruiter got back to me quickly and the team worked under a short deadline. I started with an ini…
> 1 year
Easy Negative San Francisco, CA
I went through a surprisingly low-tech process where I mostly talked with people who felt like future teammates and managers—an internal recruiter, a …
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 & Communication
Candidates frequently reported mixed experiences with recruiter responsiveness and clarity, with some experiencing delays and a lack of updates throughout the process. This inconsistency can lead to frustration and uncertainty about the next steps.
RecruiterCommunicationResponsiveness
Technical Screening Process
The technical screening typically includes a mix of coding challenges, debugging exercises, and system design questions, with a focus on real-world problem-solving rather than purely theoretical questions. Candidates should be prepared for both live coding and take-home assignments.
Coding ChallengeDebuggingSystem Design
Onsite Interview Structure
The onsite interviews are generally structured and can be intensive, often lasting several hours with multiple back-to-back rounds. Candidates should expect a variety of technical evaluations and behavioral interviews to assess both skills and cultural fit.
OnsiteStructuredBehavioral
Interview Difficulty & Expectations
Candidates described the interview difficulty as variable, with some facing challenging problems under tight time constraints, which can lead to a sense of pressure. It's important to manage expectations regarding the intensity and nature of the questions asked.
DifficultyTime ConstraintsPressure
Behavioral & Cultural Fit Evaluation
Behavioral interviews often focus on cultural fit and collaboration, with interviewers looking for alignment with company values. Candidates should be prepared to discuss their past experiences and how they relate to the company culture.
BehavioralCultural FitValues
Post-Interview Feedback & Closure
Many candidates expressed disappointment regarding the lack of feedback or closure after the interview process, with some feeling left in the dark about their performance and the reasons for not receiving an offer. It's advisable to seek clarity and follow up if feedback is not provided.