Job Description Template for Hiring New Employees

Standard Operating Procedure: Creation, Approval, and Deployment of Job Description Templates

---

1. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the institutional framework for engineering, validating, and deploying standardized job description templates across Template Registry. The purpose of this procedure is to ensure legal compliance, eliminate structural bias, optimize talent acquisition funnels through targeted keyword mapping, and maintain organizational taxonomy consistency. Adherence to this SOP is mandatory for all personnel involved in headcount requisition and talent sourcing.

2. Scope & Prerequisites

Scope

This procedure applies to all internal and external hiring initiatives across all engineering, product, operations, and administrative divisions within Template Registry.

Prerequisites & Software Stack

• Access Control: HRIS Administrator and Greenhouse ATS (Applicant Tracking System) Write Permissions.
• Tooling: Workday (for compensation bands), Greenhouse (for pipeline publishing), and the Template Registry Master Competency Matrix (internal knowledge base).
• Legal/Compliance Framework: EEOC compliance guidelines, local pay transparency statutes, and ADA physical/cognitive requirement standards.

3. Roles & Responsibilities

---

4. Step-by-Step Procedure

Phase 1: Requisition Analysis and Data Gathering

• 1.1 Review the approved headcount requisition ticket in Greenhouse and verify budgetary alignment with the Finance Department.
• 1.2 Audit existing job description templates in the repository to identify structural drift or obsolescence compared to market standards.
• 1.3 Interview the Hiring Manager (HM) to define core business outcomes, technical stack requirements, and key performance indicators (KPIs) for the first 90 days.
• 1.4 Coordinate with the Total Rewards Specialist to benchmark the compensation band against current regional labor market data.

Phase 2: Template Drafting and Structural Composition

• 2.1 Initialize a blank document utilizing the official Template Registry Job Description Markdown schema (TR-JD-SCHEMA-v2).
• 2.2 Populate the Header Block: Job Title, Department, Level (IC1-IC6 / M1-M5), Employment Type, and Reporting Line.
• 2.3 Draft the Mission Statement (max 3 sentences): Summarize the macro objective of the role and its direct impact on organizational goals.
• 2.4 Enumerate Key Responsibilities: List 5 to 7 bullet points formatted in active voice (e.g., Design, build, and maintain...), ordered by descending percentage of time allocation.
• 2.5 Define Required Qualifications (Hard Criteria): Establish non-negotiable educational, technical, or experiential baselines. Avoid arbitrary years-of-experience inflation.
• 2.6 Define Preferred Qualifications (Soft Criteria): List secondary competencies that serve as tie-breakers during candidate screening.
• 2.7 Insert the Tech Stack/Tooling Inventory: Detail exact software, hardware, methodologies (e.g., Agile, ITIL), or regulatory frameworks utilized daily.
• 2.8 Append the mandatory institutional boilerplate: Equal Opportunity Employer (EOE) statement, accommodation notices, and remote/hybrid work policies.

Phase 3: Compliance, Equity, and Quality Audit

• 3.1 Execute automated linguistic analysis to scan for gender-coded, ageist, or exclusionary terminology using the internal DEI linting tool.
• 3.2 Verify pay transparency compliance: Ensure geographical salary bands and equity/benefit summaries are explicitly integrated where legally mandated.
• 3.3 Submit the draft to the Total Rewards Specialist for validation of leveling and compensation band accuracy.
• 3.4 Route the finalized draft through the Chief Architect review gate if the role falls under Engineering or Systems Architecture.

Phase 4: ATS Integration and Deployment

• 4.1 Export the validated markdown template into the Greenhouse ATS ingestion wrapper.
• 4.2 Configure candidate scorecard parameters, interview stage routing, and automated screening kill-questions within Greenhouse.
• 4.3 Publish the active job posting to internal career boards, LinkedIn, and targeted external aggregators.
• 4.4 Archive the master template version within the Template Registry repository for future auditing.

---

5. Quality Assurance & Pro-Tips

Best Practices

• Focus on Outcomes, Not Tasks: Frame responsibilities around the value generated rather than the manual steps executed. A strong bullet point answers: "What problem does this person solve?"
• Level Calibration: Ensure the gap between an IC3 (Mid-Level) and IC4 (Senior) template clearly delineates autonomy, architectural scope, and mentorship expectations.

Common Pitfalls to Avoid

• Credential Inflation: Do not require a Master's degree or 10+ years of experience for roles that can be successfully executed with a Bachelor's or equivalent practical experience. This creates unnecessary filtering bias.
• The "Superperson" Fallacy: Avoid listing contradictory skill sets (e.g., deep low-level kernel engineering combined with full-stack UI design and heavy enterprise sales). Split unrealistic roles into distinct headcount requests.

Metric Thresholds

• Time-to-Fill (TTF): Target < 45 days from ATS publication to offer acceptance.
• Candidate Quality Ratio: Ensure at least 15% of inbound applicants meet baseline hard qualifications, indicating clear and precise template definitions.

---

6. Frequently Asked Questions

Q1: What is the protocol if a Hiring Manager insists on including non-standard, restrictive requirements that limit candidate flow?
A: The People Operations (HRBP) and Talent Acquisition lead must facilitate a calibration session. If the requirement is non-essential, it must be shifted from "Required Qualifications" to "Preferred Qualifications" to prevent narrowing the diversity pipeline prematurely.

Q2: How frequently must legacy job description templates be audited for compliance and market relevance?
A: All active templates must undergo a comprehensive audit annually, or immediately upon regulatory shifts in pay transparency laws or significant internal architectural pivots within the department.