Standard Operating Procedure: Role Description Engineering

Standard Operating Procedure: Role Description Engineering (RDE)

---

1. Executive Summary & Purpose

This procedure defines the institutional standard for drafting Role Descriptions (RD) at Template Registry. The objective is to standardize cross-departmental hiring, eliminate ambiguity in performance expectations, and ensure alignment with the overarching organizational competency framework.

2. Scope & Prerequisites

• Scope: Applies to all permanent, contract, and fractional roles within the organization.
• Prerequisites: Access to the Template Registry Unified Competency Matrix (UCM) and the organization's HRIS (Workday/Greenhouse).
• Tools: Standardized RD Markdown Template, Organizational Org Chart, Compensation Benchmarking Data.

3. Roles & Responsibilities (RACI)

---

4. Step-by-Step Procedure

Phase I: Architectural Definition

• Define the "North Star" metric for the role (How does success look in 90 days?).
• Determine the seniority level (I-V) using the UCM criteria.
• Identify the core technical stack and soft skill requirements.

Phase II: Drafting the Artifact

• Role Overview: Draft a 3-sentence summary emphasizing the "Why" behind the hire.
• Impact Pillars: List 4-6 key result-oriented responsibilities, not just tasks.
• Minimum Qualifications: Distinguish strictly between "Required" and "Preferred" to reduce demographic bias.
• Growth Path: Define the next logical horizontal or vertical move within the registry.

Phase III: Review & Validation

• Bias Audit: Run the draft through the automated inclusivity linter.
• Calibration: Validate compensation parity against current internal role benchmarks.
• Final Sign-off: Secure physical or digital signature from the relevant Department Head.

---

5. Quality Assurance & Pro-Tips

Best Practices

• Outcome Over Input: Focus on what the candidate will achieve, not what they will do (e.g., "Increase conversion by 10%" vs. "Manage the landing page").
• Specificity: Use quantitative verbs (Architect, Execute, Analyze) rather than passive ones (Assist, Help, Support).

Common Pitfalls

• Kitchen-Sink Syndrome: Including excessive "nice-to-haves" that discourage qualified candidates from applying.
• Jargon Saturation: Over-reliance on internal acronyms reduces the applicant pool quality.

Metric Thresholds

• Target Diversity Ratio: 40%+ representation in the applicant pipeline.
• Time-to-Fill: Goal of < 45 days from posting to offer acceptance.

---

6. Frequently Asked Questions (FAQ)

Q: Can we deviate from the template structure for specialized engineering roles? A: No. The structure is fixed to ensure systematic data ingestion into our internal applicant tracking system (ATS). You may expand the "Technical Requirements" section, but the metadata headers are immutable.

Q: How often should a role description be audited? A: Every 6 months or whenever the role's primary North Star metric shifts. An outdated description is a liability during performance calibration cycles.

---

Authorized by: Julian Vance Chief Architect, Template Registry