IT Project Manager resume example

Choose the right format for an IT Project Manager resume

Use a reverse-chronological format. Hiring managers and applicant tracking systems both expect it, and IT project management roles require a clear progression of scope — team sizes, budget authority, and project complexity should visibly grow across your timeline.

Keep the resume to two pages if you have more than eight years of experience; one page if you are early career. Use a clean single-column or mild two-column layout with consistent section headers. Avoid tables, text boxes, and graphics — many ATS platforms misparse them and drop your content entirely.

• Font: Calibri, Arial, or Georgia at 10–11pt body text
• Margins: 0.75–1 inch on all sides
• File format: PDF unless the job posting explicitly requests .docx
• Section order: Contact info → Summary → Work Experience → Skills → Certifications → Education

Write a professional summary that frames your PM specialty

Your summary should answer three questions in three to four sentences: What type of projects do you run (infrastructure, software delivery, ERP, cloud migration)? How large is your typical scope (budget, team, timeline)? What is your delivery record? Avoid vague openers like 'results-driven professional.'

Example: "PMP-certified IT Project Manager with nine years delivering enterprise software and cloud migration projects in financial services. Managed portfolios up to $4.2M and cross-functional teams of 18 across onshore and offshore locations. Consistent record of on-time delivery — 92% of projects closed within scope and budget over the past four years. Skilled in Agile, Waterfall, and hybrid methodologies using Jira, MS Project, and ServiceNow."

Write work-experience bullets that prove delivery, not just activity

Every bullet should follow an action-result structure and include at least one number. Quantify budget managed, team size, timeline, cost savings, risk reduction, or user impact. Recruiters for IT PM roles want evidence you shipped something, not just that you 'facilitated' or 'assisted.'

Aim for five to seven bullets per role. Front-load the most impressive metrics. Avoid listing tools in every bullet — tools belong in the Skills section.

• Led end-to-end migration of on-premises ERP system to Azure cloud for a 1,200-seat manufacturer, delivering 3 weeks ahead of a 14-month schedule and $180K under a $2.1M budget.
• Restructured sprint planning and backlog grooming process for a 12-person Scrum team, reducing average defect rate by 34% and improving velocity by 22% over two quarters.

Skills and certifications recruiters and ATS systems look for

IT PM job postings are keyword-dense. Your skills section needs to match the exact terminology used in postings — 'risk management' not just 'risk,' 'stakeholder communication' not just 'communication.' Split your skills into two or three clusters: methodologies, tools, and domain knowledge.

Certifications carry significant weight in IT PM hiring. PMP is the baseline expectation for mid-to-senior roles. CAPM works for early career. Agile-specific certs (PMI-ACP, CSM, SAFe 6.0) are increasingly required for software delivery roles. ITIL 4 Foundation matters for infrastructure and service management positions.

• Methodologies: Agile, Scrum, Kanban, Waterfall, SAFe, PRINCE2
• Tools: Jira, Confluence, Microsoft Project, ServiceNow, Smartsheet, Asana, Azure DevOps
• Certifications: PMP, PMI-ACP, CSM, CAPM, ITIL 4 Foundation, SAFe 6.0 Agilist
• Domain keywords: SDLC, risk register, change management, RAID log, resource allocation, vendor management, SLA governance

Education, licenses, and extras that strengthen your candidacy

List your highest degree first with institution, degree, and graduation year. For IT PM roles, a bachelor's in information systems, computer science, business, or engineering is standard. An MBA is a differentiator for senior or program director-level positions. You do not need to list GPA unless you graduated within the past two years and it is above 3.5.

Add a separate Certifications section below Education rather than burying certs inside it. Include the issuing body and the expiration or renewal date for PMP and ITIL — hiring managers verify these. If you hold a PMO leadership role or have published a case study, a brief 'Additional' section for board memberships or PMI chapter involvement can add credibility without padding.

• List PMP renewal date — it signals active maintenance of the credential
• Include LinkedIn URL only if your profile is complete and current
• Omit references, headshots, and 'References available upon request'

Mistakes to avoid

• ×Listing tools and methodologies only in bullet points rather than a dedicated Skills section causes ATS systems to miss them during keyword parsing.
• ×Using passive or vague language like 'responsible for managing projects' instead of active, outcome-focused verbs like 'delivered,' 'reduced,' or 'launched' makes your impact invisible to recruiters.
• ×Omitting budget and team-size figures from work experience is the single most common gap — IT PM compensation is directly tied to scope, and hiring managers use these numbers to benchmark you against the open role.
• ×Listing an expired PMP or a certification you are 'in progress' on without labeling it as such damages credibility, since PMI membership records are publicly searchable.

Frequently asked questions

Do I need a PMP certification to get hired as an IT Project Manager?

For mid-level and senior IT PM roles at companies with 500-plus employees, PMP is effectively a baseline filter — many postings list it as required or strongly preferred. Without it, you can still compete if you have strong delivery metrics and an Agile cert like CSM or PMI-ACP, particularly in software-focused organizations. If you are actively job searching without a PMP, enroll in a prep course and note 'PMP exam scheduled [month/year]' on your resume.

How far back should an IT Project Manager resume go?

Cover the last 10 to 15 years in detail and summarize anything older in one to two lines or omit it entirely. Technology stacks and methodologies from the early 2000s are rarely relevant and can date you. If a role older than 15 years included a landmark project — a large ERP rollout or a major infrastructure build — you can reference it briefly in your summary rather than in a full job entry.

Should an IT Project Manager resume include technical skills like coding or networking?

Include technical literacy that is directly relevant to the projects you manage — cloud platforms (AWS, Azure, GCP), ITSM tools, or database environments you have overseen — but do not list programming languages unless the role explicitly requires technical depth. Hiring managers want to see that you can speak credibly with engineers, not that you are competing with them. Framing it as 'working knowledge of SQL and REST APIs' is more accurate and appropriate than listing them alongside your PM tools.