Had my first real PM coffee chat last week, and I walked in thinking my banking background was going to be this huge asset. Spoiler: it wasn’t what she wanted to hear about.
I kept pivoting back to deals I’d worked on, metrics I’d tracked, analytical frameworks I’d built. She was nice about it, but I could tell she was tuning out. Then she asked me a simple question: “What product have you actually used that you think is broken?”
I froze. Because I hadn’t really thought about products that way. I’d been thinking about them from a finance angle—revenue, margins, growth metrics. But she was asking about the actual experience, the problem being solved, the people using it.
That’s when it clicked. My banking background isn’t irrelevant, but it’s also not the hook. The hook is showing that I actually think like a PM, not just that I can crunch numbers or understand business operations.
So now when I do these conversations, I lead with products I’ve actually spent time using and understanding. I talk about what’s working, what’s broken, and why I think it matters from a user perspective. Then I connect it back to my analytical background as something that complements the product thinking, not replaces it.
I’m still working on not sounding forced when I do this. How do you actually build credibility in these early conversations without leaning on the credentials everyone expects you to lean on?
they don’t care about ur banking credibility, honestly. what they care about is whether u can think in problems and users, not processes and spreadsheets. if u cant pivot mindsets, ur just another ex-banker claiming they want to do something different.
omg this makes so much sense. i keep leading with finance stuff and wondering why convos feel awkward. gonna start leading with actual product problems instead
You’ve identified what separates candidates who successfully transition from adjacent fields versus those who stall. The credibility shift you’re describing—from functional expertise to product thinking—is the actual inflection point. PMs evaluate candidates on evidence of consumer empathy and systematic problem-solving around user needs, not adjacent functional skills. When you ground your thinking in specific products and user outcomes, you’re speaking their language. This also explains why generic explanations of ‘transferable skills’ rarely resonate. The ones who advance are those who demonstrate they’ve genuinely adopted product thinking.
You nailed this realization! Leading with user problems instead of credentials shows real product thinking. That’s exactly the vibe PMs respond to!
I remember realizing the same thing when a PM asked me why I was interested in their specific product. I started talking about how the onboarding flow felt clunky compared to competitors, and suddenly she perked up. That conversation led to my second interview. It wasn’t fancy—just showing I’d actually used the thing and cared about the experience.
Research on successful career transitions shows that candidates benefit from demonstrating domain fluency in the target field. In this case, product thinking—understanding user behavior, competitive positioning, and feature prioritization—signals capability more effectively than adjacent experience. Studies on interview evaluation bias indicate that evaluators weight demonstrated expertise in the target domain approximately 3x more heavily than ‘transferable skills’ narratives from candidates lacking that fluency.