Skip to main content

Real Interview Experiences

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

Updated 9 hours 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.

Anduril
Software Engineer (New Grad)
Anduril·Posted 4 days ago · Apr 2026

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.

Verified5 rounds4 questions
Read full interview
LinkedIn
Senior Software Engineer, Apps
LinkedIn·Posted 4 days ago · Apr 2026

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.

Verified3 rounds6 questions
Read full interview
Robinhood
Senior Software Engineer
Robinhood·Posted 4 days ago · Apr 2026

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.

Verified5 rounds4 questions
Read full interview
OpenAI
Software Engineer (New Grad)
OpenAI·Posted 4 days ago · Apr 2026

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.

Verified3 rounds4 questions
Read full interview
Uber
Staff Software Engineer (L5B), Ads
Uber·Posted 4 days ago · Apr 2026

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.

Verified7 rounds6 questions
Read full interview
Microsoft
Software Development Engineer II
Microsoft·Posted 4 days ago · Apr 2026

In my binary tree round, I was not even leaning on BFS or DFS terminology, and they still liked my solution because I kept reasoning it out. That was the moment where Microsoft felt more about logical thinking than memorized interview patterns.

Verified5 rounds5 questions
Read full interview
Google
Software Engineer (L4)
Google·Posted 4 days ago · Apr 2026

My strongest Google round was with a senior interviewer who never opened a LeetCode prompt. He just asked what I knew about algorithms, pushed me into distributed merge sort from first principles, and apparently got more signal from that than a standard coding screen.

Verified6 rounds11 questions
Read full interview
Stripe
Software Engineer (New Grad)
Stripe·Posted 1 month ago · Apr 2026

When they wrote that one column depends on another, I pretty much immediately jumped to cycle detection and modeled it as a graph. There was a lot of reading involved, but the solutions themselves were mostly brute force and straightforward.

Verified2 rounds1 question
Read full interview
Lyft
Software Engineer T3
Lyft·Posted 1 month ago · Apr 2026

The process wasn’t as long as I expected. My onsite was supposed to be four rounds, but they cut it to just two, and one of them was a time-based key value store with delete at a specific timestamp given in the full spec up front.

Verified4 rounds2 questions
Read full interview