Skip to main content

Real Interview Experiences

Learn what to expect directly from candidates and interviewers who've been through it.

Updated 1 hour ago
Share your experience or upgrade to unlock access

Interviewed recently? Share your experience to try it free, or become a member for full access.

Nvidia
Senior Software Engineer, LLM Applications
Nvidia·Posted 1 month ago · Sep 2025

What stood out about Nvidia was how low level they went. I got the sense they don’t want you using a lot of these high level library functions, and implementing an entire transformer from scratch was honestly what helped me most.

Verified4 rounds6 questions
Read full interview
Google
Product Manager, Gemini
Google·Posted 1 month ago · Sep 2025

I’d never had to do vibe coding live before. In the product design interview, they gave me 10 to 15 minutes to actually build a rough prototype, and most of what they were probing on was how I prompted and reprompted the tool.

Verified5 rounds7 questions
Read full interview
Google
Software Engineer Intern
Google·Posted 1 month ago · Sep 2025

Google’s online assessment took me like 5 minutes and it was supposed to be 90, and that’s when I realized they really prioritize your interactions with the interviewer. You absolutely are not going to run any of your code, so if you don’t understand that landscape, you’re going to fail.

Verified4 rounds3 questions
Read full interview
Anthropic
Senior/Staff SWE, Inferencing
Anthropic·Posted 1 month ago · Aug 2025

The main thing is that Anthropic had a very small question bank. When I was interviewing, I already knew the system design question, and the coding questions were like five of them, which was kind of wild.

Verified7 rounds12 questions
Read full interview
ElevenLabs
Forward Deployed Engineer
ElevenLabs·Posted 1 month ago · Aug 2025

I passed the interviews and it was verbally confirmed, but when the process was finished they decided they only want to hire in SF. Even though I was open to moving, they saw some immigration risks that they didn’t want to continue.

Verified5 rounds4 questions
Read full interview
OpenAI
Research Engineer
OpenAI·Posted 1 month ago · Jul 2025

The coding plus ML stats round was the hardest by far. They basically asked me to implement an all_gather on noisy nodes, derive how many rounds you’d need for a target error, then figure out a better algorithm using the fact you’re transmitting floats.

Verified6 rounds1 question
Read full interview
Harvey AI
Principal MLOps Engineer
Harvey AI·Posted 1 month ago · Jul 2025

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.

Verified5 rounds1 question
Read full interview
Meta
Product Manager
Meta·Posted 1 month ago · Jul 2025

Culturally, they struck me as much more direct about conflict than my current company. The vibe was state your view, defend it with data, then move on. They also wanted every answer tied back to the company's mission of connecting people, even in the cases that seem far away from social products. I got the sense that internal visibility matters a lot there.

Verified8 rounds7 questions
Read full interview
Meta
Product Experience Analyst (IC6)
Meta·Posted 1 month ago · Jun 2025

The internal tooling and the data is incredible. When I was there last year, they had their own Meta AI wired into the most commonly used databases, so I could reference tables and column names and just prompt it to give me the query I needed.

Verified8 rounds
Read full interview