This is keeping me up at night. I have solid years in operations and business strategy, and I genuinely care about product thinking. But every time I talk to someone in PM, I feel like there’s this unspoken question: ‘Are you actually interested in this or just looking for your next step up the career ladder?’
I think the difference is real. Some people network for PM roles because they actually want to solve product problems. Others are just climbing the ladder and PM happens to be the next rung.
I want to be in the first camp, and I want people to actually believe that when I talk to them. But I don’t know how to demonstrate that without sounding forced or overly invested.
Here’s what I’m trying: I’ve been reading product teardowns, engaging thoughtfully with product discussions, and I keep specific examples of products I use and what I’d change. But when it comes to the actual conversation—how do you bring this up naturally without making it weird?
And how do you actually address the elephant in the room? Like, do you just say ‘I know I’m coming from ops, not engineering’ and own it? Or do you let your actual product thinking do the talking?
What’s worked for you when you’ve had to make this leap in a conversation? Where did people actually believe you genuinely cared about the work, not just the title?
ppl can smell desperation. if ur just chasing the title, theyll know. dont try to convince them ur passionate—show them. know specific decisions that product made, have opinions about them, ask why they made different choices. dont say ‘im pivoting to pm’ say ‘ive been thinking about problems this way for years.’ ops ppl who get product always talk about trade-offs and constraints. lean into that.
own the ops background actually. best move i ever saw was someone saying straight up ‘i know the ops side inside out, heres what i see pms missing’—suddenly shes not a tourist, shes someone with insight. the career ladder thing? ppl assume everyones climbing it. what separates u is whether u have actual thoughts about their product or just generic ambition.
wait this is so real. ive been worried about this too. maybe just ask them about a specific feature or decision? like genuinely curious, not rehearsed? i feel like when i do that ppl open up more and forget im trying to network lol
havent done this yet but from what ive read, ppl respect when u acknowledge the gap instead of pretending it doesnt exist. like ‘heres what i bring from ops that might be useful’ sounds way better than ignoring it entirely?
You absolutely have an advantage here—PMs need operational thinking! Lead with genuine curiosity about how they build, share real insights from your background, and watch them relax. Authenticity wins every time!
I was worried about the exact same thing. What changed for me was when I stopped thinking about it as ‘explaining my non-tech background’ and started thinking about it as ‘showing I understand this differently.’ In one conversation, I actually said ‘from ops, I’ve noticed most products don’t account for internal limitations—here’s an example,’ and suddenly it wasn’t a gap, it was an asset. That person ended up introducing me to someone because I had a genuine perspective, not because I was desperate.
Research on career transitions shows that candidates with non-traditional backgrounds who explicitly connect prior experience to PM competencies have significantly higher success rates. The key distinction is framing operations as a strength—understanding process, constraint management, and cross-functional dependencies are genuinely valuable PM skills. In your conversations, quantify or provide specific examples of how operational decisions you influenced positively impacted user experience or product strategy. This moves the narrative from ‘I want a new job’ to ‘I bring relevant expertise.’ Most successful ops-to-PM transitions involve candidates who treated their history as foundational knowledge rather than something to overcome.