Job Description Example for Sales Representative

Standard Operating Procedure: Sales Representative Role Definition & Acquisition

---

1. Executive Summary & Purpose

This SOP establishes the architectural framework for drafting, validating, and publishing a high-conversion Sales Representative job description. The objective is to standardize candidate acquisition to ensure alignment between organizational growth targets and talent competency.

2. Scope & Prerequisites

• Scope: Applies to all Sales department requisitions managed through the Template Registry ATS.
• Required Tools: ATS (Greenhouse/Lever), Role Competency Matrix (Doc-ID: HR-COMP-09), CRM (Salesforce).
• Prerequisites: Approved headcount budget, finalized compensation band, and identified key performance indicators (KPIs).

3. Roles & Responsibilities (RACI)

---

4. Step-by-Step Procedure

Phase I: Role Parameterization

• Define quota attainment expectations (e.g., $XM ARR/year).
• Determine technical stack proficiency requirements (e.g., Salesforce, Outreach.io, LinkedIn Sales Navigator).
• Codify the "Ideal Candidate Profile" (ICP) based on previous top-performer attributes.

Phase II: Template Construction

• Position Summary: Write 3-4 sentences focusing on market impact, not just duties.
• Core Responsibilities: List 5-7 bullet points centered on revenue-generating activities (prospecting, demo execution, closing).
• Technical Requirements: Specify "Must-Haves" vs "Nice-to-Haves" to filter out noise.
• Success Metrics: Include objective 30/60/90-day onboarding milestones.

Phase III: Review & Deployment

• Audit for inclusive language using internal bias-detection software.
• Execute formal sign-off by Hiring Manager and Finance.
• Push to ATS and distribution channels.

---

5. Quality Assurance & Pro-Tips

Best Practices

• The "Why" Factor: Candidates optimize for equity and commission structure transparency. Disclose OTE (On-Target Earnings) range clearly.
• Action Verbs: Use aggressive, outcome-oriented language (e.g., "Drive," "Penetrate," "Negotiate").

Common Pitfalls

• Bloated Requirements: Listing 15+ requirements increases candidate drop-off. Limit to 8 core competencies.
• Generic Descriptions: Avoid "Must be a self-starter." Replace with "Demonstrated history of sourcing 20+ qualified leads weekly."

Metric Thresholds

• Conversion Goal: Aim for a 15% interview-to-screen ratio. If lower, audit the job description for technical requirement drift.

---

6. Frequently Asked Questions (FAQ)

Q: Should I include the exact commission percentage in the job description?

• A: No. Maintain salary transparency (OTE range) to remain competitive, but keep specific commission structures for the Offer Phase to preserve legal flexibility.

Q: How do we handle candidates who lack industry-specific experience?

• A: If the candidate demonstrates exceptional SDR/BDR velocity in a different sector, pivot the requirements section to favor "Transferable SaaS Skills" over "Domain Expertise."

Q: What if we receive too many unqualified applicants?

• A: Implement a "knock-out" question in the ATS (e.g., "Are you willing to work in a high-velocity, quota-carrying environment?") to reduce top-of-funnel noise.

---

Authorized by: Julian Vance, Chief Architect, Template Registry