A pragmatic roadmap for moving from banking to product management

i’m aiming to break into product management after 2 years in ib and wanted a veteran-tested, step-by-step plan. pulling threads from veteran advice and people who’ve done it, here’s a distilled roadmap that i’ve started following:

first 60 days: identify product stories in your deal work. rewrite two deal narratives as product problems — what was the user pain, what metrics would you track, and what quick experiments could you run? build a 2–3 page product spec for one of them.

next 60–120 days: get hands-on product experience. volunteer for cross-functional projects at your bank (internal tools, client portals), or build a tiny side project/landing page and measure user interest. network with PMs—ask for 20-minute feedback sessions on your spec; convert feedback into version 2.

90–180 days: prepare for interviews by practicing behavioral PM stories and a 30-minute product case weekly. tailor your resume to highlight product-relevant impact (user metrics, hypothesis-driven tests, stakeholder management). reach out with your spec as a conversation starter.

i’ve blocked weekly 2-hour sessions to churn out these artifacts. for those who’ve landed pm roles from banking—which part of this roadmap mattered most in your interviews?

most interviewers don’t care about your banking spreadsheet; they want to know you can empathize and make trade-offs. the spec is gold if it’s concise and you can defend every assumption. practice defending dumb choices — interviewers live for that.

also stop using ‘stakeholder management’ as a buzzword. show one real example where you influenced a decision.

made a tiny landing page and showed 200 signups in 2 weeks. got interest from a pm recruiter.

practicing product cases weekly helped my confidence a ton. do it.

this roadmap is practical. two additions from mentees who succeeded: firstly, translate banking metrics into user impact terms (e.g., “reduced processing time by X% leading to Y increase in retention”). second, document decision trade-offs in your spec—why you prioritized one metric over another—and be ready to discuss alternatives. interviewers often probe how you think, not just what you recommend. finally, seek cross-functional allies who can vouch for your execution. which product domain are you targeting (finance tooling, consumer, enterprise)?

this is actionable and realistic—love it! keep iterating on that spec and you’ll shine in interviews!

also, mention the pushbacks you faced while building the spec—those make your story believable and interesting.

among 38 bankers who transitioned into PM roles, the most predictive actions were: producing a measurable prototype (27/38), securing a cross-functional sponsor (22/38), and demonstrating A/B test thinking in interviews (26/38). interviewers ranked concrete metrics and a polished spec as top signals of readiness. if you want, i can share a short template that maps banking achievements to product metrics.