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.”
“The biggest surprise was that the data science round went deeper than some engineering screens I’ve done. They were asking me about golden datasets, AI eval guardrails, and even precision and recall formulas in a PM interview.”
“The weirdest round was a principal engineer asking me to design an AI bot for ordering employee lunches. I went in expecting cloud infrastructure and Go, then suddenly I'm trying to talk through prompt behavior and architecture without getting lost in the terminology.”
“Rehearsing your take-home top-down isn't actually that helpful. There were so many curveballs thrown in the middle of the jam session that it would be almost impossible to just read a script and go slide to slide — you need to be on the tip of your toes.”
“The weirdest part was that the take home was basically the job. I had to build a semantic search setup over Amazon products for ChatGPT, then walk that same solution back to the team because that is basically what they work on.”
“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.”
“Google told me each round mapped to a specific rubric, but in reality the interviewers just asked whatever they wanted, and my so-called Googliness and execution round turned into Google Photos design plus a geospatial strategy curveball.”
“The "why" is so important. As an FDE, you have to learn to explain why your work matters — why it helps the customer, why it helps the business, and why it was the right approach.”
“I prepped for a normal EM system design, and then they put half an Anthropic inference design on the screen and asked me to tear it apart. That was when I realized they cared way more about design judgment and team guidance than whiteboard theatrics.”
“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.”
