Job Description Example for Quality Assurance

SOP: Development of Institutional-Grade Quality Assurance Job Descriptions

Document ID: SOP-HR-QA-001
Effective Date: 2023-10-27
Version: 1.0.0
Review Cadence: Annual

1. Executive Summary & Purpose

This procedure defines the rigorous methodology for authoring Quality Assurance (QA) job descriptions at Template Registry. The objective is to standardize the recruitment of high-caliber engineering talent capable of maintaining our zero-defect architectural standards. Adherence to this SOP ensures alignment between role expectations, technical competency requirements, and organizational performance metrics.

2. Scope & Prerequisites

• Scope: Applies to all QA/QE roles (Manual, Automation, SDET, and Lead).
• Required Tools: ATS (Greenhouse/Lever), Role Taxonomy Matrix, Technical Competency Rubric (TCR).
• Prerequisites: Hiring Manager must have finalized the Architectural Dependency Map and Projected Velocity Targets for the team before drafting.

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase I: Defining Technical Rigor

• Map role to the current stack (e.g., Selenium, Playwright, Python/Go).
• Define the split between "Black Box" testing and "White Box/Code Review" involvement.
• Specify CI/CD integration requirements (Jenkins, GitHub Actions, GitLab CI).

Phase II: Drafting Core Responsibilities

• Technical Scope: Explicitly state the percentage of time spent on test automation vs. manual exploratory testing.
• Infrastructure Ownership: Require experience in maintaining test environments or containerized ephemeral environments (Docker/K8s).
• Cross-Functional Collaboration: Define interaction points with DevOps and Product Management.

Phase III: Qualification Criteria (The "Bar")

• Establish a minimum threshold for years of experience vs. demonstrated project output.
• Define "Must-Haves" vs. "Nice-to-Haves" using the TCR.
• Include a mandatory "Portfolio/Code Sample" review requirement.

Phase IV: Final Audit

• Verify inclusion of "Soft Skills" requirements (Root cause analysis, cross-team advocacy, technical documentation).
• Ensure non-discrimination compliance (ADA/EEOC) across all requirements.

5. Quality Assurance & Pro-Tips

• Metric Thresholds: A well-written JD should result in a Resume-to-Interview conversion rate of no less than 15%. If below this, audit the "Must-Have" requirements for scope creep.
• Common Pitfalls: Do not use generic terms like "quality-minded." Be granular: "Experience maintaining 90%+ branch coverage in microservice architectures."
• Pro-Tip: Include a "What you will accomplish in your first 90 days" section. This aligns candidate expectations with immediate architectural priorities.

6. Frequently Asked Questions (FAQ)

Q: Should I include a list of every tool we use in the JD?
A: No. List only the foundational tools required to be effective on Day 1. Excessive tool lists deter elite candidates who understand that technologies are transient; prioritize architectural fundamentals over syntax knowledge.

Q: How do I distinguish between an SDET and a pure QA Tester in the description?
A: The defining variable is "Code Ownership." If the role requires contributing to production-bound test frameworks and CI/CD pipeline optimization, classify as SDET. If the role focuses on requirement validation, edge-case discovery, and test suite execution, classify as QA.

End of Document
Authorized by: Julian Vance, Chief Architect, Template Registry