What's being asked right now, at any company, for any role.
36,206 experiences·1,663 added this week
Software Engineer
The first round is completed. It was entirely oral, with questions on basic Java concepts, JWT authentication, SOLID
Product Manager
Prod managament case on azure, intro questions Brightwave Database Migration Tool – Product Management Case You are a
The interview process had three rounds, and my first interview was a one-hour coding session in C++. I was asked to
Quantitative Analyst
The question I still think about is the one about designing the interface between a trading system and an exchange,
The part I keep replaying isn't the coding problem. It's the hour I spent trying to get a straight answer from the
Data Analyst
I went through an interview process that included three case studies, each lasting one hour and conducted by three
AI Engineer
I got a rejection after the first round, where the HR asked both motivational and technical questions around AI
Software Engineer, Security Product
I went into this loop expecting three parts: system design, a domain-specific interview, and a behavioral round. The
My Roblox experience was entirely the online assessment, and I didn't get past it. It had five parts. Two were
There were four rounds, and the last one is where I'd spend the most prep time. It started with a standard recruiter
There were two main rounds, and both were pretty different. The first was Experience & Goals, which was more of a
The part I didn't expect was the online assessment. Alongside the standard coding problems, it included game-based
Software Development Engineer
My Amazon SWE loop in late 2026 was two interviews, and both leaned on LeetCode-style coding. Each interview had about
What stood out most to me was how little of my process involved a whiteboard. The first hurdle was a HackerRank online
ML Engineer
I gave the technical screening round, which included a few ML fundamental questions and 1 LC medium level coding
I completed a 30-minute, six-question online assessment. The business scenarios felt pretty manageable, but the time
Data Scientist
Recruiter screen, after that it's 1 hours of interview that consist of 30 min analytical design, 30 min case question,
I had a single technical phone screen, about 45 minutes long, built around a problem with three parts. I got too caught
I went into Cisco expecting a grilling and ended up with something closer to a long technical conversation. The process
L4 Frontend Engineer
Going in, I'd heard the usual advice to grind LeetCode, but the problems I got didn't come from there. Google wrote