Non-technical background trying to land an apm role—does my resume even matter?

I’m starting to second-guess myself here. I come from a sales and business development background, and while I’ve been PM-adjacent in some projects, I don’t have a technical co-founder story or a “I built an app” moment to lean on. I see so many APM profiles that highlight technical or engineering internships, and I’m wondering if my resume is basically disqualifying me before I even get a phone screen.

I’ve talked to a few people in my network, and they’ve given me conflicting advice. Some say to dive into product management courses to offset the technical gap, while others laughed and said “they don’t care about courses, just tell a good story.” One person told me to reframe my sales wins as product insights, which made me think—maybe I’m just not packaging my experience right?

Has anyone else been in this boat? How did you actually structure your resume and application story to make non-traditional experience feel relevant? And be real with me: do you think technical background is actually table stakes for APM programs, or is it just the people posting about their wins that have it?

nah technical background isnt table stakes despite what ppl tell u. what matters is whether u can show u managed something complex and made tradeoffs. ur sales background can absolutely work if u frame it right—like how u managed customer needs vs internal constraints. most hiring managers have seen enough product experience diversity to know it comes from places outside eng.

this is so helpful bc i also have non-tech background! did u find it helpful to take any product courses or just focus on storytelling?? asking bc im trying to decide where to invest my time rn

Your sales and BD background is actually a significant asset that many technical candidates lack. APM programs need people who understand market dynamics and customer workflows. The key is reframing your experience through a product lens: identify moments where you identified a gap between what customers needed and what existed in the market, or where you influenced a solution based on customer feedback. Your resume should tell a narrative arc showing progression toward product thinking, not just list past titles. Avoid the trap of taking PMO certification courses—instead, focus on demonstrating that you’ve already thought like a PM in practical situations.

Your sales background is genuinely a superpower! You understand customers in ways many engineers don’t. APMs need that perspective. Trust your story!

I was in sales before my APM role, and honestly that’s what got me in the door. During my interviews, I talked about a situation where I identified a gap between what customers were asking for and what we were selling. The interviewer said that insight mattered way more than if I’d done a coding bootcamp. Your job is to show you’ve been solving problems, not that you know how to code.

Research from several APM program cohorts shows approximately 30-40% of participants come from non-technical backgrounds, disproving the notion that technical experience is strictly required. However, candidates from business-facing roles who explicitly demonstrate product thinking—such as identifying customer pain points or influencing roadmap decisions—advance further in screening. The differentiator is your ability to articulate systems thinking and cross-functional impact, which your BD experience positions you well for if framed strategically.