What a PM vibe coding interview tests and how to prepare
A handful of companies now ask PM candidates to build something working, with an AI coding tool, inside the interview. It is a new enough format that most advice about it is speculation, so here is what is actually being tested.
PMMockr.com
Quick Answer
A vibe coding interview asks you to build a working prototype during the interview using an AI coding tool, describing what you want in natural language rather than writing most of the code yourself. It is not a coding test. It tests whether you can scope something small enough to finish, judge whether the output is actually correct, and decide what to cut when time runs short.
Set expectations honestly
This format is new and not standardised. A minority of companies use it, implementations differ widely, and anyone describing a canonical structure is inventing one. Treat what follows as preparation for the underlying skill rather than for a fixed test.
What is actually being assessed
The artifact matters less than the decisions visible while you build it. Interviewers are watching how you narrow scope and how you react when the tool produces something wrong.
- Scoping: can you cut an ambiguous brief down to something completable in the time given.
- Verification: do you check whether the generated code does what you asked, or do you accept it because it ran.
- Prompting as specification: a vague instruction produces vague software, which is the same failure as a vague PRD.
- Recovery: what you do when the tool goes down a wrong path, which it will.
- Taste: whether the thing you chose to build was worth building at all.
How to practise
Give yourself 45 minutes and a deliberately vague brief, then build something demonstrable with whichever AI coding tool you have. Do it several times with different briefs. The reps teach the thing being tested: how much scope actually fits in the time, and how fast you notice when the output is wrong.
- Narrate your decisions out loud while building, since you will have to in the interview.
- Practise saying 'this is not working, I am cutting it' rather than sinking the whole session into one broken piece.
- Finish with something demonstrable every time, even if it is much smaller than you planned.
- Get comfortable reading code you did not write well enough to spot when it is wrong.
The trap
Candidates who can code often try to write it themselves and run out of time. Candidates who cannot code often accept the first output uncritically. Neither is what the format rewards. The skill is directing a fast, unreliable implementer and knowing when to stop, which happens to be a reasonable description of the job.
FAQ
What is a vibe coding interview?
An interview where you build a working prototype using an AI coding tool, specifying what you want in natural language rather than writing most of the code yourself. It assesses scoping and judgment, not syntax.
Do PMs need to know how to code for a vibe coding interview?
You need to read code well enough to tell whether the output does what you asked. You do not need to write it fluently, and trying to write it all yourself is a common way to run out of time.
How common are vibe coding interviews for PMs?
Still uncommon and concentrated at AI-forward companies and startups. The format is new and implementations vary a lot, so ask your recruiter whether it is part of your loop.
How do I practise for one?
Take a vague brief, set a 45-minute timer, and build something demonstrable with an AI coding tool. Repeat with different briefs until you can reliably judge how much scope fits in the time.