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
McKinseyData Scientist · L4“The technical round is the hardest to crack.”
McKinseyBusiness Analyst · L3“The process was structured and fairly demanding. After the initial application, I completed the Solve assessment and then had two rounds of interviews. Each interview had two main parts: a Personal Experience Interview (PEI), where the interviewer went deep into a specific leadership/impact experience, and a case interview based on a client problem. The cases tested structuring, quantitative analysis, interpreting exhibits, brainstorming and synthesizing a recommendation. The final round followed a similar format but was with more senior interviewers and felt a bit more conversational and open-ended. What went well was that the process was very consistent with the preparation materials McKinsey provides, and the interviewers were engaging and gave me room to explain my thinking. I also received useful feedback between rounds. The biggest challenge was the intensity of the PEI — interviewers go much deeper into one story than in a typical behavioral interview — and some of the cases were less standard than the ones I had practiced. Overall, though, I thought the process was well organized and gave a good sense of the actual problem-solving style at McKinsey.”
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.”