QA Sales Senior Analyst

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections: - About the role (intro paragraph) - Responsibilities (list of duties) - Basic Qualifications (list) - Preferred Qualifications (list) - Location/Schedule info (full-time in office, Atlanta, GA) - Pay information (hourly salary ranges by state) - Benefits (mentioned: medical, dental, vision, life, long-term disability, 401(k), bonus, paid holidays, PTO) - Then there's a lot of boilerplate: accommodation, EEO, other employment statements, California notifications, recruiting statement - these should be removed. Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for lists - Use

  for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include section ONLY when real, specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no /, no markdown code fences Let me structure: 1. About the role: The first paragraph "Within Operations, we are growing our Digital Inside Sales (DIS) team. Our groundbreaking approach to sales brings clients the right combination of trusted technical sellers and innovative technology, powered by data and insights." ->

  2. Responsibilities: The bullet points under "Key responsibilities:" ->

  • each 3. Basic Qualifications: "Minimum of 2 years in Quality assurance, Data Analytics or Reporting" -> this is a single item, but it's a list. Could be
    • or just

      . Since it's a qualification list, I'll use

      • . 4. Preferred Qualifications: List of items ->
        • 5. Schedule/Location: "This role is a full-time in office position going into our Atlanta, GA office." -> This could be a Schedule section or Location. The rules mention Schedule as a heading. I'll create a Schedule section with

          for the description. 6. Pay: The hourly salary ranges by state. This is specific compensation data. Should include as Pay section with

          • for each state range? Or a table? But rules say use
            • for lists. Could do a list of states with ranges. However, it's a lot of data. Might be better as a
              with each state as a list item. But the rule says "use
              • for any list of duties/requirements/benefits". Pay is not duties/requirements/benefits, but it's a list. I think it's okay to use
                • for pay ranges. Alternatively, could be a

                  with the ranges, but that's messy. I'll use

                  • for each state. 7. Benefits: "Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off." -> This is a list of benefits. Use
                    • for each benefit. Now, the boilerplate after that should be removed: Requesting an Accommodation, Equal Employment Opportunity Statement, Other Employment Statements, California notifications, Recruiting and Hiring Statement. Also note: "We anticipate this job posting will be posted until 10/9/2026." This is metadata, could be folded into a short

                      or dropped. I'll drop it as it's not substantive. Now, headings: The rules say use

                      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I need to map my sections to these standard headings. - About the role ->

                      About the role

                      - Responsibilities ->

                      Responsibilities

                      - Basic Qualifications -> could be

                      Requirements

                      or

                      Qualifications

                      . The rules mention both "Requirements" and "Qualifications". Since there are Basic and Preferred, I could combine under "Qualifications" with two sublists? But the rules say use

                      for section headings. I'll do

                      Qualifications

                      and include both basic and preferred as separate lists? Or separate headings? The rules say "Prefer a few substantive sections over many thin ones." So maybe combine under one Qualifications heading with two subsections? But we can't use subheadings (only h3). Could do two separate h3: "Basic Qualifications" and "Preferred Qualifications". However, the example headings include "Requirements" and "Qualifications". I think "Requirements" for basic, "Qualifications" for preferred? But the posting says "Basic Qualifications" and "Preferred Qualifications". I'll use

                      Basic Qualifications

                      and

                      Preferred Qualifications

                      as they are specific. But the rules say "use

                      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those. I'll stick to the standard ones where possible. For qualifications, I'll use

                      Qualifications

                      and then have two lists: one for basic, one for preferred, maybe with a

                      label? But the rule says use

                      • for any list. Could do:

                        Qualifications

                        Basic Qualifications:

                        • Minimum of 2 years in Quality assurance, Data Analytics or Reporting

                        Preferred Qualifications:

                        • Bachelor’s Degree
                        ... etc. But that uses

                        for labels. That's okay. Alternatively, separate headings:

                        Basic Qualifications

                        and

                        Preferred Qualifications

                        . I think that's fine. Similarly, Schedule:

                        Schedule

                        with

                        Full-time, in-office position in Atlanta, GA.

                        Pay:

                        Pay

                        with
                        of state ranges. Benefits:

                        Benefits

                        with
                        of benefits. Now, ensure no filler text. The pay ranges are specific. Benefits are specific. Now, write the HTML fragment. Let me draft:

                        About the role

                        Within Operations, we are growing our Digital Inside Sales (DIS) team. Our groundbreaking approach to sales brings clients the right combination of trusted technical sellers and innovative technology, powered by data and insights.

                        Responsibilities

                        • Execute within the quality assurance program for the inside sales operation, ensuring adherence to defined sales quality standards, behaviors, and compliance requirements.
                        • Design, maintain, and continuously improve QA scorecards and evaluation frameworks aligned to the sales motion, client expectations, and business objectives.
                        • Conduct and oversee call monitoring, deal reviews, and sales interaction evaluations across sellers and teams to assess quality, effectiveness, and consistency.
                        • Lead QA calibrations with Sales Managers, Service Delivery Leads, and clients to ensure scoring consistency, alignment, and credibility of results.
                        • Translate QA findings into actionable insights, trends, and recommendations that drive measurable improvements in conversion, customer experience, and sales effectiveness.
                        • Partner with Sales Leadership and Learning & Development to deliver targeted coaching inputs, training recommendations, and remediation plans based on quality gaps.
                        • Track, analyze, and report quality performance metrics, including pass rates, defect trends, root cause analysis, and improvement outcomes.
                        • Ensure compliance with contractual, regulatory, and internal sales standards, escalating risks and quality issues proactively.
                        • Support new hire onboarding and ramp by validating quality readiness and providing early-stage feedback to sales leaders and trainers.
                        • Continuously refine QA processes, tooling, and governance to scale quality standards as the sales program evolves.

                        Basic Qualifications

                        • Minimum of 2 years in Quality assurance, Data Analytics or Reporting

                        Preferred Qualifications

                        • Bachelor’s Degree
                        • Inside Sales Experience
                        • Experience with Pivot Tables and PowerPoint
                        • Proficiency in Microsoft Excel, advanced functions preferred
                        • Prior experience using call monitoring/ auditing
                        • Excellent written and verbal communication skills
                        • Experience with corporate policies and/or community standard
                        • Strong attention to detail, both written and verbal

                        Schedule

                        Full-time, in-office position in Atlanta, GA.

                        Pay

                        • California: $26.39 to $72.31 per hour
                        • Colorado: $26.39 to $62.45 per hour
                        • Connecticut: $26.39 to $62.45 per hour
                        • District of Columbia: $28.08 to $66.49 per hour
                        • Illinois: $24.42 to $62.45 per hour
                        • Maine: $22.45 to $53.22 per hour
                        • Maryland: $26.39 to $62.45 per hour
                        • Massachusetts: $26.39 to $66.49 per hour
                        • Minnesota: $26.39 to $62.45 per hour
                        • New York: $24.42 to $72.31 per hour
                        • New Jersey: $28.08 to $72.31 per hour
                        • Ohio: $24.42 to $57.84 per hour
                        • Virginia: $24.42 to $66.49 per hour
                        • Washington: $28.08 to $66.49 per hour

                        Benefits

                        • Medical, dental, and vision coverage
                        • Life and long-term disability coverage
                        • 401(k) plan
                        • Bonus opportunities
                        • Paid holidays
                        • Paid time off
                        That seems comprehensive. I removed all boilerplate. The pay section includes all states listed. The benefits list breaks down the mentioned benefits. Check rules: "Do NOT repeat the job title as a heading" - I didn't. "Do NOT put Job ID / requisition numbers as headings" - none. "Preserve ALL substantive information" - yes. "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions" - done. "Include a section ONLY when the posting has real, specific content for it" - all sections have content. "Never emit a heading followed by filler/placeholder text" - no filler. "Never