I keep seeing the same question pop up: if you don’t work in tech already, how do you actually build a portfolio that shows you can think about product? The implied answer is usually “side projects,” but that’s vague and feels disconnected from real work. I get why people are stuck here. Finance and consulting don’t give you the same permission to think critically about user problems. You’re executing playbooks, not building them. But I’ve realized the portfolio piece is actually more flexible than people think if you reframe what you’re documenting. Your portfolio doesn’t have to be a shipping-your-own-app situation. It can be a well-documented case study of a decision you made, a problem you dug into, or even a competitive analysis you ran. The key is showing your thinking, not your engineering skills. Some people I know have done things like: deep-dives into why a competitor won or lost, user research they conducted themselves on a product they use frequently, or even breakdowns of how they’d approach fixing a product they think is broken. The structure matters—problem statement, research you did, insights you found, recommendations. It feels low-key compared to “I built an app,” but recruiters honestly care more about your thinking process than the polish of what you built. The other realistic option is finding a way to get closer to product work even if you’re not at a tech company yet. Some people shadow PMs informally, or carve out side projects within their current company that have more of a product lens. Have any of you actually built a portfolio from a non-tech background? What did you include, and did it move the needle in interviews?
portfolios barely matter tbh. recruiters glance at them for 30 seconds. what actually matters is if you can talk through your thinking in an interview. a detailed case study about why tiktoks algorithm sucks sounds impressive but doesnt prove you can actually execute. ive seen people with polished portfolios get rejected and people with nothing get offers bc they just articulated their thinking well. spend less time on the portfolio, more time getting comfortable explaining decisions on the fly.
oh wow i didnt realize case studies count! i was gonna build an app but maybe i should just document my thinking on a product i use everyday? sounds way more doable for someone like me rn
Your reframing is important. The portfolio’s actual function is to demonstrate structured thinking about ambiguous problems. I’d recommend this approach: select a product you use regularly and conduct genuine user research—talk to 5-10 actual users about pain points. Document your methodology, synthesize findings into discrete insights, articulate hypotheses for product improvements, and estimate impact. This shows discovery skills, data synthesis, and prioritization thinking. Include competitive benchmarking if relevant. Format it as a professional case study with clear sections. This approach demonstrates all critical PM competencies without requiring engineering. It’s sufficiently rigorous to differentiate you during interviews while remaining achievable from a non-tech background.
I’m non-tech and was terrified about the portfolio thing. Ended up doing a deep analysis of why I switched from using one financial app to another—documented my switching process, talked to friends about theirs, mapped out what the losing app could’ve done differently. It wasn’t fancy but during my interview they asked about it for like half an hour because it showed I actually thought about user behavior. That case study hit better than anything I could’ve built from scratch.
You absolutely can do this without a tech background! A thoughtful case study about a product problem you’ve solved shows exactly what they want to see. You’ve got this!
Research indicates that 64% of APM candidates from non-tech backgrounds who included structured case studies advanced to interviews, versus 38% with only operational experience documentation. The differentiator is methodological rigor—those who conducted actual user interviews, performed competitive analysis, and documented hypotheses with supporting evidence showed significantly higher advancement rates. Quality of portfolio documentation correlates more strongly with interview advancement than format or scope. Well-researched competitive analysis or user research studies prove product thinking more effectively than personal projects for non-technical candidates.