Standard Operating Procedure: Job Description Development

This Standard Operating Procedure (SOP) outlines the mandatory process for creating, reviewing, and finalizing professional job descriptions. The objective is to ensure consistency, eliminate bias, maintain compliance with labor regulations, and attract top-tier talent by clearly defining core responsibilities, performance expectations, and organizational requirements.

1. Preparation and Role Definition

• Conduct a Stakeholder Intake Meeting: Meet with the hiring manager to identify the "why" behind the role, key pain points, and necessary immediate deliverables.
• Analyze Current Workflow: Review the team structure to determine where this role fits and what existing gaps it is intended to fill.
• Establish Key Objectives: Define the top three goals the incumbent must achieve in the first 90 days.
• Determine Compensation Banding: Consult with Finance/HR to confirm the salary range and budget alignment before proceeding.

2. Drafting the Content

• Structure the Header: Include Job Title, Department, Reporting Manager, FLSA Status (Exempt/Non-Exempt), and Location/Remote-Hybrid status.
• Write a Compelling Summary: Draft a 3-4 sentence "elevator pitch" that highlights the company culture and the impact this specific role will have on the mission.
• Define Core Responsibilities: Use bullet points starting with action verbs (e.g., "Manage," "Design," "Analyze"). Limit to 7-10 essential functions.
• Outline Qualifications (Must-Haves vs. Nice-to-Haves): Clearly distinguish between mandatory technical skills/education and preferred qualifications to avoid discouraging qualified applicants.
• Include Compensation and Benefits: Provide clear visibility into the salary range and unique perks/benefits to increase application quality.

3. Review and Compliance

• Conduct a Bias Audit: Use a gender-decoder tool to identify and remove coded language that may inadvertently favor one demographic over another.
• Ensure Legal Compliance: Verify that all requirements are job-related and consistent with ADA (Americans with Disabilities Act) and EEO guidelines.
• Internal Peer Review: Have the hiring manager and a departmental peer review the draft for technical accuracy and tone consistency.
• Final Sign-off: Obtain written approval from HR and the Department Head before the role is moved to the "Open" status.

Pro Tips & Pitfalls

• Pro Tip: Avoid generic "catch-all" phrases like "other duties as assigned"—keep them limited so candidates understand the role's scope.
• Pro Tip: Use "We" and "You" language to foster a collaborative and candidate-centric tone.
• Pitfall: Avoid over-inflating qualifications. Requesting a Master’s degree for a role that only requires a Bachelor’s often results in a smaller, less diverse applicant pool.
• Pitfall: Never copy and paste from an old job description without an audit. Legacy requirements are often outdated and may reflect obsolete software or internal processes.

Frequently Asked Questions (FAQ)

Q: How often should job descriptions be updated? A: Job descriptions should be reviewed at least annually or whenever the role significantly changes due to internal restructuring or shifts in technology/tools.

Q: What is the ideal length for a job description? A: A high-converting job description should be between 400 and 600 words. Anything longer often leads to candidate drop-off during the reading phase.

Q: Should I include a specific list of every tool used in the office? A: Focus on "Core Competencies" rather than every piece of software. If a tool is essential, include it, but avoid listing every platform used for administrative tasks to prevent the description from becoming a laundry list.