Real Interview Experiences
Learn what to expect directly from candidates and interviewers who've been through it.
- 1,326 experiences
- 314 companies
- 37 roles
- +207 added this month
Scale AINew Grad Software Engineer · L3“What stood out most was the interviewer straight up told me the culture at Scale is “pretty like 996,” which you usually never hear that openly. And the rounds were super speed focused, like two interval-style problems in one hour.”
Scale AIForward Deployed Engineer“The wild part was that they basically put me through the same bar as software engineering, then only later figured out whether I fit FDE.”
Scale AIProduct Manager · L5“Efficient interview process. Recruiter, then hiring manager, then interview loop. Interview loop consists of 4 interviws.”
Scale AIEngineering Manager · L6“the recruiter was very prompt and communicative. i wish the people doing the interviews were at the same level, sometimes they were very junior”
Scale AIDeployment Strategist · L3“During the technical interview round with the hiring manager, I had to share my screen and live SQL code. Make sure to verbally speak out loud.”
Scale AITechnical Program Manager · L5“Had good experience with both the recruiter and the hiring manager, but I was not prepared enough for this interview. ”
Scale AIForward Deployed Product Manager · L5“A thorough, well-structured process: recruiter screen, hiring manager screen, a take-home case, a virtual onsite of four rounds (product sense, bar raiser/culture, technical execution, ML fundamentals), and a final conversation with a senior product leader. The interviewers were friendly, engaged and clearly hands-on practitioners. Each round probed a different angle, so you get to show range. The recruiting team was responsive and gave candid feedback mid-process, which I appreciated. What didn't go as well was logistics near the end. A late-stage round was cancelled at short notice and rerouted to a different interviewer, who treated it like an early screen, so I wasn't sure what was left. With interviewers across time zones, some slots also fell late in my evening. I didn't get an offer. Looking back, the gap was answer length and audience awareness in the senior rounds, not technical depth.”
Scale AISoftware Engineer New Grad · L3“I was given a PDF of questions related to the card game. I was asked to choose a language, I chose Python, and then I had to write complex Python logic to simulate the Card game amongst 4 players. The logic was not that hard; what was hard was that we had to write a lot of code in a very short amount of time. The interviewer was very helpful and asked me to correct my mistakes pretty early, which saved me some precious time.”
Scale AIBizOps & Strategy“The process felt quite rigorous, with multiple stages and a lot of coordination involved. There were also periods where communication felt fragmented—for example, it took some time to hear back between stages, and one of the interviews started noticeably late. While everyone I spoke with was professional and engaging, more consistent communication throughout the process would have made for a smoother candidate experience.”
Scale AIRevenue Operations Associate · L4“The process was fairly straightforward, although the company at the time was very focused on hiring people with the right values. They had a specific "credos" round, with a long-time employee who's focused on making sure you exhibit their top values/credos. The take-home case study was relatively straightforward for someone with an analytical/finance background.”
Preview full access of other recent interview experiences
AnthropicSoftware Engineer, Safeguards · L5“The weirdest Anthropic round was the company values interview. It was almost like a therapy session, and honestly if you went to a therapist at some point, you will pass that round much more easily.”
NetflixEngineering Manager, Tooling“What was very unusual is they didn’t give me any tooling to draw the system design, so I just sketched it on a piece of paper and talked them through it, then we got into this oddly deep debate about whether hover-over history should count as a recommendation signal.”