Fit and behavioral questions

Why are you leaving, 5-year plan, strengths and weaknesses

Lesson 19 of 45~10 min read
In this lesson7 sections

An unofficial lesson drawing on the methods in the Define Yourself chapter of Cracking the PM Interview by Gayle Laakmann McDowell and Jackie Bavaro (2014). PracHub is not affiliated with the authors or publisher. Buy the book

Why you're leaving, where you'll be in five years, and your strengths and weaknesses all test the same things: whether you'll be honest about yourself and whether this job fits where you're headed. Each has a few predictable ways to fail, and candidates mostly hit them because they never said their answer out loud first.

We'll follow one candidate through all of them. Nadia spent four years as a PM at Kestrel Stays, an invented vacation-rental booking site, where she worked on the tools hosts use to set their prices. In March, Kestrel merged her team into a central pricing group and her role was cut. She's now interviewing at Fernline, an invented campground-booking marketplace, for a PM role that owns the tools campground owners use to set nightly rates. Another PM owns the fees Fernline charges campers.

What the interviewer is listening for

These questions usually come early and sound like small talk. Three checks sit behind them.

The first is candor: will you say something unflattering about yourself without being cornered? The second is self-knowledge. A PM who can't describe their own habits will struggle to describe a user's. The third is fit. The company wants you to stay long enough to repay the months it takes to get good, so it listens for goals it can't meet and hints that you'll leave soon.

Strengths: what this job needs, with proof

Choose strengths by reading the job, not your self-image. Fernline's posting talks about pricing experiments, campground owners and seasonal demand. Nadia also set up Kestrel's partnerships with travel agents, but Fernline has no agent channel, so that story stays home.

A strength is a claim, and a claim needs proof. "I'm very analytical" gives the interviewer nothing to write down. One specific skill and a short story ending in a visible result gives them a note for the debrief.

That test, what an interviewer can write down, is why intelligence never makes the list. "Says she's smart" isn't evidence in a debrief. The interviewer forms that view from the rest of the hour, so claiming it only makes you sound pleased with yourself.

Here's Nadia's lead strength, out loud:

"I'm good at setting prices from booking data nobody trusted. At Kestrel, stays of a week or more were 11% of searches but only 5% of bookings, and nobody could say why, because relisted homes were counted twice. I spent two weeks with an analyst cleaning the records. Long-stay guests converted at about half the rate on listings with no weekly discount, so I proposed turning on a 10% weekly discount for every host by default, with a switch to turn it off. In an eight-week, two-region test, bookings of a week or more rose 18%, and 85% of hosts kept it on."

That runs under a minute: the skill in one sentence, then the mess, what she did, and two numbers.

Have three strengths, each with its own story. Lead with the same one in every round, so the people deciding hear it from more than one interviewer (see how hiring decisions are made), and keep the other two for prompts it doesn't fit. Nadia's others: explaining a price change to hosts so it doesn't feel like a trick, and designing tests that hold up when demand swings with the season. A story bank keeps them in one place.

A weakness that is real, with the habit that contains it

The weakness question often comes dressed differently: "What's an area you're working on?" or "What feedback have you acted on?" To find one that rings true, start where someone has already told you: past performance reviews, peer feedback, the notes from a retro that went badly. Feedback someone else gave you is also easier to believe. Nadia's came from her review a year ago: she defaults to consensus.

Test it before you lead with it. It's true, it has cost you something you can name, it isn't the skill this job lives on, and you can show your fix working. It also can't give them a reason to distrust you: for Nadia, nothing that would make Fernline wary of letting her change what campground owners charge. Hers passes: Fernline's role lives on booking data and pricing tests, and her flaw shows up on the rarer calls that split several teams.

A strong answer has four parts. Name the flaw in plain words. Give one time it cost something. Say what good comes with the trait, honestly. Then describe the habit or system that keeps it from costing as much now, with some sign that it works.

Nadia's, built out:

"On contested calls, I keep looking for agreement long after I should just decide. On the weekly-discount change, finance worried about margin and support worried about angry hosts, and I ran three more rounds of meetings. That cost five weeks, and the test started after the summer peak instead of before it. The upside is that when I do decide, people rarely reopen it, because they've been heard. That didn't make the five weeks worth it, and my manager said so in my review, so I changed how I work. For any contested call, I now write down who decides, the date, and what I need from each team. Objections go in the decision doc by that date, and I decide on the day. My last four pricing decisions landed on the date I set."

The cost is something an interviewer can weigh: five weeks and a missed season. The upside is stated, then put in its place, so it doesn't read as an excuse. And the habit is concrete enough to picture her doing it on an ordinary Tuesday.

To practise this step, try Name a Real Professional Weakness and Show How You Are Improving It or Self-awareness interview: a real PM weakness, its impact and your mitigation plan. Write your four parts on paper before you say a word.

Why the disguised weakness fails

The version Nadia could have given instead:

"If anything, I care too much about bringing everyone along. I'll stay late to make sure every team feels heard."

It sounds safe, and it scores worst. It costs nobody but her, so there's nothing to fix, and it tells the interviewer she won't name a fault even when asked for one. Then the follow-up lands: "Tell me about a time that hurt a project." Now she either makes up a story or confesses the real one from behind.

