Writing Job Descriptions (Outcome-Based)

Scope

Covers

• Turning a vague “we should hire X” into a clear role outcome + success scorecard
• Defining competency spikes (major/minor) instead of a generic laundry list
• Writing a high-signal job description that is honest about context (pace, constraints, trade-offs)
• Building a lightweight iteration loop to improve the JD after real candidate conversations

When to use

• “Write a job description / job posting for …”
• “Create a role scorecard / success profile for a new hire.”
• “Make this JD more high-signal (it’s generic and attracting everyone).”
• “Rewrite our JD around outcomes instead of responsibilities.”

When NOT to use

• You haven’t decided whether to hire vs restructure/contract/automation (do org planning first)
• You need a full interview loop, question maps, or structured interview design (use conducting-interviews)