Real Interview Experiences
Learn what to expect directly from candidates and interviewers who've been through it.
Interviewed recently? Share your experience to try it free, or become a member for full access.
“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.”
“I walked into this thing with 48 pages of prep, and that still barely felt like enough because at Amazon the first question is maybe 20% of the interview and the other 80% is them asking, 'How do you know that? Prove it.'”
“The recruiter literally told me the system design prompt was frequency capping, and even with that heads-up the real test was whether I could talk about ads like I actually live in that world. If you get the terminology half wrong, it feels like a red flag immediately.”
“The weirdest round was a HackerRank about arranging two football teams for a photo, and the interviewer basically admitted it was confusing on purpose. I left thinking I had definitely failed it, then still got pushed to finals.”
“The weirdest part for me was the AI coding round. They gave me a buggy maze class in HackerRank, made me use the built-in assistant, and then spent the back half probing why I trusted one AI-generated approach over the others.”
“What stuck with me was that Robinhood barely cared about classic DSA questions. Three of my four real rounds were system design, and every interviewer kept coming back to the same thing: what fails, what happens next, and how do you recover.”
“I expected the AI safety interview to be super guarded, but the engineer was actually really open about his views on regulation and what AI safety should mean. It ended up feeling more like a lunch conversation with a very opinionated engineer than a normal behavioral.”
“The wildest round was not system design. It was a cross-org interview with a cost management partner grilling me on how I would forecast host spend for an observability team, and I had not seen that anywhere else.”
“My hiring manager came back as part of the final loop and literally asked me zero interview questions. The whole 30 minutes was just, what questions do you have for me, which made it feel more like a sell call than an evaluation.”
“If I were doing it again, I would spend less time trying to grind every Uber-tagged LeetCode problem and more time on two things: their engineering blog and getting my behavioral framing right for staff.”
“I got all the way to the end for an L6 EM role, and the must-pass round was a 200-plus-line code review in a Google Doc where I had to manually debug broken interval logic with no IDE and no tools.”
