Field Notes · Elle Anderson · andersonco.uk

Product leadership interviews: FAQs and how-tos

Frequently asked questions and working methods for Head of Product, VP Product, and CPO loops, written from both chairs: I have sat the candidate side across financial services, retail, healthcare, and consumer goods, and I have designed and run these loops as the hiring leader. Companion piece to Product sense, the way Meta grades it.

FAQs

How is a product leadership loop different from a PM loop?

Craft becomes table stakes and the org becomes the product. A PM loop asks whether you can find the right problem and ship the right solution. A leadership loop assumes you can, and asks whether you can build a system of people, decisions, and funding that does it repeatedly without you in the room. Every answer you give gets read at that altitude: not "what did you decide" but "what did you build so the decision gets made well next time".

What rounds should I expect?

The common shape: a recruiter screen, a hiring manager conversation, a product sense or craft round calibrated up, a leadership and org design round, an execution and metrics round, one or two cross-functional partner interviews (usually engineering and design, sometimes commercial), and an exec panel. Increasingly there is also a case presentation or a take-home. Ask the recruiter for the loop shape and what each round scores; a good recruiter will tell you, and the question itself signals you know how loops work.

Do senior candidates still get product sense rounds?

Yes, and skipping preparation for them is the most common senior-candidate mistake I see. The prompt is the same as a PM would get; the bar is different. You are expected to move through the spine faster, show taste rather than coverage, and connect the answer to portfolio and organisational consequences a PM would not be asked about. The interviewer wants to see that fifteen years in, the muscle is still warm.

How do I answer "tell me about a product you're proud of"?

At leadership level this is not a feature story, it is a systems story with a product inside it. Name the commercial or customer outcome first, in a number. Then the judgement calls: what you bet on, what you refused, what evidence changed your mind. Then the people: who you grew, what capability outlasted you. A strong answer makes the interviewer want to work for you, not just with you. Keep two versions ready, one at three minutes and one at ninety seconds, because panels steal time.

How do I talk about failure?

Pick a real one with money attached, not a humble-brag about perfectionism. Structure it like a blameless review: the decision as it looked at the time with the information you had, the signal you missed or dismissed, what it cost, and the mechanism you changed so the class of failure got harder to repeat. The last part is the answer; the rest is setup. Leaders who cannot name a changed mechanism have not finished learning from the failure, and panels can tell.

What is the exec panel actually scoring?

Judgement under ambiguity, clarity of thought at speed, and whether they can imagine you disagreeing with them productively. Execs rarely score your framework; they score whether the room felt sharper with you in it. Answer in conclusions first, reasoning second, detail on request. If you disagree with a premise in the question, say so respectfully and early; agreeable candidates are forgettable candidates at this altitude.

How do I answer "what would you do in your first 90 days"?

Do not promise a reorg, a new strategy, or quick wins you cannot know exist. The credible shape is listen, diagnose, bet: the first month meeting people and reading the artefacts that never lie (the roadmap versus what shipped, the funding model, the last three things killed), the second forming a diagnosis and testing it with the leadership team, the third placing one or two visible bets that the diagnosis justifies. Name what you would deliberately not touch yet. Restraint reads as seniority.

What questions should I ask them?

Ask questions that diagnose the organisation while showing product sense: how does an idea become funded work here, what was the last thing you killed and how did that feel, where does the strategy live and who can recite it, what does this role own that the CEO currently owns. Their answers tell you whether the job is real; your questions tell them you would know what to do with it. Never waste a question on something the careers page answers.

The title says Head of Product, but the scope sounds like a Director. How do I read levels?

Titles compress badly across companies, so interrogate scope instead: team size and shape, budget ownership, who sets strategy versus who executes it, and what the role's seat at the exec table actually is. Ask "what decisions does this role make alone, and which does it recommend?" early, because the answer changes how you should pitch every subsequent round, and a mismatch discovered at offer stage wastes everyone's month.

How-tos

How to prepare in two weeks

Build a story matrix before you rehearse anything: eight to ten real stories down one axis, the scored signals across the other (strategy, org design, talent, delivery, influence, failure, commercial outcome), and tick which stories evidence which signals. Fill the empty columns; those are the questions that will hurt. Then rehearse out loud, timed, with someone who will interrupt you, because panels interrupt. Finally, warm up the product sense muscle with the prompt bank, one per day.

How to build the portfolio narrative

A leadership career is not a list of jobs, it is an argument. Write the one-sentence thesis of your career first (mine leads with data science and ML products since 2018, and the realities beneath the aspiration), then arrange your proof so each role advances the argument. Cut anything that does not. When your CV, your LinkedIn, your answers, and your questions all argue the same thesis, panels experience you as coherent, and coherence gets hired.

How to run the case presentation

Treat the brief like a product sense prompt with slides: problem before solution, a chosen segment with a stated rationale, bets with kill criteria, and a final slide that says what you would do next Monday. Ten slides maximum, one idea per slide, a third of the time reserved for discussion, because the discussion is the interview; the deck is just the fuse. Bring one deliberately contestable choice and defend it warmly. A presentation nobody argues with scored nothing.

How to handle the take-home

Time-box it visibly: state on page one the hours you spent and the assumptions you made, because unbounded effort signals poor judgement, not commitment. Answer the question asked, then add one paragraph they did not ask for that shows the altitude of the role, usually a note on what you would need to learn before trusting your own recommendation. If the take-home would take more than a working day, it is extracting free consulting; it is fair to say so and propose a scoped version.

How to close the loop

Send the follow-up the same day while the room still remembers you, and make it useful rather than grateful: one sharpened thought on something discussed, in three sentences. Prepare references before you need them, and brief each referee on the thesis of your candidacy so their story and yours rhyme. If you are rejected, ask for the signal that was missed; some loops will tell you, and it is the cheapest coaching you will ever get.

For hiring leaders: how to run a loop worth its signal

Everything in the interviewer's rubric from the product sense piece applies doubly at leadership level, because the cost of a vibes-based hire is a whole organisation's morale. Write the signals down before opening the role, assign each round an owner and a non-overlapping question set, score independently in writing before conferring, and give the case presentation a real internal problem rather than a hypothetical, with an NDA if needed. And check your loop against the health check first; interviewing candidates for an operating model you have not fixed selects for people who interview well inside broken systems.