My process started with a recruiter call, and after that I moved into a more multi-round onsite-style setup with multiple interviews. A couple of the conversations felt genuinely easy to connect with—the interviewers were engaged and it felt like they’d be good coworkers. The whole process still felt fair overall, even though it took a while to get through everything.
From there, things turned into a heavier technical run. After the initial recruiter screen, I did a set of technical interviews that blended discussion of how I approach daily engineering problems with coding-style evaluation. I remember having to slow down and actually talk through my reasoning process, not just arrive at an answer. I was also asked to reflect on my train of thought and how I would handle typical issues in the work.
4 months ago
Average Negative United States
I started with a recruiter phone screen where I mostly talked through my background, but I didn’t get much detail about the role or the team. After that, I had a live coding interview with an engineer, and it quickly turned unpleasant.
During the coding part, the engineer repeatedly suggested directions that were incorrect, and I had to spend time pushing back, explaining why the approach wouldn’t work, and steering the conversation back toward something viable. By the end, when I asked questions, the responses didn’t feel professional or respectful—there was a kind of casualness about the job and even statements that implied they didn’t particularly care.
6 months ago
Average Neutral United States
My first interaction was a recruiter screening call, and it set a weird tone immediately. The interviewer was standoffish and seemed uninterested in h…
6 months ago
Average Negative Santiago
I went through a pretty long hiring loop that felt out of proportion to the role and compensation. After an initial screening, I ended up doing a live…
7 months ago
Average Positive San Francisco, CA
After speaking with a recruiter about my experience and how I might align with the internal tool work, I got logistics and then an online assessment 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
Initial recruiter calls varied significantly in tone and effectiveness, with some candidates experiencing a friendly and informative conversation, while others felt standoffish or unprofessional. This inconsistency set the stage for the overall interview experience.
RecruiterCommunicationTone
Technical Screen
Candidates typically underwent a technical screen involving coding exercises that focused on practical engineering tasks rather than algorithmic puzzles, though the quality of the interviewers varied, affecting the overall experience.
CodingPractical TasksTechnical Evaluation
Onsite Interviews
The onsite interviews often included multiple back-to-back technical sessions that assessed coding, system design, and architecture, but the atmosphere could range from collaborative to hostile, impacting candidates' perceptions of the company culture.
OnsiteTechnical InterviewsCulture Fit
Communication & Follow-Up
Many candidates reported a lack of clear communication and follow-up throughout the process, leading to frustration and a sense of disrespect for their time, especially after extensive interviews.
CommunicationFollow-UpCandidate Experience
Interview Difficulty & Expectations
The difficulty level of interviews was generally high, focusing on real-world engineering challenges, but some candidates felt the expectations were misaligned with the job descriptions or their experiences, leading to confusion.
DifficultyExpectationsReal-World Tasks
Overall Experience & Closure
Candidates expressed mixed feelings about the overall experience, with some appreciating the structured approach while others felt it lacked respect and closure, often ending without meaningful feedback or resolution.