Artist / Scientist / General Manager Spike
Hire PMs by which of three modes they spike in, and compose the team so the spikes cover each other.
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 4
- Confidence
- 85%
Rather than hunting for the mythical complete PM, Miller's interview question asks candidates to place themselves on three axes of the product craft — artist (creative, taste, vision), scientist (data, experimentation, rigour), and general manager (business, execution, stakeholders) — and say where they spike. There is no universally correct answer; the right hire depends entirely on the spikes already present in the team.
Origin
Nikita Miller's favourite product-manager interview question, shared in the lightning round. It is the hiring counterpart to her Roles and Responsibilities Contract: both start from the premise that no one human covers everything a PM is asked to be.
Core principles
- 01No PM is strong on all three modes; pretending otherwise produces bad hires and burnt-out people.
- 02The PM role is genuinely hard because you are expected to be competent across many areas all the time, have an answer, and stay calm — naming the spike relieves some of that.
- 03There is no ideal answer to the question; the correct answer is a function of your existing team's composition.
- 04Self-knowledge is the actual signal — a candidate who can locate their own spike understands the craft's shape.
- 05Team design is portfolio design: cover the three modes across people, not within one person.
How to run it
- 1
Map the spikes already on your team
Before opening a role, audit the current PMs: who is the artist, who is the scientist, who is the general manager? The gap in that map is your hiring brief.
- 2
Ask the candidate to self-locate
In interview, frame product as artist, scientist, and general manager, and ask: where do you spike? Listen as much for the quality of the self-assessment as for the answer itself.
Watch out Do not score this against a fixed ideal profile. Miller is explicit that the answer she wants totally depends on the composition of her team.
- 3
Hire to the gap, not to the archetype
Select the candidate whose spike complements the team's blind spot. A team of scientists shipping optimisations may need an artist; a team of visionaries with no rigour needs a scientist.
Pro tip Cross-check against the wider trend Miller observes: PMs are becoming more technical, designers more business-savvy, and engineers more product- and user-focused — the spikes are converging at the edges, so hire for depth, not for coverage.
- 4
Use the spike to bound the job once they're in
When a PM is drowning, don't problem-solve for everything at once. Acknowledge the role is genuinely hard, then focus on one of the many things being expected of them — ideally leaning on their spike.
Pro tip Miller periodically tells her PMs, with the core of her being, that she knows the job is hard. The acknowledgement is part of the mechanism.
In the wild
Asked whether she has a preferred answer to the spike question, Miller says it totally depends on the composition of her team — Lenny calls it 'a different triad'. The hire is a portfolio decision, not a search for the best individual on an absolute scale.
→ The team collectively covers artist, scientist, and general manager even though no single PM does.
PMs are expected to be competent across many areas all the time, to always have an answer, and to keep their calm. Miller's response when problem-solving with her PMs is to explicitly not solve for everything, and instead focus on one of the many things expected of them.
→ The PM works from their strength on a bounded problem instead of failing diffusely across all three modes at once.
Common mistakes
Looking for the unicorn who spikes on all three
Hiring against an ideal complete-PM profile guarantees disappointment and drives the 'expected to be competent across many areas all the time' pressure that makes the role so stressful.
Treating the question as having a right answer
There is no globally preferred spike. Grading candidates against a fixed favourite mode ignores the only variable that matters — what your existing team is missing.
Assuming technical depth is the new bar
PMs are trending more technical, and bootcamps or coding classes help — but Miller is explicit that it is not a requirement, and she isn't a technical PM herself. Screening on it as a gate filters out artists and general managers you may badly need.
Is it for you?
Best for
Product leaders hiring PMs into an existing team, and PMs trying to work out where to invest their own development.
Not ideal for
A first PM hire at a startup with no existing team to complement — there you likely need broad coverage over a deep spike.
From the transcript
“we think about product in the context of artist scientist General general manager where do you spike”
“totally depends on the composition of my team”
“there are a lot of expectations you're expected to be competent across many areas all the time you're expected to have an answer and you're…”
“helping them understand that I understand that and so when we're problem solving let's probably not solve for everything let's like focus on one of…”
“am not like a technical PM I don't have a tech background I think I've been doing it long enough at this point to to…”
From the episode
Driving alignment and urgency within teams, work-life balance, and the changing PM landscape
Nikita Miller (The Knot, Trello)