Free, ready to customize

Project Manager Job Description Prompt

A project manager job description should make delivery responsibility concrete: what is being delivered, who contributes, and which decisions the manager can make. Use this prompt to describe project planning, dependencies, risk, and stakeholder coordination without implying unlimited authority over every team. It works best when you supply examples of project scope and the organization’s delivery method. The resulting posting should show how the person keeps work moving and makes decisions visible when plans change.

Free to copy. No sign-up required.

Go to the copy-ready prompt

Start with the right scope

Separate managing a defined project from owning an ongoing business operation or setting a product roadmap. Explain whether the manager controls budget, assigns work directly, or coordinates contributors through functional leaders. State the typical project duration, number of concurrent initiatives, and customer involvement if known. Ask for requirements grounded in planning and communication rather than a default certification list. The description should show how success depends on sound coordination, timely escalation, and agreed delivery criteria.

Confirm these details with your hiring manager

Name the types and approximate complexity of projects rather than inventing a delivery portfolio.
Clarify budget authority, sponsor support, and how contributors are assigned.
State the delivery approach and stakeholder reporting needs actually used by the organization.

Copy, customize, draft

Your ATS-ready Project Manager prompt

Copy the prompt below, replace the bracketed details, and paste it into your preferred AI tool. It creates a first draft for review, rather than a finished job offer.

Act as an experienced HR copywriter. Draft an ATS-friendly Project Manager job description using plain language, standard headings, and concise bullet points. Separate required competencies from optional skills. Avoid tables, graphics, vague personality labels, and unsupported claims. Do not claim compatibility with every applicant tracking system.

COMPANY CONTEXT TO COMPLETE
Company: [Company name and what it does]
Location and work arrangement: [Location; on-site, hybrid, or remote]
Schedule and employment type: [Hours, time zone, employment type]
Reporting line: [Manager and team]
Culture: [Observable working practices]
Approved compensation and benefits: [Pay range and confirmed benefits]
Application process: [Application link and accommodation contact]

ROLE PURPOSE
Help teams deliver defined projects with clear plans, visible priorities, and informed decisions. You will coordinate contributors, track dependencies, maintain project information, and surface risks early enough for stakeholders to respond. Working with project sponsors and functional leads, you will keep scope, timing, and responsibilities aligned while documenting changes and supporting a practical handover when work is complete.

CORE RESPONSIBILITIES TO ADAPT
- Develop and maintain project plans with agreed scope, dependencies, owners, and completion criteria.
- Coordinate contributors and facilitate meetings that resolve issues or clarify decisions.
- Track progress, risks, and changes while keeping stakeholders informed through useful reporting.
- Escalate resource constraints and decision needs to the appropriate sponsor or functional lead.
- Support project closure, handover, and lessons learned with the teams receiving the work.

REQUIRED CORE COMPETENCIES
- Experience coordinating projects with multiple contributors and interdependent tasks.
- Ability to build practical plans and communicate scope, timing, and risks clearly.
- Skill facilitating decisions and following up without relying on direct reporting authority.
- Ability to maintain accurate project records and adapt plans when assumptions change.

OPTIONAL NICE-TO-HAVE SKILLS
- Familiarity with the organization’s project tracking tools.
- Experience in the industry or project type involved.
- Relevant project management training or certification where useful for the work.

TOOLS TO CONFIRM
Examples only: Asana, Jira, Microsoft Project, spreadsheets, and shared documentation. Describe the workflow rather than requiring every platform. Treat these as examples. Include only tools the hiring manager confirms, and distinguish day-one requirements from tools that can be learned.

ROLE-SPECIFIC HIRING CONTEXT
Separate managing a defined project from owning an ongoing business operation or setting a product roadmap. Explain whether the manager controls budget, assigns work directly, or coordinates contributors through functional leaders. State the typical project duration, number of concurrent initiatives, and customer involvement if known. Ask for requirements grounded in planning and communication rather than a default certification list. The description should show how success depends on sound coordination, timely escalation, and agreed delivery criteria.

PROPOSED SUCCESS MILESTONES FOR REVIEW
Day 30: By day 30, understand active projects and establish a shared view of owners, milestones, and risks.
Day 90: By day 90, coordinate an agreed project phase with current reporting and documented decisions.
Year 1: By year one, demonstrate consistent delivery practices and useful lessons applied across assigned projects.

