I’ve been grinding networking for PM roles for a few months now, and I keep running into the same wall: when I finally get a coffee chat with a PM, I freeze up trying to explain why someone from ops/finance/consulting should care about me for a product role.
The thing is, I genuinely care about building products and understanding user problems. I’ve done that work in my previous role—just not in a tech context. But when I’m sitting across from someone who’s been shipping features at tier-1 companies, I feel like I’m apologizing for my background instead of owning what I’ve actually done.
I’ve tried a few angles. Sometimes I lead with the specific product decisions I was curious about. Sometimes I talk about metrics and user feedback loops I’ve observed. But I’m never sure if I’m hitting the right note—like, am I coming across as someone who gets product, or just someone trying really hard to convince them I’m not a total outsider?
For people who’ve actually broken through on this—how do you frame your non-tech background without making it feel like you’re overcompensating? What actually resonates in those conversations?
honestly? they don’t care about the frame. they care if you can talk intelligently about their product for five minutes without sounding lost. i’ve seen finance guys land pm roles because they asked one smart question about unit economics. i’ve seen ops people fail because they spent the whole chat apologizing. stop selling the background and start asking questions about what they actually build. that’s it.
this is such a good question!! i think the key is showing you understand product thinking, not just ops stuff. like, ask them about a feature decision they made and why. that shows ur curious abt the thinking behind it yk?
Your instinct is correct: you’re overcompensating. The most effective approach I’ve observed is to reframe your background as evidence of problem-solving capability rather than a liability. Specifically, lead with a concrete example of how you identified a user need or optimized a process based on data and feedback—then connect that directly to a product decision you’ve observed in their space. The transition should feel natural, not forced. Technical depth matters less than demonstrating you think systematically about tradeoffs and user impact.
You’ve got this! Your perspective is actually valuable—PMs need people who understand ops too. Own that confidence!
I had this exact moment a year ago. I was in strategy at a fintech company, and I realized I didn’t need to explain my background—I just needed to talk about why I cared about products. I started asking PMs about a specific feature they’d shipped and what surprised them about how users actually used it. Suddenly, the conversation shifted. They weren’t evaluating my resume; they were just talking shop with someone genuinely interested.
also, pro tip: stop calling it ‘non-technical.’ you have a different background. big difference. one sounds like you’re scared; the other sounds like you bring something they don’t have.
One additional point: avoid generic product talk. Instead, prepare 2-3 specific critiques or observations about their actual product—decisions you’d question, gaps you’ve noticed, or opportunities you see. This demonstrates you’ve done your homework and think critically. Non-technical backgrounds often excel at spotting friction points that technical-first thinking misses. That’s your edge.