Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

7 stories

Likes earn the author +10 XP for the first 3 likes each day

ScaleProduct Manager
Reported Jul 2026

Scale Product Manager interview: AI product cases and fit

After a recruiter call, I entered a product-focused process that lasted several weeks. It combined behavioral questions with product-sense work. The work was AI-focused, and the cases asked for broad thinking with room to shape an approach. The live interviews involved several people and tested different aspects of my thinking. Some conversations were about product sense and design, while others…

Technical Screen0
ScaleSoftware Engineer
Reported Jun 2026

Scale Software Engineer interview: card-game coding exercise

The recruiting flow felt friendly at first, then the technical work proved unlike a standard LeetCode trick question. The coding prompt used a card-game theme and was more about implementing many conditions than finding an elegant idea. It moved through multiple cases, so I had to track the logic and states carefully. In the live coding round, I needed to work through those conditions quickly. Th…

Technical Screen0
ScaleSoftware Engineer
Reported Apr 2026

Scale Software Engineer interview with a time-pressured technical screen

My interview process was drawn out. It started well enough, but the ending left a sour feeling. I first had a recruiting call, followed by a technical screen after some preparation from the recruiter. The last part was the most exhausting. The final round was a loop with many interviews, and my experience varied by interviewer. Some seemed distracted or disorganized, which made the day feel longe…

RejectedTechnical Screen0
ScaleSoftware Engineer
Reported Apr 2026

Scale Software Engineer live coding interview implementing a card game

After I cleared an initial online assessment, my next step was a 60-minute live coding interview. I was surprised that it wasn't a traditional algorithm question. Instead, I had to implement a unique card game with enough rules to turn it into a real build exercise. I had to translate the problem into working code, and the time limit forced me to stay organized. I passed that round and moved into…

In progressOnline Assessment0
ScaleSoftware Engineer
Reported Mar 2026

Scale Software Engineer interview with many coding rounds and debugging

My process felt like an implementation marathon. I went through many coding-focused rounds, and it eventually became tiring and even boring instead of engaging. There were also behavioral and debugging rounds, and the debugging session was the most excruciating part for me. Some interviewers were good, but others turned off their cameras and stayed silent throughout the coding rounds. That made i…

Technical Screen0
ScaleMachine Learning Engineer
Reported Feb 2026

Scale Machine Learning Engineer interview: coding round followed by ML theory

After speaking with a recruiter, I went through a compact sequence: a manager screen, a coding round, and a final discussion focused on machine learning theory. The process felt broad and deep at the same time, which made it difficult to approach as one straightforward type of interview. Even when I felt comfortable with the technical parts, the theory discussion kept bringing me back to fundamen…

RejectedOther0
ScaleSoftware Engineer
Reported Jan 2026

Scale Software Engineer interview with practical frontend work

My interview path followed a fairly classic structure: a recruiter screen, a technical screen, and then meetings that expanded into onsite-style rounds. The technical portion included system design and practical problem-solving that combined algorithmic work with a frontend component, so it was more ambiguous than pure coding. The hardest part for me was figuring out what the interviewers expecte…

Technical Screen0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP