Job Description Example Team Leader

Standard Operating Procedure: Engineering Team Leader Job Description Authoring & Lifecycle Management

1. Document Control Block

• Document ID: SOP-TR-ENG-042
• Effective Date: October 24, 2023
• Version: 2.1.0
• Review Cadence: Annual / Post-Organizational Restructuring
• Author: Julian Vance, Chief Architect, Template Registry
• Approver: VP of Global Engineering & People Operations

---

2. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the institutionalized protocol for authoring, reviewing, and operationalizing the "Engineering Team Leader" job description within Template Registry. The purpose is to eliminate role ambiguity, align technical talent acquisition with our distributed systems architecture requirements, and maintain strict compliance with global labor standards. Adherence to this SOP ensures that every Engineering Team Leader recruited possesses exact operational competencies, leadership paradigms, and technical proficiencies required to scale our microservices infrastructure.

---

3. Scope & Prerequisites

• Scope: Applies to all Engineering Team Leader requisitions globally across Platform, Infrastructure, and Core Product engineering divisions at Template Registry.
• Required Tools & Software:
  • Workday HCM (Requisition Management)
  • Greenhouse ATS (Applicant Tracking System)
  • GitHub Enterprise (Template Version Control)
  • Confluence (Institutional Documentation)
• Prerequisites: Approved headcount budget, completed organizational design review, and signed off architecture roadmap for the target fiscal period.

---

4. Roles & Responsibilities (RACI Matrix)

---

5. Step-by-Step Procedure

Phase 1: Requisition Scoping & Core Competency Definition

• 1.1 Extract baseline architectural requirements from the current engineering roadmap in Confluence.
• 1.2 Define the technical stack boundaries (e.g., Go, Kubernetes, Kafka, Terraform) specific to the target team.
• 1.3 Establish the operational split: 60% hands-on systems architecture/coding, 40% technical leadership, mentorship, and sprint delivery.

Phase 2: Template Assembly & Markdown Customization

• 2.1 Access the master Engineering Team Leader template repository in GitHub Enterprise (template-registry/hr-job-descriptions).
• 2.2 Branch the master template into a feature branch: git checkout -b feature/etl-jd-[division-code].
• 2.3 Populate the Position Overview section detailing mission-critical objectives for the first 90 days.
• 2.4 Enumerate the Key Responsibilities utilizing clear, metric-driven action verbs (e.g., Architect, Scale, Debug, Mentor).
• 2.5 Specify the Required Qualifications (minimum 5+ years systems engineering, 2+ years technical leadership) and Preferred Qualifications.

Phase 3: Compliance & Stakeholder Review

• 3.1 Execute the automated linter for inclusive language and bias reduction (make lint-jd).
• 3.2 Submit a pull request (PR) for review by the HR Business Partner and Chief Architect.
• 3.3 Incorporate architectural feedback and obtain formal PR sign-off.

Phase 4: ATS Integration & Publishing

• 4.1 Sync the finalized Markdown document to Greenhouse ATS via the automated API sync pipeline.
• 4.2 Verify compensation banding alignment with current market data in Workday HCM.
• 4.3 Publish requisition and notify the Talent Acquisition souring squad to initiate candidate intake.

---

6. Quality Assurance & Pro-Tips

Best Practices

• Quantify Impact: Avoid vague terms like "good communicator." Specify "Drive cross-functional technical alignment across 3+ distributed microservices squads."
• Clarity on Hands-On Expectations: Clearly define the percentage of coding expected to prevent misalignment with pure people managers.

Common Pitfalls to Avoid

• Tech Stack Bloat: Listing every known technology instead of core foundational dependencies results in flooded pipelines of unqualified generalists.
• Outdated Compensation: Failing to verify regional pay transparency compliance leads to regulatory delays and candidate drop-off.

Metric Thresholds

• Time-to-Fill (TTF): Target $\le 45$ calendar days from requisition approval to offer acceptance.
• Pipeline Conversion Rate: Minimum 15% pass-through from recruiter screen to technical interview stage.

---

7. Frequently Asked Questions (FAQ)

Q1: What should I do if the required technical stack changes mid-recruitment cycle?

A1: Do not edit an active requisition with live candidates in flight. Close the existing requisition in Workday/Greenhouse, update the master Markdown template in GitHub, and open a revision-controlled new requisition to ensure all candidates are evaluated against identical criteria.

Q2: Is the 60/40 coding-to-leadership split mandatory for all Engineering Team Leaders?

A2: It is the standard baseline for core infrastructure and platform teams. However, for specialized squads (e.g., Security Architecture), the ratio may be adjusted to 50/50 with explicit sign-off from the Engineering VP.