Job Description Template for Project Manager

Standard Operating Procedure: Project Manager Job Description Generation

Template Registry Engineering Standards

---

1. Document Control Block

---

2. Executive Summary & Purpose

This SOP establishes the standardized workflow for constructing a high-fidelity Project Manager (PM) job description. The objective is to eliminate role ambiguity, ensure alignment with departmental performance metrics, and optimize candidate filtering through standardized competency mapping.

---

3. Scope & Prerequisites

• Scope: Applies to all recruitment requests for Project Management positions (Level I–IV).
• Required Tools: ATS (Greenhouse/Lever), Role Competency Matrix (Internal), Markdown Editor, HRIS Integration.
• PPE: N/A (Digital environment).

---

4. Roles & Responsibilities (RACI Matrix)

---

5. Step-by-Step Procedure

Phase I: Role Specification & Leveling

• Define the project lifecycle management methodology (Agile, Waterfall, or Hybrid).
• Determine the "Complexity Score" (1-10) of the target portfolio.
• Confirm salary banding against current market intelligence (Quarterly benchmarks).

Phase II: Content Drafting

• Insert core mandatory headers: Role Summary, Key Accountabilities, Required Qualifications, Preferred Skills.
• Apply the "3:2 Ratio": 3 must-have technical requirements (e.g., PMP, Jira mastery, Budgeting) for every 2 soft-skill imperatives (e.g., Stakeholder management, cross-functional leadership).
• Define 3 explicit "KPIs of Success" for the first 90 days.

Phase III: Optimization & Review

• Perform a bias-check using the Gender Decoder tool.
• Audit for "Passive-Aggressive" qualifiers (e.g., "Rockstar," "Ninja").
• Final sign-off by HRBP and Hiring Manager via internal approval workflow.

---

6. Quality Assurance & Pro-Tips

• Quality Metric: A job description is considered "Optimized" if the resume-to-interview conversion rate for qualified candidates exceeds 15%.
• Pro-Tip (The "Vance" Principle): Do not list "Years of Experience" as a hard filter. List "Project Complexity Handled" instead. A PM who managed a $5M migration in 2 years is higher value than a PM who managed a $100k maintenance task in 10 years.
• Common Pitfall: Listing "Multi-tasking" as a skill. Replace with "High-context switching capability and prioritization strategy."

---

7. Frequently Asked Questions

Q: Should I include the specific tech stack? A: Yes. PMs operating in a Java/Cloud-native environment require different risk-mitigation skill sets than those in Creative or Hardware-based environments. Include the primary stack as a "Required" field.

Q: How do we handle candidates who lack a PMP certification? A: Treat certification as a proxy for methodology knowledge. If the candidate possesses equivalent experience (as defined in the Role Competency Matrix), grant an equivalence waiver.

Q: Is it necessary to list a salary range? A: Yes. Transparency correlates with a 30% reduction in time-to-hire by disqualifying candidates misaligned with budget parameters before the screening phase.

---

End of Document. Authorized for use by Template Registry Recruitment Operations.