Job Description Template for Company

Standard Operating Procedure: Enterprise Job Description Engineering

Document ID: SOP-TR-HR-042
Effective Date: October 24, 2023
Version: 3.2.0
Review Cadence: Annual
Owner: Julian Vance, Chief Architect, Template Registry

---

1. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the institutional engineering standard for authoring, validating, and deploying Job Descriptions (JDs) across Template Registry and its subsidiaries. Job descriptions function as mission-critical systems architecture documents: they dictate human resource allocation, define behavioral and technical operational boundaries, ensure regulatory compliance (FLSA, EEOC, GDPR), and establish the baseline metrics for performance engineering.

Adherence to this SOP is mandatory for all hiring managers, HR business partners (HRBPs), and organizational architects to eliminate ambiguity, mitigate legal liability, and optimize talent pipeline conversion rates.

---

2. Scope & Prerequisites

2.1 Scope

This protocol applies to all internal, external, temporary, and contractor job requisitions globally, ranging from entry-level operational roles to executive leadership.

2.2 Prerequisites & Tools

• Access Control: Verified permissions within the HRIS (Workday) and Applicant Tracking System (Greenhouse/Lever).
• Software: Markdown editors, Enterprise Taxonomy Dictionary (ETD v4.2), and Legal Compliance Checker (LCC-2023).
• Reference Artifacts: Approved departmental organizational chart, leveled competency matrices, and current compensation bands.
• Safety/PPE: N/A (Administrative workflow; standard ergonomic workspace guidelines apply).

---

3. Roles & Responsibilities (RACI Matrix)

• Definitions: Responsible (does the work), Accountable (owns the outcome), Consulted (provides input), Informed (kept updated).

---

4. Step-by-Step Procedure

Phase 1: Requirements Gathering & Scoping

• 1.1 Convene alignment session between Hiring Manager and HRBP using the Template Registry Intake Questionnaire.
• 1.2 Determine organizational leveling (e.g., IC3, IC4, M1) mapped against the Enterprise Competency Matrix.
• 1.3 Audit existing job architecture to prevent role duplication or taxonomy drift.

Phase 2: Structural Assembly

• 2.1 Initialize a blank document utilizing the standardized Template Registry Job Description Schema (Section 4.1).
• 2.2 Draft the Role Overview (The Hook): Synthesize the mission, department impact, and reporting structure into a maximum of 3 declarative sentences.
• 2.3 Formulate the Core Responsibilities (The Stack): List 5–7 bullet points prioritized by operational weight using active verbs (e.g., Architect, Execute, Validate).
• 2.4 Define Required Qualifications (Must-Haves): Establish objective, verifiable baseline criteria (e.g., specific technology stacks, years of verified domain experience, required certifications).
• 2.5 Specify Preferred Qualifications (Nice-to-Haves): Detail secondary competencies that accelerate ramp-up time.

Phase 3: Compliance & Optimization Audit

• 3.1 Run the draft through the Inclusive Language & Legal Scanner to eradicate gender-coded terminology, ableist language, and non-inclusive phrasing.
• 3.2 Validate FLSA classification (Exempt vs. Non-Exempt) and local labor law compliance with Legal/Compliance.
• 3.3 Verify compensation alignment with Compensation & Benefits to ensure salary range transparency compliance.

Phase 4: Sign-off & Deployment

• 4.1 Secure formal electronic sign-off from the Accountable party (HRBP) and Hiring Manager.
• 4.2 Ingest the finalized document into the ATS and publish to the internal/external career portals.

---

5. Quality Assurance & Pro-Tips

5.1 Best Practices (Pro-Tips)

• The Rule of Thirds: Allocate 33% of the JD to company mission/culture, 33% to day-to-day operational execution, and 33% to growth and developmental opportunities.
• Avoid the "Purple Squirrel" Fallacy: If a candidate profile requires more than three distinct, specialized domain masteries, the role must be split into two separate requisitions or the qualifications re-leveled.
• Precision over Fluff: Eliminate corporate jargon (e.g., "rockstar," "ninja," "fast-paced environment"). Define the operational realities explicitly (e.g., "high-throughput deployment cycles").

5.2 Common Pitfalls

• Conflating Tasks with Outcomes: Listing "manages database" instead of "optimizes database query latency to sub-50ms thresholds."
• Outdated Skill Stacks: Retaining legacy technologies in requirements when the engineering stack has shifted.

5.3 Metric Thresholds

• Time-to-Fill (TTF): Optimized target is $\le 45$ calendar days from requisition approval to offer acceptance.
• Qualified Applicant Conversion Rate: Minimum threshold of $12%$ of total applicants passing initial recruiter screen.

---

6. Frequently Asked Questions (FAQ)

Q: How do I handle sudden scope changes for an open requisition mid-hiring cycle?
A: Any modification to required qualifications or level post-publication invalidates the current ATS instance. You must unpublish the role, execute an expedited change-control review with Compensation and HRBP, update the SOP artifact version, and re-publish.

Q: Are degree requirements mandatory for technical engineering roles?
A: No. Template Registry enforces an equivalency standard. Degree requirements may be substituted with demonstrable open-source contributions, portfolio artifacts, or equivalent years of professional systems engineering experience, provided it is explicitly noted in the JD schema.