Program Manager Job Description Template

In plain language: States the exact job title, the department or business unit, the position's place in the org chart, and the title of the direct supervisor.

Common mistake: Using an inflated or inconsistent title that doesn't match payroll or HR systems — creating misalignment in compensation benchmarking and triggering re-grading disputes at offer stage.

In plain language: A 3–5 sentence overview of the role's primary purpose, the outcomes it is accountable for, and how it fits into the broader organization.

Common mistake: Writing a summary so broad it could apply to any manager — leaving candidates and evaluators with no clear picture of what makes this role distinct from a project manager or operations manager.

In plain language: A structured list of the key duties the employee is expected to perform, written as action-verb statements that are specific enough to form the basis of a performance review.

Common mistake: Listing generic duties like 'manage projects and communicate with stakeholders' without specifying scope, cadence, or decision-making authority — making performance management ambiguous.

In plain language: The minimum education, certifications, years of experience, and hard skills an applicant must have to be considered for the role.

Common mistake: Setting education requirements (e.g., 'bachelor's degree required') that are not demonstrably related to job performance — creating disparate-impact liability under EEOC guidelines in the US.

In plain language: Supplementary credentials or experience that differentiate strong candidates but are not eliminatory if absent.

Common mistake: Treating preferred qualifications as de facto requirements during screening — effectively excluding qualified candidates and undermining the legal distinction between required and preferred.

In plain language: The leadership, communication, and problem-solving attributes the employer expects the program manager to demonstrate on the job.

Common mistake: Including subjective competency language like 'must be a team player' or 'excellent interpersonal skills' without behavioral indicators — language that cannot be assessed objectively during hiring or performance review.

In plain language: States the compensation range, FLSA classification (exempt or non-exempt), employment type (full-time, part-time, contract), and benefits eligibility.

Common mistake: Omitting the compensation range in jurisdictions where pay transparency is legally required — exposing the employer to regulatory penalties and reputational risk in markets where salary bands are expected.

In plain language: Describes the work environment, travel expectations, remote or on-site requirements, and any physical demands relevant to ADA compliance.

Common mistake: Omitting physical requirements entirely or listing demands unrelated to actual job functions — both create ADA compliance exposure and can be challenged during the reasonable-accommodation process.

In plain language: A required declaration affirming the employer's commitment to non-discriminatory hiring practices across all protected classes.

Common mistake: Using a boilerplate EEO statement that omits protected classes added by state or local law — for example, failing to include sexual orientation in jurisdictions where it is explicitly protected.

In plain language: Confirms the employee has read, understood, and agreed to the job description as a condition of employment or continued employment.

Common mistake: Treating the job description as informational rather than having it signed — losing the evidentiary value it provides in wrongful termination, misclassification, or scope-of-duty disputes.

A program manager job description is a formal document that defines the responsibilities, qualifications, reporting structure, compensation range, and employment terms for a program manager role. It serves as both a recruiting tool — posted on job boards to attract candidates — and a legal record — attached to the employment agreement to establish the contractual scope of the role. A signed job description is the employer's primary evidence in performance management and scope-of-duty disputes.

A project manager oversees a single, defined project with a specific start date, end date, and deliverable. A program manager oversees a group of related projects managed in a coordinated way to achieve a strategic outcome that individual projects cannot deliver alone. Program managers typically operate at a higher organizational level, manage larger budgets and cross-functional teams, and are accountable for long-term benefit realization rather than individual project delivery.

Typical required qualifications include a bachelor's degree in a relevant field (or equivalent experience), 5–8 years of program or project management experience, and a recognized certification such as PMP, PgMP, or PRINCE2. Preferred qualifications often add an MBA, experience with Agile or SAFe methodologies, and familiarity with tools like Jira, Smartsheet, or MS Project. Required credentials should have a documented job-relatedness justification to avoid EEOC disparate-impact exposure.

No federal or provincial law mandates a signed job description, but obtaining a signature is strongly recommended. A signed acknowledgment proves the employee received and understood their role expectations, which is material evidence in performance management proceedings, wrongful termination claims, and reasonable-accommodation disputes. Execute the signature block alongside — or as part of — the employment agreement before the employee's first day.

It depends on the posting location. California, New York, Colorado, and Washington require employers to disclose the pay range for any advertised position. Several additional municipalities have adopted similar rules. Non-disclosure in covered jurisdictions triggers regulatory fines and applicant complaints. Maintain a current compliance calendar for pay-transparency requirements in every location where you post roles.

Yes — and this is one of its primary legal functions. Attaching a signed job description to an employment agreement as Schedule A establishes the contractual scope of duties, supports IP assignment clauses, and provides the factual basis for termination-for-cause provisions. Courts and arbitrators regularly rely on the job description when determining whether an employer's performance expectations were communicated and agreed to.

The FLSA classification line should state whether the role is Exempt or Non-Exempt, the exemption category relied upon (Executive, Administrative, or Professional), and the basis for the classification. Program managers are typically classified as exempt under the Administrative or Executive exemption, but the classification must be supported by a duties test — not merely by salary level. Misclassification of a non-exempt employee as exempt triggers up to three years of back overtime under federal law.

Review job descriptions at minimum annually and whenever the role's responsibilities materially change — for example, when the program manager takes on a new portfolio, gains direct reports, or absorbs duties from an eliminated position. Have the employee re-acknowledge material changes in writing. A job description that is more than 18 months out of date is a liability, not an asset, in any employment dispute.

An equal opportunity employer statement declares that the company does not discriminate in hiring based on race, color, religion, sex, national origin, age, disability, or other protected characteristics. Federal contractors in the US are legally required to include EEO language in job postings. Non-contractors are not federally mandated to include it, but omission creates reputational risk and may conflict with state or local fair employment laws. Always tailor the statement to include protected classes required by the laws of your specific posting location.