Fit and behavioral questions

PM behavioral questions: failure, influence and teamwork

Lesson 22 of 45~9 min read
In this lesson5 sections

An unofficial lesson drawing on the methods in the Behavioral Questions 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

Behavioral questions about failure, influence and teamwork test how you act when your own call goes wrong, and how you get help from people who don't report to you. We'll follow Tess, an invented PM at an invented online furniture store, through one year in which she owned a pricing test she misread, lost an argument without blaming anyone, won another team's engineers for a checkout fix and made room for a quiet analyst.

Loops today also probe ambiguity, customer focus and company values such as Amazon's Leadership Principles, so plan on 8 to 12 stories in your story bank, not one per question type. How answers are scored and delivered covers the telling.

The number she chose after the results

Tess found her failure story by working backward. She listed three things she does differently from her first year at work and asked what taught her each. Usually a mistake did, and the story already ends well: you got better.

Her list began with "I decide what counts as a win before I see test results." It came from an A/B test on the pricing page for the store's free-delivery membership. After two weeks, sign-ups on the new page were up 4%. Only then did she pick sign-ups as the deciding number, because it was the one that went up, and she shipped. She hadn't checked which plan people chose. The new page made the monthly plan look like the default, and the share choosing the yearly plan fell from 40% to 30%. Once each plan was valued over a typical membership, revenue per visitor was down about 3%.

She chose this story over the other two because the mistake was a misreading, never a cover-up. A story where someone got hurt, or you hid a bad number or took credit you hadn't earned, is about character, and one answer can't repair it. It also cost real money, so it can't pass for a typo in a deck, the kind of miss that suggests you've never taken on anything risky enough to break.

From the weekly numbers to a signed plan

Most of the answer is what she did next. Seven days after launch, Tess spotted the drop herself in the weekly revenue numbers. She told her manager that afternoon, before anyone else could, and came with the numbers and a recommendation to roll back, not just bad news. The old page was live by evening.

Then she went after the cause. Every test on her team now starts with a one-page plan, written before launch, that names the deciding number, the guardrail it must not hurt and how long it runs. She got the team's analyst to sign off each plan, so the fix doesn't rest on Tess remembering. Her lesson:

"I decide what a test has to move before it starts, and I write it down, because once results are in I'll find a reason to like whichever number went up."

A course correction counts too: a plan you changed halfway because the evidence turned against it is a failure story with the repair built in.

Telling the story, Tess opens with the mistake and its cost in one plain, first-person sentence:

"I shipped a pricing-page change on the wrong metric, and for a week it cost us about 3% of revenue per visitor."

The interviewer is listening for whether you own it outright or soften it. "The data was ambiguous" sounds like someone stepping back.

To practise, try Owning a Mistake You Made: How to Tell Your Team and Lead the Recovery and PM Behavioral: A Failure You Owned, How You Responded and What Changed After with mistakes of your own. Make your first sentence name the mistake as yours.

When you lost the argument

Tess wanted the coupon-code box off checkout, because shoppers who saw it left to hunt for codes. The marketing lead kept it. Told as "Marketing wouldn't let me," the story makes Tess sound like someone things happen to, which hurts her more than the lost argument does. Losing is normal. Give the reason the decision went the other way, blame no one, and say what you did next:

"Marketing had two partner promotions running on codes that quarter, and breaking them would have cost more than the box did. So the box stayed, and with marketing's agreement I tested tucking it behind a link."

At Amazon, a story like this sits close to the principle Have Backbone; Disagree and Commit.

One checkout fix, framed for each question

Tess's biggest project that year, a checkout that kept failing for large carts, is one story she can tell from three sides: the obstacle, the people she won over, or the result. Tell it from the side each question asks about, but within one loop give it to only one interviewer: they compare notes.

For months, mobile shoppers with big carts had been dropping out at payment, and two bug tickets had been closed as "can't reproduce." Tess reproduced it herself with a 30-item cart on a slowed-down phone connection: the payment service, which her team didn't own, priced each item with a separate call, and large carts timed out. Six weeks into one quarter, leadership moved four of her eight engineers to a partner launch, freezing half her roadmap, the checkout fix included.

Her obstacle was people taken away by a decision above her. She could fight the reallocation, rank the frozen work, or borrow engineers from elsewhere. Fighting suits a decision made in error or for no good reason. Hers came with a signed partner deadline she judged fair, so arguing would only have spent goodwill. Ranking the frozen work and borrowing engineers for the one urgent item fit what she actually faced. Before you tell a challenge, name what kind of obstacle it was and check that your response suits it. A good approach aimed at the wrong obstacle sounds like luck.

