Fit and behavioral questions

Tell me about yourself: a two-minute PM introduction

Lesson 17 of 45~9 min read
In this lesson6 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

"Tell me about yourself" opens most PM interviews, and it tests a PM skill: choosing the few facts that matter and tying them to this job in about two minutes. Your interviewer will spend the rest of the hour asking about whatever you put in those two minutes, so a good introduction hands them the questions you want.

Tessa has spent six years in customer support at a company that sells scheduling software to physical therapy clinics, the last two as support operations lead. She's interviewing for a PM role at a company that makes scheduling and dispatch software for home-repair businesses, on the team that owns the tools office staff use to plan and change technicians' days.

She'll hear this question from the recruiter, from the hiring manager and, shorter, at the start of many onsite rounds. Related questions have their own lessons, on why this company and why hire you and on why you're leaving and your weaknesses.

Start from the posting, not from college

Tessa's first draft started at college and walked forward, job by job. Before rewriting it, she read the posting, underlined what this PM will do, and found the part of her past that answers each line:

The posting asks forWhat in Tessa's past answers it
Work with engineers to decide what to fix firstThe dashboard she built with two engineers, and the fix she helped choose
Talk to office staff at repair businesses every weekSix years on calls with clinic front desks, the same kind of user
Set goals and measure whether a launch workedEscalations before and after the fix

Anything in your story that answers no line needs a strong reason to stay.

Cut the four-minute tour

Judged against that table, here is where her four minutes went and what her rewrite did with each part.

What she coveredSecondsIn the rewrite
Her psychology degree20Cut: it's on her resume
Two years at a hotel front desk25Cut
Starting as a support agent, taking calls from clinic front desks30One sentence
Two promotions and the 14 agents she manages30A few words
Rebuilding the agents' shift schedule35Cut
Moving support to a new ticket tool30Cut, saved as a follow-up story
The escalation dashboard she built with engineering20The center, about a minute
Her hiking club20Saved for the free-time question
"And now I'm looking at PM roles"10Replaced by why this team
Pauses and "so, yeah"20Gone

The only product work in her career got 20 seconds, at minute three. The shift schedule got the most because it was the most work, yet it answers no line in the posting, so it goes, however proud of it she is. From her years as an agent she keeps who called and why: front-desk staff whose morning fell apart because a calendar was wrong. She drops her ticket-close rate.

Decide what you want this person to remember when they write their notes tonight, and keep only what serves it. For most candidates that's two things. Tessa's: she knows this kind of user from the other end of the phone, and she has turned their complaints into a fix she shipped with engineers.

To practise this step, put a real PM posting beside you and try Open a PM interview with a short personal pitch: present, past, why here. Then answer Opening PM behavioral: your current team, your scope on it, and why this role fits, and check what you said about your team against the posting.

Make the dashboard the center

The dashboard got 20 seconds in her draft and gets about a minute in the rewrite. That minute has to prove her through-line: one sentence that explains why her career went where it did and why PM comes next:

"I'm good at turning a pile of angry tickets into one problem engineers can fix, and the part I like best is the day the fix ships."

Everything in the introduction should support that sentence. It also answers what every interviewer wonders about a career switcher: why PM.

Her results could have gone in a row instead:

"Built an escalation dashboard. Cut repeat-appointment escalations 71%. Lead a team of 14. Rebuilt the staffing model. Moved us to a new ticket tool."

Said aloud, that row gives no reason why any of it mattered. She keeps one result and puts the problem before it and the fix after it. The staffing model and the ticket tool drop out, and the team of 14 shrinks to a few words.

She doesn't start at the beginning either. She opens with her current job in one sentence, goes back to how she started, then runs forward: one story, no tour of every year. Here is her rewrite as she first wrote it:

"I lead a support operations team of 14 at a company that sells scheduling software to physical therapy clinics, where I own our routing rules, the tier-two queue and our SLAs. I started there six years ago answering phones, mostly from front-desk staff whose morning had just fallen apart because the calendar was wrong. I've learned I'm good at turning a pile of angry tickets into one problem engineers can fix, and the part I like best is the day the fix ships.

The clearest example is from last year. Problems support couldn't solve went to engineering through a shared inbox, and nobody could see what they had in common. I worked with two engineers to build a dashboard that tagged every escalation by the part of the product it came from. Within a month it showed that about four in ten came from one thing: when a clinic changed a therapist's weekly hours, repeating appointments already booked moved or vanished without warning. Patients were turning up for visits that no longer existed.

