Back to resources
August 20265 min read

How to Record a Product Manager Video Intro (Script + Examples)

Hiring managers now watch a 60-90 second video before booking a screen. The structure, script approach, and recording mistakes that decide whether a PM video intro helps or hurts.

How to Record a Product Manager Video Intro (Script + Examples)

How to Record a Product Manager Video Intro (Script + Examples)

More hiring managers now skim a portfolio and watch a 60-90 second video before they ever schedule a screen. It's the fastest way for them to check the two things a resume can't show — can this person communicate clearly under zero prep, and do they sound like someone the team would actually want in a room. A good video intro takes that check off the table before the first call even happens.

1. Keep it under 90 seconds

A video intro is not a cover letter read aloud. The moment it runs past 90 seconds it stops being a quick signal check and starts being a time cost, and most reviewers will skip ahead or close the tab. Aim for 45-75 seconds. If you can't say what matters in that window, the problem isn't the time limit — it's that you haven't cut the script down to the one or two things that actually move the needle for this reader.

2. Structure: who you are, what you've shipped, what you're looking for

Three beats, in this order, cover almost every version of a strong intro. First, a one-line identity that's more specific than your job title — the domain or problem space you work in. Second, one concrete thing you've shipped with a real outcome attached, not a list. Third, what you're looking for next, stated plainly enough that a recruiter can match you to a role without guessing. Skip the "thanks for watching" close — end on the third beat and let it land.

3. Write a script, then throw half of it away when you record

Write out what you plan to say word for word first — it forces you to cut filler you wouldn't otherwise notice. Then record from a bullet-point version of that script, not the full text. Reading a script on camera is easy to spot and reads as rehearsed in a way that undercuts trust; speaking from three or four bullet points sounds like you, because it is you, just with the wandering parts already cut in the writing pass.

4. What to actually say in the "what you've shipped" beat

Pick one project, not three. Name the problem in a sentence a non-expert would understand, the decision you made, and the result with a number. This is the same discipline as a written case study — see how to write a PM case study — compressed into about 20 seconds of spoken word. Resist the urge to summarize your whole career here; that's what the portfolio underneath the video is for.

5. Record it like a stakeholder update, not an audition tape

The tone that lands best is the one you'd use giving a two-minute status update to a VP — direct, unhurried, no forced enthusiasm. Sit or stand somewhere with a plain background and reasonable light facing you, use your laptop or phone camera at eye level, and do two or three takes. Pick the take where you sound most like yourself in a normal meeting, not the take with the fewest verbal stumbles — a little imperfection reads as authentic; over-polish reads as rehearsed.

6. Common mistakes that undercut a good video intro

The three that show up most: starting with "Hi, my name is" and your job title (the reader already has your name and title — spend the first line on something they don't already know), talking through your entire resume chronologically instead of one sharp example, and recording in a space with visible clutter or bad audio that becomes the thing the viewer remembers instead of what you said. Fix the audio before the video — a clear voice on a mediocre camera beats a sharp picture with echoey audio every time.

Bottom line

A product manager video intro works because it's the fastest way for a reviewer to check communication and presence before investing a screen call. Keep it under 90 seconds, hit the who/what-shipped/what's-next structure, script it then speak from bullets, and record it like a status update, not an audition. For the written version of the same "what you've shipped" beat, see how to write a PM case study, and for the one-line identity that opens both the video and your LinkedIn, see how to write a PM elevator pitch. This video lives on your portfolio for whoever finds it — for the more aggressive move of sending a shorter version directly to a hiring manager as part of the application itself, see how to send a video application.

Product Leader builds this structure — case studies, metrics, and a video intro — from your CV or LinkedIn in under a minute. Start your portfolio here, free, no credit card.

FAQ

How long should a product manager video intro be?

45-75 seconds, under 90 seconds at the outside. Past that it stops being a quick signal check for the reviewer and becomes a time cost they'll skip past. If the script doesn't fit, cut it down to the one or two points that matter most, don't extend the time.

What should a PM video intro actually say?

Three beats: a one-line identity more specific than your job title, one concrete project you shipped with a real outcome, and what you're looking for next. Skip a chronological résumé recap — pick one project and go deep rather than summarizing your whole career.

Should I read from a script when recording a video intro?

Write a full script first to cut filler, but record from a bullet-point version, not the full text. Reading word-for-word on camera is easy to spot and reads as rehearsed; speaking from a few bullets sounds natural because it still is you talking, just already trimmed.

What mistakes hurt a product manager video intro the most?

Opening with your name and job title instead of something the reviewer doesn't already know, narrating your entire resume instead of one sharp example, and recording with bad audio or a cluttered background that becomes what the viewer remembers instead of what you said.

Related reading

Cookies

We use cookies for analytics and to remember your preferences. "Necessary" is always on.