I’ve been having a lot of coffee chats lately, and I keep stumbling on the same moment: the 30-second pitch about why I want to get into product. My background is operations and finance—solid analytical skills, deep process knowledge, stuff that actually does transfer to PM. But when I open my mouth, it feels like I’m either overselling the “I’ve been thinking about this for months” angle or I’m underselling why I’m credible at all.
I’ve tried a few different versions. One emphasizes the business analysis side, another focuses on my curiosity about user problems. Every time, I walk away feeling like I didn’t actually make the case for why someone should take me seriously when I’m not coming from a tech or product background.
The people I’m talking to are mostly PMs and product ops folks at companies like Google, Airbnb, and some earlier-stage startups. They clearly know what they’re doing, and I don’t want to sound like I’m naive about what the role actually entails.
What’s the pitch that actually lands? How do you explain why you’re a credible candidate when your background isn’t the traditional “I’ve been thinking about product for five years” story?
forget the “i’m passionate about product” angle. that’s what everyone says. instead, talk about a specific decision you made or problem you solved in your ops/finance role where you had to think like a PM—user insights, tradeoffs, data-driven choice. then connect it: “this is why i want to do that full-time.” shows you actually understand the role, not just the title. bonus: makes you sound competent, not just enthusiastic.
and honestly, drop the apologies for your background. ops and finance backgrounds are assets for pm. most pms come from random places anyway. confidence matters way more than fitting some template.
ohhh the specific problem angle is so much better than generic passion stuff
wait ur right, ops background is actually really valuable for pm. never thought of it that way
confidence over perfection. noted lol
gonna steal that specific decision angle for my next chat
the apologies thing hit me. ive been doing that and it probably makes me sound insecure
Keep your pitch to 45-60 seconds. Lead with your example, explain the thinking behind your decision, mention the outcome, and end with one sentence about why that work energizes you about product. Avoid buzzwords like “stakeholder management” or “user-centric thinking”—show them, don’t tell them. The people you’re meeting have heard dozens of pitches. The ones that stick are specific, honest, and demonstrate real judgment.
You’re credible because you’ve solved real problems. That matters way more than where you started!
What changed everything for me was one mentor who said, “Stop explaining why you’re not a PM yet. Start showing why you think like one.” So in my pitch, I’d lead with the story, not the aspiration. People responded so much better because I sounded like someone who’d already done the work, not someone asking them to take a chance on me.
Your pitch should include: one specific decision or problem (15 seconds), your reasoning and approach (20 seconds), measurable outcome (10 seconds), and connection to why this motivates you toward PM (15 seconds). This 60-second structure maintains engagement and demonstrates systematic thinking. Operations backgrounds correlate strongly with successful PM transitions because they bring business acumen. Lean on that correlation rather than explaining it away.