Golden Example — Job Description Optimization (Consultant Process)

The Benchmark

Status: AWAITING FIRST DEPLOYMENT

The golden example will be drawn from the first completed client deployment that passes full QC. This file will be updated with the specific deliverable set, structural analysis, and design patterns once that deployment exists.

What the Golden Example Will Demonstrate

Position Profile Benchmark

• Role purpose that explains WHY, not just WHAT
• Must-haves clearly distinguished from nice-to-haves with explicit designation rationale
• Organizational context that tells the reader what's happening in the organization right now
• Competency expectations written in behavioral terms, not generic labels
• Success measures at defined time horizons

Job Description Benchmark

• Responsibilities written as actions, not competencies
• Qualifications calibrated to the actual role (no requirement inflation)
• Reporting structure that shows organizational placement, not just "reports to [title]"
• Compliance elements present where required

Job Ad Benchmark

• Opens with what makes the opportunity compelling, not with a requirements list
• Written for the target candidate's perspective, not the organization's needs
• Tone matched to the target audience and publication channel
• Clear application method and timeline

Cross-Deliverable Consistency

• Same must-haves across all three documents (no requirements in the ad that aren't in the profile)
• Same role purpose, adapted for each audience
• Same compensation context, disclosed appropriately per deliverable type

Interim Specifications

Position Profile Structure

1. Role Title and Organizational Placement — Title, department, reporting structure, direct reports
2. Role Purpose — Why this role exists (2-3 sentences, not a responsibility list)
3. Organizational Context — What's happening in the organization that makes this role critical right now
4. Key Responsibilities — 6-10 major responsibility areas, each with 1-2 sentences of detail
5. Must-Have Requirements — Explicitly designated, with brief rationale for why each is non-negotiable
6. Nice-to-Have Requirements — Preferred qualifications that strengthen a candidacy but don't gate it
7. Competency Expectations — Behavioral expectations beyond technical qualifications
8. Key Relationships — Internal and external stakeholders this role interacts with
9. Success Measures — What success looks like at 6 months and 12 months
10. Compensation Range — Market control point and range, with context
11. Working Conditions — Location, travel, remote/hybrid/on-site, physical requirements

Job Description Structure

1. Role Title and Classification — Title, department, FLSA status, employment type
2. Role Summary — 3-4 sentence overview
3. Responsibilities — Detailed action-based responsibilities
4. Required Qualifications — Education, experience, certifications, technical requirements
5. Preferred Qualifications — Nice-to-haves
6. Reporting Structure — Reports to, direct reports, key peers
7. Working Conditions — Location, travel, physical requirements
8. Compensation and Benefits Overview — Range, benefits summary
9. Equal Opportunity Statement — Standard or organization-specific language

Job Ad Structure

1. Headline — Compelling, specific, not just the role title
2. Opening Hook — 2-3 sentences on why this opportunity matters (for the candidate, not the organization)
3. About the Organization — Mission, culture, what makes it a place people want to work
4. About the Role — What the person will do and why it matters (responsibilities rewritten for attraction)
5. Who You Are — Requirements reframed as identity ("You've led organizations through transformation" vs. "10+ years of change management experience required")
6. What We Offer — Compensation, benefits, growth, culture — the candidate's value proposition
7. How to Apply — Clear instructions, timeline, what to expect after applying

What the Golden Example Does NOT Provide

Role-specific content, must-have requirements, organizational context, or compensation ranges for your deliverable. All content comes from extraction.