I'm a 2nd year APM trying to move to a mid-size company for a PM II role. I've gotten feedback from four different people and all four said something different. So I'm going to share what I've compiled and ask for reactions.
Context: I'm at a large tech company, 2 years in. My APM program ends in July. I have two product areas I can claim: a consumer notification feature (launched, got to 5M users) and an internal tooling project that was cancelled. I need to decide what to keep, cut, or reframe.
Things I've been told: "Lead with impact, not features" - fine but hard when you're an APM and the impact metrics went to the senior PM on the team "Show you can work with eng" - I do this but it reads like soft skills, unsure how to make it concrete "One page is outdated, you can do two" - I've heard the opposite equally. currently at 1.5 pages "Cut the cancelled project" - conflicted on this because I learned a lot from it
Here's my actual question: for a PM resume, is a 1.5 page resume a problem? Most PM job descriptions I see say nothing about length. And the cancelled project, do I include it and just frame it neutrally, or does it raise red flags?
Also curious what specific PM resume sections people are finding useful in 2026 besides experience and skills. I've seen some people do a "selected launches" section and some do a product portfolio link. Worth it?
5 replies
jordan_pm
1.5 pages is fine, stop worrying about it. Include the cancelled project. Every honest PM has a cancelled project. The question is whether you frame it as "we built a thing and it died" vs "we validated this wasn't the right bet, here's what we learned, here's how I influenced the decision." The second version shows product judgment. That's what PM interviews are actually testing.
qa_quinn
"Show you can work with eng" is vague advice. Make it concrete: name the specific engineering trade-offs you influenced. "Worked with eng to descope X feature to hit the Q3 deadline without breaking existing API contracts" is a sentence that tells me you understand tech constraints. Soft isn't the problem, vague is.
director_dee
Product portfolio link: yes, include it if it's real and has substance. Don't link a notion doc with 3 bullets. If you've written up your key product decisions somewhere, that's better than a resume bullet. I've hired PMs where the write-up was the differentiator.
apm_aisha
Ok this is helpful. I have a notion doc that's basically my PRD templates and launch retrospectives. I could clean that up and link it. Appreciate the nudge.
pm_priya
For "show you work with eng" specifically. Try writing it as a constraint problem you navigated. "Partner with eng across 4 squads, managing a shared dependency queue that blocked 3 concurrent launches." That's not soft skills, that's coordination at scale.