What hiring teams screen for
- Project scale: budget, duration, team size, number of stakeholders and any cross-functional or vendor complexity.
- Delivery record: on time, on budget and to scope, and what you did when plans changed.
- Methodology: waterfall, agile, scrum, kanban or hybrid, matched to the posting.
- Certifications such as PMP, CAPM, PMI-ACP, PRINCE2 or a scrum certification.
- Tools: scheduling, tracking and reporting software, and how you communicated with executives.
Certifications: how to list them
- PMP (Project Management Professional). Issued by the Project Management Institute after verified project-leadership experience and an exam. List it after your name (for example “Jordan Lee, PMP”) and again under Certifications with the year, so both a human and a keyword search see it.
- CAPM and PMI-ACP. CAPM suits early-career professionals, and PMI-ACP signals agile experience. List the full name once and the acronym, with the year earned.
- PRINCE2. Common in the UK, Europe and public-sector work. State the level (Foundation or Practitioner). If the posting names PRINCE2, make sure it appears in your skills and certifications.
- Scrum and scaled-agile certifications. Certified ScrumMaster (CSM), PSM and SAFe credentials are screened for in agile and software roles. Add the issuer and year.
- Six Sigma and domain credentials. Lean Six Sigma belts help in operations and manufacturing. Add them if relevant, and mention the project you completed to earn them when you can.
ATS keywords for project managers
Use these only where they are true for you, and mirror the exact wording of the posting you are applying to. An applicant tracking system matches phrases, so “Project Management Professional” and “PMP” can be treated as different things.
Planning and control
scope managementproject schedulebudget managementWBScritical pathGanttresource allocationbaselinechange controlrisk management
People and delivery
stakeholder managementcross-functional teamsvendor managementRACIstatus reportingexecutive communicationteam leadershipPMO
Methods and tools
agilescrumkanbanwaterfallhybridMS ProjectJiraAsanaSmartsheetConfluenceburndown
Section by section: building the resume
1. Header with certification after your name
Name and credentials on one line, then contact details and city. Credentials after your name are scanned by recruiters, and they remain in the text for keyword searches.
2. Summary: scale and method in three lines
Say how many years you have led projects, the kind of projects, the largest budget and team, and your method.
PMP-certified project manager with [X] years delivering [software / construction / healthcare] programs up to $[X]M with teams of [X]. Hybrid agile and waterfall, with a record of on-time delivery and clear executive reporting.Illustrative only. Replace the bracketed placeholders with your own real numbers; never invent them.
3. Experience: lead each role with a portfolio line
Open each role with one line giving the portfolio you ran: number of projects, total budget, team size and sector. Then use bullets that show how you controlled scope, schedule and cost, and the result. Use numbers: budget size, schedule saved, savings, defects or incidents prevented, stakeholders managed.
Led a $[X]M ERP migration across [X] sites with a team of [X]; held scope through [X] change requests and delivered [X] weeks early and [X]% under budget.Illustrative only. Replace the bracketed placeholders with your own real numbers; never invent them.
4. Show how you handle risk and change
Add at least one bullet where something went wrong and what you did: a risk you caught early, a vendor you replaced, a scope change you negotiated. This is what separates a coordinator from a project manager.
5. Tools and methods
Use a short skills block: methodologies, scheduling and tracking tools, and reporting tools. Use the posting’s exact terms, such as “Jira” or “Microsoft Project”, instead of a generic “project software”.
6. Education and training
Degree, school and year. Add the training hours behind your certifications, such as the 35 contact hours that PMP candidates complete, only if the posting asks for them.
7. Format and length
One page up to about eight years, two pages beyond, and more only if you apply for a federal role that requests detail. Use a single-column layout and standard headings.
Common mistakes to avoid
- Listing responsibilities (“coordinated schedules”) without budget, team size or outcome.
- Leaving PMP off the first lines, or putting the acronym only and never the full name.
- Claiming agile or waterfall expertise without naming a project where you used it.
- Omitting the cost side: schedule and scope without budget looks incomplete for senior roles.
- Using the same resume for construction, software and healthcare projects. The vocabulary differs; mirror the posting’s.
- Naming tools you only observed, such as Jira, rather than used.
Where to apply, and what the ATS will do
Project-manager postings are common on LinkedIn and Indeed and on the career pages of large employers, which commonly use applicant tracking systems such as Workday, Greenhouse and iCIMS. Recruiters search by certification, methodology and tool names, then by industry.
- Company career pages for direct applications, and LinkedIn for networking and alerts.
- Industry boards for your sector, such as construction, healthcare IT or government contracting.
- Contract and consulting roles go through staffing firms that ask for a tailored one-page summary.
- Make the certification and methodology visible in your LinkedIn headline, so recruiters find you in a search.
Want the AI to tailor it for you? Open the project manager resume tailoring page page, paste your resume and a job posting, and get a tailored version in about 30 seconds.
Related guides: Resume writing for accountants • Resume writing for software engineers