IT Project Manager Job Description Template

In plain language: States the official job title, the department it sits within, and the direct reporting line — typically to a CIO, CTO, VP of Technology, or equivalent.

Common mistake: Listing only the name of a specific manager rather than the role title. When that manager leaves, the reporting line becomes ambiguous and may create a constructive dismissal risk if the successor's authority is disputed.

In plain language: A 2–4 sentence overview of the position's purpose — what the IT PM is accountable for delivering and the level of authority they hold.

Common mistake: Writing a role summary so broad it could describe any management role. If the summary does not mention IT, technology, or systems, it provides no useful boundary for performance review or dispute resolution.

In plain language: An itemized list of the specific tasks the IT PM owns — project planning, risk management, stakeholder communication, budget oversight, and team coordination.

Common mistake: Over-specifying tool names (e.g., 'Microsoft Project version 2019'). When tooling changes, the description becomes inaccurate and creates grounds to argue the role has materially changed.

In plain language: Lists the minimum technical knowledge — programming familiarity, infrastructure understanding, SDLC exposure — and any required or preferred certifications such as PMP, PRINCE2, or Agile.

Common mistake: Listing certifications as 'required' when they are genuinely preferred. Requiring a PMP for a junior-to-mid PM role narrows the talent pool without improving hire quality.

In plain language: States the minimum academic qualification — typically a bachelor's degree in computer science, information systems, or a related field — and any acceptable equivalents.

Common mistake: Mandating a specific degree without an equivalency clause. Jurisdictions including the UK and Canada increasingly scrutinize degree requirements that exclude candidates with equivalent practical experience, particularly in technical roles.

In plain language: States the salary range or pay grade, employment classification (exempt/non-exempt in the US; salaried/hourly elsewhere), and a reference to the applicable benefits program.

Common mistake: Publishing a salary range so wide it is meaningless (e.g., '$60,000–$150,000'). In jurisdictions with pay transparency laws — California, Colorado, New York, Illinois — ranges must reflect the actual budgeted compensation for the role.

In plain language: Requires the IT PM to maintain confidentiality of all proprietary systems, data, and project information and assigns ownership of any work product to the employer.

Common mistake: Including confidentiality language in the job description but not repeating it in the employment contract. Job descriptions are not always treated as binding contracts — the obligation must appear in the signed agreement to be reliably enforceable.

In plain language: Restricts the IT PM from soliciting the company's employees, clients, or vendors after departure, and may limit joining direct competitors for a defined period and geography.

Common mistake: Using a one-size-fits-all non-compete clause copied from a generic template, without calibrating the geographic scope or duration to the IT PM's actual level of access to competitive systems, client data, or strategic roadmaps.

In plain language: States the key performance indicators the IT PM will be evaluated against and the frequency of formal reviews — typically annual, with a mid-year check-in.

Common mistake: Omitting performance expectations entirely. Without documented KPIs, performance-based termination claims are harder to defend, and the employee has no objective basis for understanding what success looks like.

In plain language: Specifies which jurisdiction's employment law governs the document and includes a signature block confirming the employee has received, read, and understood the job description.

Common mistake: Omitting the acknowledgment signature block. Without a signed copy on file, the employer cannot demonstrate the employee was aware of the defined duties, qualifications, or restrictions — undermining performance management and termination defenses.

An IT Project Manager job description is a formal document that defines the duties, qualifications, reporting structure, compensation, and employment conditions for the IT PM role. It serves as the reference point for hiring decisions, performance reviews, and — when signed by both parties — as a legal record of agreed expectations. It is typically attached to or incorporated into the employee's employment contract.

At minimum: role title and reporting line, a focused role summary, core duties and responsibilities, required and preferred technical qualifications and certifications, education requirements, compensation range and employment classification, confidentiality and IP assignment obligations, non-solicitation terms, performance KPIs and review cadence, and a governing law and signature block. Missing any of these creates gaps that complicate performance management and termination.

A job description is not automatically a standalone binding contract in most jurisdictions. However, when signed by both parties and incorporated by reference into an employment agreement, its terms — including confidentiality, IP assignment, and non-solicitation — become enforceable as part of that agreement. Always pair a signed job description with a formal employment contract to maximize enforceability.

The most widely recognized certification is the PMP (Project Management Professional) issued by PMI. PRINCE2 Practitioner is common in the UK, EU, and government sectors. Agile-specific credentials — Certified Scrum Master (CSM) or PMI-ACP — are increasingly required for roles in software-focused environments. ITIL 4 certification is relevant for IT service management projects. Whether to require or merely prefer these depends on the seniority of the role and the nature of the projects managed.

An IT Project Manager leads a single project or a small cluster of related projects through defined phases — initiation, planning, execution, and closure — with a fixed scope, budget, and timeline. A Program Manager oversees a portfolio of interdependent projects aligned to a strategic business objective, managing dependencies and trade-offs across projects rather than delivering individual ones. Program Manager roles typically require an IT PM job description as a prerequisite or prior role.

As of 2025, mid-market IT Project Manager salaries in the US range from approximately $85,000 to $130,000 annually depending on industry, location, and project complexity. Senior or enterprise IT PMs in major metros can reach $150,000–$180,000. In the UK, ranges run £50,000–£85,000. In Canada, CAD $90,000–$130,000 is typical for major urban centers. In pay-transparency jurisdictions, disclose the actual budgeted range, not a wide placeholder.

For a standard internal hire, a well-structured template is usually sufficient. Engage an employment lawyer when the role involves access to highly sensitive IP or competitive systems that require a carefully scoped non-compete, when hiring across multiple jurisdictions with different employment standards, or when the organization operates in a regulated sector such as healthcare or financial services. A 30–60 minute legal review typically costs $150–$400 and is worthwhile for senior IT PM roles.

No. An employee job description sets out employment terms including benefits, classification, IP assignment, and termination conditions. Using it for a contractor can contribute to misclassification — the contractor may be reclassified as an employee, triggering back taxes, benefits liability, and employment standards obligations. Use an Independent Contractor Agreement and a separate scope-of-work document for contracted IT PMs.

The most commonly used IT PM KPIs include: on-time project delivery rate (target 85–95%), budget variance (target within 5–10% of approved budget), stakeholder satisfaction score (measured via post-project survey), scope change frequency (number of approved change requests per project), and defect or issue resolution time. Frame KPIs as targets rather than hard thresholds to preserve management discretion in performance reviews.