I’m staring at my resume and I’m basically seeing: McKinsey, strategy projects, stakeholder workshops, client deliverables. No CS. No coding. Zero real product experience. And I’m trying to figure out if that’s a red flag for tech PM roles or if I’m overthinking it. I know the ‘product is not just for engineers’ thing, but I also know some hiring managers are looking for evidence that you actually understand how products get built. My consulting projects had business impact, but they were pretty traditional—strategy recommendations, go-to-market plans, org design. I haven’t shipped software. I don’t have a product portfolio. I haven’t even done a side project to demonstrate product thinking. I’m wondering: is my consulting experience enough as-is if I package it right? Or do I actually need to build something to show I can think like a PM? And if I do need to build something, what kind of portfolio project actually signals ‘product thinking’ to recruiters rather than just looking like resume padding?
no cs? fine. most pms can’t code anyway. but a portfolio? yeah, u kinda need that now. not because u need to code, but because u need to show u’ve actually thought about user problems instead of just client problems. your resume is boring without proof of product thinking. build something small, even if it’s wireframes + user research. show the work.
like should the portfolio be a side project or like case studies from consulting work reframed as products?
Your consulting background is a genuine asset for PM roles—many top tech companies actively recruit from top consulting firms. The CS gap isn’t a dealbreaker, but the product portfolio is increasingly expected. Your portfolio doesn’t require coding; it requires evidence of product thinking. I’d recommend one of two approaches: either build a small product or feature concept around a real problem you’ve identified (doesn’t need to be coded—wireframes, user research, metrics framework), or deeply reframe one of your consulting projects by adding user research, competitive analysis, and outcome metrics that signal product thinking rather than consulting delivery. Hiring managers want to see that you think about users first, then business, then organization. That’s different from how consultants typically frame work.
CS background isn’t required for PM roles—your consulting foundation is solid! A thoughtful portfolio project will absolutely set you apart!
I didn’t have a portfolio when I started interviewing and I got rejected by three companies before I finally built one. It wasn’t even that impressive—just a simple problem I’d noticed, some user interviews I did with friends, and wireframes I threw together. But once I had that case study to show, the feedback changed completely. Interviewers suddenly believed I could actually think about users, not just clients.
also stop calling it ‘case studies.’ that’s consultant speak. call it what it is: a product i made or thought about. recruiters can smell consultant language a mile away.
okay so portfolio is basically required now. doing that this month then. any specific tools people actually recommend for simple wireframing?
Figma is industry standard and free tier is sufficient. But honestly, the tool matters less than the thinking. Your portfolio should answer: What problem did you identify? How did you validate it? What solution did you propose? How would you measure success? What did you learn? That narrative matters more than pixel-perfect wireframes. One strong case study beats three mediocre ones.