Job Description Sample in WORD

STANDARD OPERATING PROCEDURE: Enterprise Job Description Generation & Configuration

---

1. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the institutional engineering standard for drafting, formatting, and releasing standardized Job Description (JD) artifacts in Microsoft Word (.docx) format across Template Registry infrastructure.

The objective is to eliminate structural variance, enforce compliance with labor standards and compensation bands, and produce machine-readable, human-accessible documentation that interfaces seamlessly with our Applicant Tracking System (ATS) and Human Capital Management (HCM) APIs.

---

2. Scope & Prerequisites

2.1 Scope

This protocol applies to all People Operations personnel, Engineering Managers, and Technical Leads tasked with authoring role definitions for internal promotions, external recruitment, and organizational restructuring within Template Registry.

2.2 Prerequisites & Environment

• Software: Microsoft Word (Office 365 Enterprise, v2309+) or LibreOffice Writer (v7.5+ for strict OOXML compliance).
• Templates: Approved Template Registry Word Template (TR-JD-Master-v3.dotx).
• Access Control: Read/Write access to the HR Shared Repository (//infra.templateregistry.internal/hr/templates).
• Reference Data:
  • Approved Compensation & Leveling Matrix (TR-COMP-2023-Q4).
  • Departmental RACI framework.

---

3. Roles & Responsibilities (RACI Matrix)

---

4. Step-by-Step Procedure

Phase 1: Environment Setup & Template Initialization

• 1.1 Navigate to the secure HR shared repository and fetch the latest master template (TR-JD-Master-v3.dotx).
• 1.2 Open the template locally and save immediately using the mandatory naming convention: JD_[Department]_[RoleTitle]_[Level]_[YYYYMMDD].docx (e.g., JD_Engineering_SystemsEngineer_L5_20231024.docx).
• 1.3 Enable the Navigation Pane (View > Navigation Pane) to monitor structural heading hierarchy.
• 1.4 Verify that document properties (Title, Author, Company) are metadata-scrubbed to reflect Template Registry standards.

Phase 2: Metadata & Header Configuration

• 2.1 Complete the Header Metadata Block matching the compensation grade and department.
• 2.2 Define the Job Title, Level (e.g., L3-L7), Department, Reporting Line, and FLSA Status (Exempt/Non-Exempt).
• 2.3 Establish the Salary Band Identifier referencing the current fiscal year matrix.

Phase 3: Core Content Assembly (Functional Sections)

• 3.1 Role Summary: Draft a 3-4 sentence clinical overview detailing the primary mission of the role and its organizational impact.
• 3.2 Key Responsibilities: List 5 to 7 core operational duties using active-voice verbs (e.g., Architect, Deploy, Validate, Enforce). Ensure no duty falls below a 10% weight allocation.
• 3.3 Required Qualifications (Hard Gates): Specify mandatory educational requirements, years of experience, and foundational technical stacks (e.g., Kubernetes, Go, Terraform).
• 3.4 Preferred Qualifications: Outline secondary competencies that accelerate time-to-productivity but do not disqualify applicants.

Phase 4: Styling, Typography, and OOXML Hygiene

• 4.1 Apply the Heading 1 style to primary sections (Summary, Responsibilities, Qualifications) to maintain strict document outline semantics.
• 4.2 Enforce typography standards: Body Text set to Calibri, 11pt, 1.15 line spacing, 6pt space-after. No manual double-returns.
• 4.3 Format all lists using native Word bullet properties (do not use manual dashes or symbols) to ensure clean API parsing.
• 4.4 Remove any embedded styling or foreign formatting pasted from external web browsers by using Paste Special > Unformatted Text.

Phase 5: Quality Assurance & Finalization

• 5.1 Execute the internal Word Accessibility Checker (Review > Check Accessibility) and resolve all flagged contrast or table header issues.
• 5.2 Perform a manual pass against the Pro-Tips threshold checklist (Section 5).
• 5.3 Lock the document layout by restricting editing permissions to "Filling in forms" if distributing unprotected drafts, or export a static .pdf for archival alongside the master .docx.

---

5. Quality Assurance & Pro-Tips

Best Practices

• Atomic Bullet Points: Keep responsibility items under 25 words. Combine action, mechanism, and measurable outcome (e.g., "Architected CI/CD pipelines using GitLab CI, reducing deployment latency by 42%.").
• Gender-Neutral Language: Run text through an inclusion analyzer to ensure equitable terminology and eliminate systemic bias in hard requirements.

Common Pitfalls

• Orphan Headings: Never allow a section header to sit at the bottom of a page without at least two lines of subsequent body text. Use hard page breaks (Ctrl + Enter) to manage layout flow.
• Inflated Requirements: Avoid laundry lists of disparate technologies. If a skill is not utilized within the first 90 days, classify it as "Preferred" rather than "Required."

Metric Thresholds

• Length Constraint: The entire document must not exceed 2 pages (approx. 600–850 words).
• Parse Success Rate: ATS parsing compatibility must register $\ge 98%$ on structural text-extraction tests.

---

6. Frequently Asked Questions (FAQ)

Q: Can I use custom typography or branding colors within the Word document?
A: No. All documents must strictly adhere to the Template Registry corporate palette (Deep Navy #0A192F for primary headers, Slate Gray #4A5568 for body copy) and approved font pairings (Calibri/Calibri Light). Deviations will be rejected during HR compliance review.

Q: How should I handle updates to an existing job description for an active requisition?
A: Do not overwrite a circulated .docx in place. Increment the minor version number (e.g., from v3.2.0 to v3.3.0), document the change in the internal change log at the end of the document, and notify the assigned Talent Acquisition partner immediately.