Project management CVs are screened on certification (PMP, CAPM, CSM), methodology (Agile, Scrum, Waterfall, Kanban), and the specific tool you ran the work in (Jira vs. Asana vs. MS Project) — three separate keyword axes that don't substitute for each other. "Managed cross-functional projects" without naming the methodology and the tool reads as generic to both an ATS filter and a hiring manager who has a specific stack in mind.
These are exact-match terms — not synonyms — that recruiters commonly build screening filters around for this role. If you genuinely have the experience, make sure the specific term appears in your CV, not just a paraphrase of it.
Example 1
Managed multiple projects and coordinated with different teams.
Led 4 concurrent Agile/Scrum projects (8-12 engineers each) in Jira, delivering all sprints on schedule across two quarters and cutting average cycle time by 18%.
Example 2
Responsible for project budgets and timelines.
Managed a $2.3M program budget across 3 vendors using MS Project, identifying a scope-creep risk early and renegotiating scope to stay within 4% of original budget at close.
Do I need a PMP to get past ATS filters, or does experience substitute?
Many postings hard-filter on "PMP" as a required or strongly preferred keyword, so if you have it, put it prominently — if you don't, lead with the equivalent methodology certifications you do have (CSM, CAPM) and state your years of hands-on PM experience as a number, since some ATS configurations accept an experience threshold as an alternate qualifier.
Should I pick one methodology (Agile or Waterfall) to keyword around, or list both?
List whichever you've genuinely run projects in — many PMs have real experience in both, and listing both is honest and covers postings on either side, but don't claim Agile fluency if your actual experience is Waterfall-only; a methodology-specific interview question will expose the gap fast.
How do I quantify project management impact if I wasn't tracking hard metrics at the time?
Reconstruct what you can defend: team size, budget size, number of stakeholders, timeline adherence, or scope changes — these are usually recoverable from memory or old status reports even without a formal KPI dashboard, and a number is more convincing to a reviewer than "successfully managed" with no scale attached.
More role-specific CV guides