I took that to the PM who owns scheduling, and we chose a first fix together: before an hours change saves, the screen lists every booked appointment it would touch. Escalations about repeating appointments went from about 120 a month to about 35. I'm proud of that one.

It's also why I'm here. I liked deciding what to build more than closing tickets, and I want to do it full time. Your team owns the tools office staff use to plan technicians' days, which is a problem I know from the other side: when a schedule changes, the people at the other end have to find out. I'm happy to walk through how we chose that fix over the others."

That's about 290 words, down from around 560. At a calm 140 words a minute, two minutes is about 280, the length Cracking the PM Interview suggests when the interviewer goes straight to the question. If they open with 45 seconds about themselves, its rule is one to two times that, so 45 to 90 seconds. Spoken, her version runs longer, as her recording shows below.

She also keeps a one-minute version, which suits recruiter screens on video: the first sentence, the pattern and result in two sentences, one sentence on why this team, and the offer to explain the fix.

End on this team, then offer your best story

Her draft ended on "And now I'm looking at PM roles", which leaves the interviewer to guess why she's in this room. The rewrite's last paragraph says what she wants next and why this team gives it to her: she knows from the other side what happens when a schedule changes.

Her last line then hands the interviewer a good next question. "I'm happy to walk through how we chose that fix over the others" points at the decision she can defend in the most depth, so the next ten minutes go where she's strongest. The ticket-tool move stays out, saved as a story she can tell if asked.

Prepare the full story behind your hook: the options you considered and why you chose one. Our lesson on building a PM behavioral story bank covers how. Keep to one hook, two at most. Four sound like a menu, and the interviewer will pick the one you prepared least.

To practise this step, try Structuring a Concise Self-Introduction for a PM Interview Opener with your through-line written at the top. Then answer Opening PM Interview Pitch: Structuring a Concise Walkthrough of Your Career and check that you end on the job in front of you.

What her recording made her fix

Written introductions read well and sound stiff, so Tessa said hers to a friend on a video call and recorded it. An AI mock interviewer will do if you only want timing. Listen back for how long it ran, whether your friend can repeat your two points, and whether you sound like you want the job.

Tessa's recording ran 2 minutes 25 seconds: nerves add pauses that a word count can't see. When they played it back, her friend, who works in finance, stopped it after the first sentence: "What's a tier-two queue?" Everyone at her company talks that way, so she had never heard it as jargon, though most people a PM talks to wouldn't know it. She rewrote the line in plain words:

"I decide how each problem reaches the right person, so a clinic that can't book any patients gets an expert within the hour."

The plain line is longer, so she cut the shared-inbox sentence and "The clearest example is from last year." The next recording ran about 2 minutes 15 seconds. She recorded it twice more, until she could start from any paragraph without notes. For the same answer outside PM, see introducing your background and motivation.

Give the hobby something people use

Tessa saved her hiking club for the question about what she does outside work. Her first answer there was "I like hiking." It's safe, but the interviewer gets nothing to ask about.

The move is to attach something you made or ran, and who uses it. If your real interests have nothing to show yet, give one of them an outcome. The point is to make something you already do visible, not to invent a hobby; two follow-up questions would expose that. Say you spend evenings trying new AI tools. Pick a chore from your week, such as sorting tax receipts, and automate it with an AI coding assistant. A merged fix to an open-source library you rely on, or a short newsletter on a field you follow, does the same job. See PM side projects that interviewers believe for more.

Tessa already had something to attach. Her hiking answer now:

"I hike most weekends with a club of about 60 people. Two years ago a member drove two hours to a trailhead that a washout had closed, so I set up a shared spreadsheet with a phone form where anyone can log trail conditions after a hike. About 40 members check it before a weekend trip now."

Same hobby, now with something she built and people who use it. Hiking has nothing to do with home-repair software, and it doesn't need to. She keeps it out of her introduction because the dashboard already shows she can build something people use.

Interviewers at AI companies sometimes ask a cousin of this question: how you use AI tools in your own life. Same rule: name a habit, then show what came of it.

To practise this step, try Robinhood PM Behavioral: Talking About a Genuine Passion and Backing It With Evidence with an interest you can back up with something you did, and say it in under a minute.

All motivation and fit questions