The recruiter screen set a rough tone for me right away. I came in for a backend engineering role and, from the start, the conversation felt overly transactional—like we were ticking boxes instead of talking about the kind of technical impact I’d been delivering.
When I shared concrete examples from past work—architecture decisions, optimizations, and the actual engineering scenarios—I expected the discussion to connect back to what matters for a backend role. Instead, the recruiter brushed past the details and focused on rigid, generic checklist questions. The call ended with a dismissive comment about having a huge volume of candidates to shortlist, which made the whole experience feel more like sorting than assessing.
4 months ago
Average Neutral San Francisco, CA
My process was pretty straightforward and followed a classic sequence: a recruiter screen first, then a technical screen, and then an onsite. At the onsite, I went through system design and behavioral rounds, plus a laptop coding interview. Depending on the day, I either did or didn’t end up interacting with the manager of the team I was being considered for during the behavioral portion.
The coding side was very OOD-flavored and felt like they were testing how I structure problems in code rather than just arriving at an answer. The system design conversation was a real back-and-forth where we designed a hypothetical system and weighed tradeoffs. The behavioral round was run by someone from a separate team and focused on standard bar-raise style questions.
5 months ago
Difficult Neutral United States
I started with a recruiter process that quickly led into a technical phone screen. What caught me off guard—in a good way—was that the interview asked…
8 months ago
Average Positive Ciudad de Mexico
My process was relatively simple from my perspective. I only went through a Byteboard-style interview, and it felt better than doing standard LeetCode…
8 months ago
Average Negative United States
After I cleared the early phone screen, I ran into scheduling and communication issues that dragged the process out in a way that felt disrespectful. …
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 Screen
The initial recruiter screen often feels transactional and focused on generic checklist questions rather than a deep evaluation of the candidate's background or technical impact. Candidates reported feeling that their experiences were not truly assessed, leading to a somewhat dismissive atmosphere.
RecruiterTransactionalChecklist
Technical Phone Screen
Candidates typically face a technical phone screen that includes coding challenges, often with a focus on algorithm and data structure problems. The difficulty can vary, with some candidates finding the questions harder than expected, which can lead to quick eliminations.
Technical ScreenCoding ChallengeAlgorithms
Onsite Interviews
The onsite interviews are structured and include multiple rounds such as system design, coding, and behavioral interviews. Candidates noted that the interviews require switching between different types of thinking and can be intense, but they generally felt organized and reflective of their abilities.
OnsiteSystem DesignBehavioral
Coding Challenges
Coding challenges vary in format, with some candidates experiencing traditional LeetCode-style problems while others faced more practical, project-based assessments. The pressure during these rounds is significant, and candidates often need to articulate their thought processes while coding.
CodingLeetCodeProject-Based
Communication & Scheduling
Candidates reported mixed experiences with communication and scheduling, with some facing delays, cancellations, and a lack of clear feedback after interviews. This can lead to frustration and a feeling of disrespect for their time, especially if the process drags on.
CommunicationSchedulingFeedback
Outcome & Team Matching
Even after successfully completing interviews, candidates often faced uncertainty during the team matching process, with some not receiving offers despite passing all rounds. This aspect can leave candidates feeling confused about their standing and the overall hiring intent.