Real Interview Experiences
Learn what to expect directly from candidates and interviewers who've been through it.
- 1,326 experiences
- 313 companies
- 37 roles
- +207 added this month
Harvey AIPrincipal MLOps Engineer · L8+“I ended up pitching this quantum ML architecture where we were training models on quantum hardware to do something as stupidly simple as predict whether a number was even or odd, and Harvey’s panel got weirdly fascinated by the remote coding environment I built for physicists.”
Harvey AIProduct Manager · L6“I interviewed for a PM role on Harvey's collaboration team in August 2026. I had one interview round and did not receive an offer. The interview was entirely behavioral. The interviewer asked about my background, why I wanted to work at Harvey, what I was proud of, and a product I had built. For the product discussion, I walked through a recommendations product I built, covering the business case, technical details, and go-to-market approach. The questions I remember were: "Why Harvey?", "What are you proud of?", and "Walk me through a product that you built." It was a straightforward conversation about my experience rather than a product case or technical exercise.”
Harvey AISoftware Engineer · L5“You need to be really fast at coding as question has multiple parts and follow ups. so practicing coding in your own language is really important”
Harvey AISecurity Engineer · L7“overall a good experience with the onsite at harvey's offices, one nit since this role is a founding trust engineer role, the interviewers and the panel did not have real experiences with auditors and bigger security frameworks, so the questions were orthogonal to my experience.”
Similar interview experiences
Sierra AIAgent Strategist“The agent design round was a live whiteboard: a new customer wants a cancellation agent, so map out the user journey and every system it needs to plug into.”
PalantirForward Deployed Infrastructure Engineer · L3“In the learning round they taught me one of their products from scratch, then kept adding constraints. They expected me to reason through it like I was already on the team.”
OpenAISoftware engineer“I still can’t tell if the final twist had a right answer, or if it was a test of how I handle something nearly impossible.”
StripeEngineering Manager · L6“What stuck with me was how fast it got into management judgment, like straight up asking if I'd actually managed a low performer and what makes someone staff in my eyes.”
AmazonSoftware Development Engineer, Level 4 · L3“It was the usual four-round AWS loop, but the HM actually spent time on how I use GenAI to fast track my workflow, and the Bar Raiser was basically all LPs with tons of follow-ups.”
GoogleSenior Software Engineer · L5“It was basically the most by-the-book Google loop possible: shortest path in a DAG, minimum meeting rooms, then a news feed design where they kept pushing on fanout, storage, and ranking.”
“My first technical round wasn’t with a person. An AI interviewer ran the whole thing, from logistics questions to reviewing my code line by line.”
MindbodySoftware Developer III · L5“The weirdest round was basically a PR review for an order-messaging system where I had to spot bugs and explain how I'd structure it so a Kafka-to-SQS switch later wouldn't turn into a rewrite.”
GoogleStaff Software Engineer · L6“The system design wasn’t generic. It was built around the team’s actual work: an AI agent that lets enterprise users search and query their data and documents.”
PalantirForward Deployed Software Engineer (Commercial)“You can’t treat coding and communication as separate skills here. Even after my code was right, they asked why I chose that approach and how I’d explain the trade-off to someone non-technical.”
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.”