Told as a challenge, the obstacle is only the setup. What gets scored is how you reacted and how you solved it, so give the obstacle two sentences and the response the rest. A big challenge from outside work is fine, but have work ones ready too. Tess keeps hers brief:

"Mid-quarter I lost half my engineers to a partner launch. I asked why and for how long: a signed partner deadline, through quarter end. That was fair, so I didn't fight it. Most of the frozen work could wait. The checkout fix couldn't, since every week of delay cost sales, so I looked for engineers outside my team."

To practise, try Behavioral: Walk Through an Ethical Dilemma You Faced and the Call You Made and Keeping a launch on track as requirements keep growing: a scope-control behavioral story with stories of your own. Name the kind of obstacle first, check that your response fits it, and keep the setup short.

Expect an influence question in almost every PM loop, because leading without authority is the job: the engineers, designers, analysts and other teams whose time you need don't report to you. The interviewer wants the specific moves that brought each person round, not "I aligned stakeholders."

If no work story comes to mind, recall a time someone changed your mind, or you changed theirs, and what did it. Then look for that move at work.

Build the answer person by person: whose yes you needed, what each of them is judged on, and what you told each. The strongest line is usually where your ask moves their number, not only yours.

To fix checkout, Tess needed two engineers for six weeks from the platform team, which reports to a different director. Two people had to agree: the platform manager, who would lend the engineers, and the platform tech lead, who cared whether the fix was sound.

Tess found what they shared in her own evidence. The timeouts in her reproduction were payment-service errors, and the platform team is judged on that service's error rate. So the bug counted against the platform manager's target as well as against Tess's checkout completion. For the tech lead, the reproduction and the timeout logs made the case: he could check them himself, and they showed his own service failing on big carts.

Her ask led with the manager's number:

"The large-cart timeouts are most of the payment service's errors this quarter. Fixing them gets you back under your error target and gets us our conversion back. I'm asking for two engineers for six weeks, and my team will run the testing and the rollout."

Pitched on checkout completion alone, it would have asked the manager to spend her team's time on Tess's goal.

To practise, try Influencing leaders above your level to back your plan: PM behavioral story with your own example. List each person whose yes you needed and what you told each.

Under every answer in this lesson, the interviewer is checking whether you understand people. Two of Tess's stories so far turned on knowing what one person wanted, and why: the marketing lead's partner promotions and the platform manager's error target.

So describe what a colleague was trying to achieve, never what they lacked. Running someone down, however fair the complaint, makes the interviewer wonder whether the difficult one was you. The platform manager's first reaction to Tess's ask was worry for her own team. Compare "she didn't care about checkout" with:

"Her team is judged on keeping the payment service up, and lending two engineers mid-quarter put that at risk. I had to show the fix helped her number, and not only mine."

The second shows Tess understood the worry, which is half the influence story.

To practise, try Resolving a disagreement with a strong-willed colleague on a product decision with a colleague of your own. Record your answer, then listen for any line that colleague would wince at.

Pick the result you're proudest of, and be ready to say why. The reason you give decides what the rest of the answer has to prove.

Tess picks the checkout fix, because it was hard.

"I'm proudest of the checkout fix because it was hard: the bug lived in another team's service, and two tickets on it had already been closed. It taught me to follow a problem across team lines before deciding it belongs to someone else. It shipped in six weeks, and mobile checkout completion went from 62% to 66%."

Her reason is difficulty, so the lesson she learned carries the answer and the number only confirms it mattered. Had her reason been impact, she would lead with the number.

To practise, try Behavioral: Walk Through Your Proudest Achievement and Why It Matters. Before you begin, state your reason and the evidence it calls for.

Fit the fix to the person

A PM's work runs through partners in engineering, design, data science and legal, many of them in other cities, and current loops ask how those partnerships went. The stories worth telling often start with a mismatch between how one person works and how the team runs its meetings.

Imani, the team's analyst, had joined three months earlier and worked from another city. Quarterly planning ran as a fast debate on video, and she barely spoke, yet her comments on the planning doc afterwards were the sharpest anyone wrote. Tess concluded that Imani had plenty to say and the format left her no room. So Tess sent the doc two days early and asked Imani to open the next meeting with five minutes on what the data said about each proposal. In that meeting she showed that one proposed test couldn't detect the hoped-for lift with the traffic available, which saved six weeks of work.

"Imani's analysis was the best on the team, and our planning format kept it out of the room until the decisions were made. So I changed the format."

Then say why that fix suited her: the problem was the format, not Imani. Had she been quiet because she disagreed and felt too new to say so, a private conversation would have come first. Naming the fix you didn't choose shows the choice was deliberate.

To practise, try Behavioral: Collaborating Across Clashing Priorities and Working Styles with a partner of your own. Name the fix you chose and one you passed over.

All failure and learning questions