went through the APM cycle last year, got into two programs, declined one. spent a lot of time talking to people inside these programs after. here's what i wish i knew when i was writing my resume.
the programs i looked at: Google APM, Meta RPM, Microsoft PM Accelerate, LinkedIn PM, and a couple of smaller ones at Series B/C companies. the big three are incredibly competitive. the smaller ones move faster and are sometimes more legible about what they want.
what they are actually screening for in the resume: evidence you've shipped something. not designed, not specced, not planned. something that went live and reached users. even a student project or a side project counts if you can say 'launched to 200 users' or 'deployed to production.' a quantified impact bullet. even approximate. 'increased DAU by 12% through XYZ' is better than 'designed feature that improved engagement.' they know you're entry-level. they're not expecting miracles. they're checking if you think in terms of outcomes. cross-functional work. did you coordinate with engineers? designers? did something require you to align stakeholders who had different opinions? name it explicitly. technical literacy signal. you don't need a CS degree but you need something. ran an A/B test, wrote a SQL query to pull data, worked with an API. something.
format notes: one page, always. summaries are mostly skipped unless they're really strong. the order i used: education, relevant experience (even if it's internships), projects, skills. don't bury your most impressive thing.
biggest mistake i see in APM resumes: describing your tasks instead of your outcomes. 'worked with design team to iterate on onboarding flow' tells me nothing. 'redesigned onboarding flow with design, reduced drop-off from step 2 by 18%' tells me everything i need to know about how you think.
if you're doing the APM cycle this fall, start the resume now. it takes longer than you think to get the bullets right.