Real, anonymous reports from people who interviewed for Software Engineer at Scale, newest first and distilled into what to expect across the loop.
My process started with a relatively friendly recruiting flow, and it quickly became clear that the technical portion wasn’t your typical LeetCode-style trick question. The main coding challenge was card-game themed, and it put me in “implement and handle lots of conditions” mode more than “derive something elegant.” I remember how the prompt pushed through multiple cases, which meant you basically had to walk through the logic carefully and cover all the states.
My interview process was fairly drawn out and, even when it started okay, the end of it left a sour feeling. I first went through a recruiting call and then a technical screen after some prep from the recruiter. The later part was the most exhausting: the final round was a loop with a lot of interviews, and my experience varied depending on the interviewer—some seemed distracted or disorganized, which made the whole day feel longer than it needed to.
The interview process typically begins with a recruiter call that serves as a fit check, followed by a technical screen that can vary in structure and difficulty. Candidates noted that some recruiters provided helpful materials, while others left them feeling ghosted or without closure.
Candidates faced live coding interviews that emphasized practical implementation over traditional algorithmic challenges, often involving unique scenarios like card games or task scheduling. The focus was on producing correct code quickly while managing multiple conditions and edge cases.
The final interview loop generally consisted of multiple rounds, combining technical and behavioral interviews, though the number of sessions and their engagement levels varied significantly. Some candidates found the experience exhausting due to inconsistent interviewer focus and organization.
Behavioral interviews aimed to assess cultural fit and communication skills, with some candidates appreciating the straightforward discussions about work-life balance and company culture. However, the clarity of expectations during these segments sometimes felt lacking.
Candidates reported mixed feelings about their overall experience, with some appreciating constructive feedback and supportive interviewers, while others felt the process was unprofessional or left them without clear outcomes. The inconsistency in interviewer engagement affected their confidence.
Candidates reflected on the need for thorough preparation, particularly for the unique coding challenges, and wished they had practiced more under time pressure. Many noted that the experience shaped their perception of the company, regardless of their technical performance.