Job Description Sample for Software Engineer

Standard Operating Procedure: Software Engineering Job Description Authoring, Calibration, and Lifecycle Management

---

1. Document Control Block

---

2. Executive Summary & Purpose

2.1 Statement of Purpose

This Standard Operating Procedure (SOP) defines the mandatory, deterministic workflow for creating, calibrating, publishing, and maintaining Software Engineer Job Descriptions (JDs) across Template Registry.

2.2 Strategic Objective

Adhoc and poorly structured JDs introduce downstream latency in the talent acquisition pipeline, degrade candidate quality, inject non-inclusive bias, and increase technical mismatch during intake screens. Executing this SOP ensures:

• Alignment between technical evaluation criteria and published requirements.
• Strict adherence to global labor compliance, salary transparency laws, and diversity benchmarks.
• A standardized, high-performing pipeline yields qualified applicant conversion rates above 22%.

---

3. Scope & Prerequisites

3.1 Scope Boundaries

• In-Scope: Full-time, contract, and remote/hybrid Software Engineers (Levels L3 through L7: Junior, Mid-Level, Senior, Staff, Principal).
• Out-of-Scope: Non-engineering technical roles (e.g., Technical Program Managers, Site Reliability Engineers, Product Managers), which fall under SOP-TR-OPS-018 through 022.

3.2 Prerequisites & Tooling Access

Before executing this procedure, the operator must possess active access to:

1. Applicant Tracking System (ATS): Greenhouse / Lever (Admin or Hiring Manager permissions).
2. Text Analysis & Equity Tooling: Textio or equivalent augmented writing software (Target Score: $\ge 90/100$).
3. Compensation Benchmark Engine: Radford / Option Impact / Pave real-time band data.
4. Engineering Matrix: Template Registry IC Leveling Matrix (TR-ENG-MATRIX-v4).

---

4. Roles & Responsibilities (RACI Matrix)

Key: R = Responsible for execution; A = Accountable (final decision/sign-off); C = Consulted; I = Informed.

---

5. Step-by-Step Procedure

[Phase 1: Intake & Banding] ──> [Phase 2: Draft Generation] ──> [Phase 3: Audit & Compliance] ──> [Phase 4: Publication]

Phase 1: Role Intake & Level Mapping

• Step 1.1: Verify Headcount Approval. Confirm budget authorization code in ERP/Workday for the target position.
• Step 1.2: Select Job Level & Family. Map requirements strictly against the IC Leveling Matrix (TR-ENG-MATRIX-v4).
  • L3 (Associate): 0–2 years; procedural execution; supervised delivery.
  • L4 (Software Engineer II): 2–5 years; autonomous execution of scoped feature modules.
  • L5 (Senior Software Engineer): 5–8+ years; system design, cross-functional technical leadership, mentorship.
  • L6 (Staff Engineer): 8+ years; architecture domain ownership, multi-team technical strategy.
• Step 1.3: Define Primary Tech Stack & Core Competencies. Select no more than 3 core languages/frameworks and 2 infrastructure/data technologies.

---

Phase 2: Draft Generation using Standard Templates

• Step 2.1: Populate Canonical Header. Ensure standard metadata fields (Title, Location, Work Model, Band) match internal records.
• Step 2.2: Apply Production Job Description Template. Copy, paste, and customize the standardized asset below based on target leveling.

Asset 2.2A: Standardized Job Description Template (L5 Senior Software Engineer)

# Role Title: Senior Software Engineer (L5) - Platform Architecture
**Location:** Distributed (US/Canada Remote) | San Francisco, CA (Hybrid)
**Department:** Engineering / Infrastructure & Core Services
**Employment Type:** Full-Time

## About Template Registry
Template Registry builds high-throughput, low-latency document control and orchestration systems for enterprise systems engineering. Our core infrastructure processes over 2 billion requests daily with 99.999% availability SLAs.

## Role Overview
We are seeking a Senior Software Engineer (L5) to join our Infrastructure & Core Services group. In this role, you will design, scale, and maintain our distributed template execution engine. You will own microservice architecture end-to-end—from system topology design and data layer performance optimization to production deployment and operational observability.

## Key Responsibilities
* **Architecture & System Design:** Design, build, and maintain highly available, low-latency microservices using Go and Rust in a Kubernetes-native environment.
* **Technical Leadership:** Lead technical design reviews (RFCs), enforce architectural patterns, and mentor L3/L4 engineers through code reviews and pair programming.
* **Operational Excellence:** Drive system reliability metrics (p99 latency < 50ms, zero-downtime deployments); participate in an on-call rotation for Tier-1 services.
* **Performance Optimization:** Diagnose data access bottlenecks, tune PostgreSQL/CockroachDB queries, and optimize gRPC execution pipelines.
* **Cross-Functional Collaboration:** Partner directly with Product Management and Security Engineering to deliver compliance-first infrastructure features.