Before drafting, identify any missing information that changes the scope of this role. Retain clear bracketed placeholders for unanswered factual details. Do not invent salary, benefits, quotas, team size, certifications, degrees, or years of experience. Use inclusive, job-related language. Output a role overview, role details, responsibilities, required competencies, optional skills, proposed milestones, and how to apply. Finish with a short hiring-manager review checklist.

See the result

Sample Project Manager job description

Illustrative sample, not a live AI result or an open vacancy. Confirm the role’s actual requirements, tools, and proposed milestones before publishing.

Project Manager

Role overview

Help teams deliver defined projects with clear plans, visible priorities, and informed decisions. You will coordinate contributors, track dependencies, maintain project information, and surface risks early enough for stakeholders to respond. Working with project sponsors and functional leads, you will keep scope, timing, and responsibilities aligned while documenting changes and supporting a practical handover when work is complete.

Role details

Company: [Company name]
Location: [Location and work arrangement]
Schedule: [Employment type and hours]
Reports to: [Manager and team]
Compensation: [Approved pay range and benefits]

Key responsibilities

Develop and maintain project plans with agreed scope, dependencies, owners, and completion criteria.
Coordinate contributors and facilitate meetings that resolve issues or clarify decisions.
Track progress, risks, and changes while keeping stakeholders informed through useful reporting.
Escalate resource constraints and decision needs to the appropriate sponsor or functional lead.
Support project closure, handover, and lessons learned with the teams receiving the work.

Required core competencies

Experience coordinating projects with multiple contributors and interdependent tasks.
Ability to build practical plans and communicate scope, timing, and risks clearly.
Skill facilitating decisions and following up without relying on direct reporting authority.
Ability to maintain accurate project records and adapt plans when assumptions change.

Nice-to-have skills

Familiarity with the organization’s project tracking tools.
Experience in the industry or project type involved.
Relevant project management training or certification where useful for the work.

Proposed success milestones

Day 30: By day 30, understand active projects and establish a shared view of owners, milestones, and risks.
Day 90: By day 90, coordinate an agreed project phase with current reporting and documented decisions.
Year 1: By year one, demonstrate consistent delivery practices and useful lessons applied across assigned projects.

How to apply

Submit [application materials] through [application process]. For application accommodations, contact [designated contact].

Refine the Project Manager draft

Accountability without authority

A project manager often coordinates colleagues who report to someone else. Explain how priorities are agreed, who can resolve resource conflicts, and which sponsor makes scope or budget decisions. Avoid holding the role solely accountable for deadlines without describing that support. Clear decision boundaries make the posting more credible and help candidates understand how they can influence delivery when competing priorities arise across the organization.

Confusing projects with product ownership

Project management focuses on coordinating defined work toward an agreed outcome. Product management generally includes deciding which customer problems deserve investment and how a product should evolve. Some roles combine these responsibilities, but that should be stated. Ask the prompt to identify the actual decision rights instead of borrowing attractive product language that obscures who sets priorities, accepts tradeoffs, and approves changes to the plan.

Ceremonies replacing useful outcomes

A long list of meetings and reports can make project management sound administrative rather than purposeful. Describe what each practice achieves, such as resolving a dependency or getting a sponsor decision. Milestones should reward clarity, coordination, and completed handovers, not simply more status updates. Avoid fixed delivery improvement percentages unless the organization has agreed baselines and a measurement method relevant to the projects assigned.

Questions before you publish

Do I need to specify a delivery methodology?

Name the approach if it materially shapes the day-to-day work, but describe the practices candidates need to use. A team may combine iterative planning with fixed contractual milestones, so a single label may not tell the whole story. Explain how work is planned, changed, and accepted. Require a specific certification only when it reflects your actual criteria rather than adding it automatically to a general coordination role.

How should the role describe budget responsibility?

Distinguish tracking a budget from approving expenditure or setting financial commitments. State whether the manager prepares forecasts, reports variances, authorizes purchases, or escalates decisions to a sponsor. Supply the real arrangement in the intake so the prompt does not imply authority the role lacks. If budget size is sensitive or variable, describe the responsibility without publishing an invented or overly precise amount.

Can the milestones apply to long projects?

Yes, but use milestones that fit the project lifecycle. A ninety-day target might involve approved planning, a completed discovery phase, or a coordinated release rather than finishing the entire project. Describe the phase and acceptance criteria clearly. The year-one example should reflect work the manager can influence, and it should account for dependencies such as sponsor decisions, vendor schedules, and resource availability.