Five years out: this job, one step bigger

This is the fit check from the start of the lesson, asked outright. Nadia's answer:

"If I do this job well, in five years I'd like to own pricing across the whole marketplace, both the rate tools campground owners use and the fees campers pay. By then I want to have run tests through enough peak seasons to know which results to trust, and to be leading a small pricing team. The part of my work I enjoy most is finding what's really going on in booking data nobody trusts, and I'd like to be the person here people bring that problem to."

Her last sentence does a different job from the rest. This is a rare question where you pick the subject, so use it to show what excites you and what you're good at. Saved for the end, that sentence ties her ambition to the work rather than to a title, which is what the interviewer is checking.

She built the rest from the role's scope, the owners' rate tools. She grew it one step in scope, to the campers' fees as well, and one in people, to a small team. That asks for nothing Fernline can't plausibly offer. Then she checked it against the direction she'd want anyway, owning more of how a marketplace sets prices. The two pointed the same way, so the role reads as a step she chose on purpose.

Her rejected drafts each got one of those moves wrong:

DraftWhat it gets wrong
"Honestly, still in product, I hope."Never names the role's scope
"Running product for the whole company."Skips several steps of scope at once
"Running my own travel startup."Heads somewhere this role doesn't lead

You don't need a long plan for this. Careers bend, as hers just did, and a direction plus the skills this job builds toward it is enough. How product managers get promoted shows the usual steps if you need to size yours.

To practise this step, try Explaining Your Five-Year Career Direction in an IBM Product Manager Interview and American Express PM Behavioral: Your Career Direction Over the Coming Years. Write the role's scope at the top of the page before you answer.

Why you're leaving: two sentences, facing forward

Nadia's answer:

"My role was cut in March, when Kestrel merged its host-tools team into a central pricing group. Building the tools owners use to price their places is the work I want to keep doing, and at Fernline that's the whole job."

One to three sentences is the range, and two is usually right. Past that, the answer starts to sound managed, and every extra clause hands the interviewer something to ask about.

Most interviewers ask this to get things going and move on, so your answer only matters if it plants a doubt. After years of large tech layoffs, "my role was eliminated" is a neutral fact, so Nadia gives it in one sentence and spends the other on what she's moving toward. What she keeps out is just as deliberate:

Kept outWhat the interviewer hearsWhat she does instead
A view on whether Kestrel's merger was wiseShe's still sore, and she'll second-guess calls here tooNames the change and judges nothing
An apology for the layoffShe suspects it says something about herStates it as one plain fact
The full story of the reorganizationA defence, with a new question in every clauseOne sentence, then the work she wants
Leaving her performance an open questionSo was it her?If asked for more, adds one fact and stops: "About a third of the product team went in the same change, and my old manager is one of my references."

That first row reaches past mergers: say nothing sour about a manager, the company, team, product or the reorganization that ended your job.

Treat a reorganization you chose to leave, or a short stint, the same way: one sentence of fact, then what you want next. "I left after nine months because the product I was hired for was shut down" is enough.

Your reason needn't be dramatic. A neutral fact works, such as a fixed-term contract ending or a return after a year caring for a parent. So does a pull toward something this job owns that your last one never touched, such as launching the first paid plan of a free product. If a recruiter called while you weren't searching, say so, then name the specific thing about this role that made you take the call. If you can't name it, pick another reason.

Keep pay out of your reason for moving. Talking salary expectations with a recruiter is a separate, normal conversation, and many postings now list a range.

To practise this step, try Why You Are Leaving Your Current Role: Framing a Career Move in a PM Interview: keep the leaving part to one to three sentences, then give the rest to what draws you to Flipkart. The Goldman Sachs version adds likely follow-ups, and the Shopify version pairs it with why this company, which our lesson on why this company covers.

The newer versions: the case against you, and your old manager's view

Some interviewers now skip "What's your weakness?" for one of two sharper versions.

"Give me a reason not to hire you" is the weakness question with the stakes said out loud, and the interviewer watches your composure as much as your content. Don't refuse, and don't name something only to take it back ("...but really, that's a strength").

A gap in experience belongs here, not in the weakness answer. "I've never set the fees a marketplace charges its buyers" is true of Nadia, but an interviewer could read it off her résumé before she said a word. Offered as a weakness, it tells them nothing new, and they'd note she reached for a fact instead of a fault. This question is about fit, so the gap is fair game; naming it before the panel does shows how. Nadia still leads with her consensus habit, because it passes the same test: it's real, it's on record, it isn't the core of a rate-tools job, and four on-time decisions show it's contained.

"What would your last manager say you need to work on?" has one rule: give the answer your manager would actually give, because references get called. For Nadia that's easy: her weakness came from her review. She says so, and adds that her manager would call it better but not finished.

Both land on the same story she gives as her weakness. Interviewers compare notes in the debrief, and the same candid answer from four rooms reads as someone who knows themselves.

To practise, try Make the case against hiring yourself: naming a real gap without sinking your candidacy with your own material, out loud, in under a minute.

All self-awareness and growth questions