## Required Minimum Qualifications
* **Experience:** 5+ years of professional software engineering experience delivering distributed backend systems at scale.
* **Core Technical Stack:** Advanced proficiency in at least one statically typed language (**Go, Rust, C++, or Java**) and deep experience with relational or distributed databases (e.g., PostgreSQL, CockroachDB).
* **Distributed Systems:** Proven track record of designing asynchronous event-driven architectures (Kafka, RabbitMQ, or NATS).
* **Cloud Infrastructure:** Strong operational knowledge of Docker, Kubernetes, CI/CD pipelines, and AWS/GCP cloud environments.
* **Computer Science Fundamentals:** Bachelor's degree in Computer Science, Software Engineering, or equivalent practical experience in data structures, algorithms, and system design principles.

## Preferred Qualifications
* Experience building infrastructure tooling using WebAssembly (Wasm).
* Contributor to high-impact open-source infrastructure or developer tooling projects.
* Direct experience with eBPF tracing, Telemetry systems (OpenTelemetry, Prometheus, Grafana), and chaos engineering.

## Total Compensation & Benefits
* **Base Salary Range:** $185,000 USD - $230,000 USD per annum (Location adjusted).
* **Equity:** Generous ISO/NSO stock option grants subject to a 4-year vesting schedule (1-year cliff).
* **Benefits:** 100% company-paid medical, dental, and vision coverages; $3,000 annual learning stipend; 401(k) matching up to 5%; unlimited PTO with a mandatory 15-day minimum requirement.

---

Phase 3: Automated Bias, Equity, & Compliance Audit

• Step 3.1: Run Augmented Text Analysis. Ingest the drafted copy into Textio/Joblint.
  • Rule: Eliminate gendered terms ("ninja", "rockstar", "guru", "dominant").
  • Rule: Limit "Required Qualifications" to $\le$ 5 bullet points (reduces demographic drop-off).
  • Metric Threshold: Achieve a Textio Score $\ge 90/100$ and Gender Neutral Balance = Neutral/Female-leaning.
• Step 3.2: Verify Pay Transparency & Multi-Jurisdiction Compliance.
  • Ensure base salary ranges reflect local mandatory reporting guidelines (e.g., CA SB 1162, NY Senate Bill S9427, EU Transparency Directive).
  • Confirm exact remote eligibility states/countries are explicitly cited.
• Step 3.3: Legal Review Routing. Send JDs with non-standard clauses to the Legal/Compliance team via Jira issue submission.

---

Phase 4: ATS Integration & Publishing

• Step 4.1: Construct ATS Posting Object.
  • Populate mandatory Greenhouse/Lever structured attributes:
    • Job Title: Standardized string format: [Domain] Software Engineer [Level] (e.g., Backend Software Engineer - L5).
    • EEOC Classification: 2 - Professionals.
    • Cost Center: Associated Engineering Department Code.
• Step 4.2: Embed Technical Evaluation Matrix. Attach corresponding interview rubrics (System Design, Coding/Pairing, Architecture) to the ATS job setup to align candidate screeners with the JD parameters.
• Step 4.3: Publish Job Post. Trigger automated distribution to target job boards (LinkedIn, Indeed, specialized tech job boards).

---

6. Quality Assurance & Pro-Tips

6.1 Metric Thresholds & SLAs

[Candidate Views] ──(SLA: >12% Click-to-Apply)──> [Applications] ──(SLA: >22% Qualified Screen)──> [Recruiter Screen]

6.2 Common Anti-Patterns & Operational Pitfalls

1. The "Shopping List" Requirement Pitfall: Listing every tool ever deployed in the org (e.g., requiring 5 years of Kubernetes and Terraform and Go and React and Kafka).
   • Mitigation: Limit requirements to fundamental system capabilities and core languages. Focus on engineering foundations over specific utility tools.
2. Arbitrary Experience Thresholds: Requiring "10+ years of Go" for a language that has only gained mainstream adoption recently, or demanding years of experience in frameworks created 2 years ago.
   • Mitigation: Benchmark requirements against real-world tech stack history.
3. Omission of Salary Bands: Omitting pay ranges reduces application volume among elite candidates and risks regulatory penalties in compliant jurisdictions.

---

7. Frequently Asked Questions (FAQs)

FAQ 1: How do we update a live Job Description if our core stack changes mid-search?

Answer: Any material modification to required skill sets or level classifications requires an immediate operational pause in active candidate sourcing.

1. Update the JD source file using Phase 2.2 standards.
2. Re-run Phase 3 compliance checks.
3. Push changes to the ATS.
4. Notify all candidates currently in the pipeline via Recruiter outreach, providing an updated job profile document to ensure total alignment before technical stages.

FAQ 2: Are we allowed to list a specific technology as a mandatory requirement if an equivalent exists?

Answer: No. Avoid single-vendor lock-in within job specifications. For example, instead of requiring "AWS Lambda," specify "Serverless cloud compute paradigms (e.g., AWS Lambda, GCP Cloud Functions, or Azure Functions)." Exception applies only when the position is an explicit domain-expert migration lead (e.g., legacy migration engineer).

FAQ 3: How frequently must legacy, continuously open engineering JDs be re-calibrated?

Answer: Continuously open evergreen positions (e.g., general L4/L5 Software Engineer pools) must undergo a full re-calibration cycle every 180 days via this SOP. Inactive JDs remaining open past 180 days without audit are automatically unpublished by ATS maintenance scripts.