The Teach-Me-Something-In-One-Minute Interview
A 60-second timed teaching exercise scored on completeness, complexity, and clarity
- Difficulty
- Starter
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 95%
Salva's icebreaker interview question for early- to mid-career product managers: teach me something new in one minute, timed on his phone. Candidates get a moment to choose, then the clock runs. Answers are scored on three explicit criteria — completeness (did they finish inside the minute), complexity (was the thing they chose non-trivial), and clarity (did the interviewer actually learn it). It tests scoping, judgment about what's worth an audience's attention, and the ability to convey an idea fully — the core product-communication skill — in a format short enough to use as a warm-up.
Origin
Ryan Salva's own PM interview practice at Microsoft and GitHub, used as an icebreaker rather than a stress question.
Core principles
- 01Timebox forces scoping — the candidate must fit the idea to the container, which is what PMs do
- 02Letting the candidate pick the topic reveals their judgment about what deserves attention
- 03Score on named criteria, not vibes, so answers are comparable across candidates
- 04The three axes trade off against each other: a complex topic is hard to complete, a complete one is easy to make trivial
How to run it
- 1
Set the frame as a warm-up, not a trap
Introduce it as an icebreaker: 'teach me something new in one minute.' Let the candidate know it's fun rather than adversarial so you're measuring communication, not stress response.
- 2
Give a beat to think, then start a visible timer
Pull out your phone, give them a second to choose their topic, then start the timer in front of them. The visible clock is part of the exercise — the constraint has to be real.
Watch out Don't let them ramble past the minute; the boundary is the test.
- 3
Score completeness
Did they actually finish the lesson inside the minute, or did the clock cut them off mid-idea? Failure here is a scoping failure.
- 4
Score complexity
Rate the ambition of what they chose to teach. Teaching you to pat your head and rub your stomach is trivial; teaching you 18th-century art and its connection to the religious trends of the time is not.
Pro tip Complexity is a signal of self-assessed confidence — a candidate who picks something hard is telling you what they think they can land.
- 5
Score clarity
Ask yourself honestly whether you learned the thing. Did they convey the idea fully and wholly, or did they just perform expertise at you?
Watch out Clarity is the axis candidates most often lose on when they over-index on complexity.
In the wild
A university candidate from Vanderbilt taught Salva about 18th-century art and its connection to the religious trends of the time — inside one minute, completely, and clearly enough that he still cites it as his benchmark answer.
→ It was an extremely strong yes hire, and it remains Salva's example of what a maximum score on all three axes looks like.
Salva contrasts the strong answer with a candidate teaching him to pat his head and rub his stomach at the same time — complete and clear, but scoring near zero on complexity.
→ Demonstrates why the three criteria are scored separately: an answer can be perfectly delivered and still tell you nothing about the candidate's judgment.
Common mistakes
Assigning the topic yourself
Half the signal is what the candidate chooses to teach. Prescribing the topic destroys the judgment test and leaves you only with delivery.
Scoring on a single impression
Without the three named axes, you conflate a charming delivery with a substantive one. Score completeness, complexity, and clarity separately.
Using it as a hard screening question
Salva deploys it as an icebreaker for early-to-mid-career PMs. Treating it as a gate over-weights a novelty format against candidates who are strong but not performative.
Is it for you?
Best for
Hiring managers screening early- to mid-career product managers, or anyone who needs a fast, comparable read on communication and scoping judgment
Not ideal for
Senior/executive hires or deeply technical roles where domain depth, not communication under a timebox, is the binding constraint
From the transcript
“So I ask them to teach me something new”
“in 1 minute. And it's all usually like I'll pull up my my phone and I'll like start the timer. I'll give them a second…”
“Clarity is like do I actually understand I learn something by the end of the lesson. Did they convey the idea fully and wholly?”
From the episode
The role of AI in product development
Ryan J. Salva (VP of Product at GitHub, Copilot)