Recruiting Specialist

The user wants me to convert this job posting into clean semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: - About the role (introductory paragraph) - Key Responsibilities (with sub-sections: Campus & Stakeholder Partnership, Recruiting Execution, Systems, Data & Compliance, Candidate Experience & Programming) - Basic Qualifications - Preferred Qualifications - Note about hours/travel - Compensation/Pay (with specific salary ranges by location) - Benefits (mentioned) - Schedule (mentioned evening/weekend hours, travel) I need to use

for section headings,

• for lists,

  for prose. Don't repeat job title. Don't include Job ID. Remove boilerplate (EEO, accommodation, etc.). Only include sections with real content. Let me structure: 1. About the role - the first paragraph describes the role. 2. Responsibilities - the Key Responsibilities section with four sub-areas. I'll make each sub-area a list under Responsibilities, or maybe keep as separate lists? The rule says use

  • for any list of duties. The responsibilities are grouped into four categories. I could make each category a sub-heading? But the rule says use

    for section headings like Responsibilities, Requirements, etc. It doesn't say to use h4 for sub-sections. I think I should keep Responsibilities as one section with a list of all duties, but the posting has categorized them. I could either flatten into one list or keep categories as sub-headings using maybe

    ? But the instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't mention sub-headings. I think I should keep the categories as part of the list items, maybe with bold labels? But the rule says use

    • for any list of duties/requirements/benefits. I could make each bullet a duty, and include the category as a prefix. Or I could create separate lists for each category under the same Responsibilities heading. That might be okay: use multiple
      under the same

      . That's acceptable. Similarly for Qualifications: Basic and Preferred. I'll make two lists under Qualifications heading. Note about hours/travel: could be under Schedule section. Compensation: there's a table of salary ranges by location. That's specific pay data. I'll include a Pay section with a list or maybe a table? But the rule says use

      • for lists. I could make a list of locations with ranges. Or a paragraph with the ranges. Since it's structured data, a list might be better. Benefits: mentioned "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." That's a list. Schedule: "This role may require evening and weekend hours, particularly in the Fall recruiting season. Travel to assigned campuses may be up to 50% during peak periods." That's schedule info. Now, I must not include boilerplate: EEO, accommodation, equal opportunity, other employment statements, California notifications, etc. Remove those. Also, the posting says "Compensation at Accenture varies depending on a wide array of factors..." and then gives a table. I'll include the salary ranges for Washington (since role is based in Seattle, WA) but the table includes many states. The role location is Seattle, WA, so the Washington range is $80,200 to $142,400. However, the posting lists ranges for many states. The rule says preserve ALL substantive information. Should I include all states? The role is based in Seattle, WA, but the posting includes ranges for other states maybe because it's a national posting. I think I should include the Washington range specifically, but the posting says "Role Location Annual Salary Range" and lists many. Since the role is based in Seattle, WA, the relevant range is Washington. But the posting includes all. I'll include the Washington range and maybe note that ranges vary by location. But the rule says preserve all substantive information. I'll include a list of all locations and ranges? That might be too much but it's substantive. However, the user might want only relevant info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should include the salary ranges for all locations listed. But that's a lot. I'll create a list with each location and range. But the HTML fragment should be clean. I'll make a Pay section with a list of locations and ranges. Now, let's write the HTML. I'll start with

        About the role

        then a paragraph. Then

        Responsibilities

        then four sub-lists? I'll do each category as a sub-heading using

        ? The rule only mentions

        for section headings. It doesn't forbid

        . But to be safe, I'll keep as

        for main sections only. I'll make the categories as bold text within list items? Or separate lists with a heading-like label? I think I can use for category labels within a single list. But the categories have multiple bullets each. Better to have separate

        for each category, each preceded by a

        Category

        . That's acceptable. Alternatively, I could make each category a list item with a nested list. That's semantic. Let's do:

        Responsibilities

        • Campus & Stakeholder Partnership
          • Serve as campus relationship manager for assigned universities and point of contact for metro office recruiting
          • Partner with on-campus teams of business stakeholders to support event execution, candidate relationship-building, and brand presence
        • Recruiting Execution
          • Partner with business stakeholders to develop and execute recruiting strategies for business demand
          • Serve as responsible recruiter for the end-to-end candidate journey: communicate status, answer questions, extend offers, schedule start dates, and coordinate follow-up
          • Plan and execute sourcing events and interview days
          • Build and maintain a robust early talent identification pipeline from target universities; monitor demand and metrics and adjust pipelines accordingly
          • Review resumes and assess candidates against target profiles; provide structured feedback for offer review
        • Systems, Data & Compliance
          • Manage candidate management systems (e.g., Workday, HiredScore) to ensure tracking, reporting, and data integrity are current and accurate
          • Understand and execute the complete candidate Workday flow from application through onboarding, including offer letter creation and compliance steps
          • Review assessment documentation to ensure alignment with EEO guidelines
          • Reconcile and manage recruiting budgets for assigned campuses
        • Candidate Experience & Programming
          • Plan and execute summer analyst programming and candidate engagement events
          • Coach candidates on available opportunities and serve as a career advisor for prospects from assigned universities
          • Participate in flex assignments such as experience hire recruiting and summer internship programming
        That's good. Qualifications: Basic and Preferred.

        Qualifications

        Basic Qualifications

        ? But rule says only

        for section headings. I'll use

        for Qualifications and then maybe a paragraph "Basic Qualifications" then list. Or I can make two separate sections: Basic Qualifications and Preferred Qualifications as separate

        ? The rule says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It lists Qualifications as one. But there are basic and preferred. I'll keep one Qualifications section with two sub-lists labeled. I'll do:

        Qualifications

        Basic Qualifications

        • Minimum of 3 years of recruiting or HR experience

        Preferred Qualifications

        • Bachelor's degree or equivalent experience
        • Proficient in MS Office Suite (Excel, PowerPoint, Teams, Outlook)
        • Experience with CTS/ATS with sourcing, tracking and managing candidates
        • Entry level recruiting or advanced degree / MBA recruiting experience
        • Prior stakeholder management experience
        • Experience managing projects of varying sizes and scope
        • Experience implementing end-to-end recruiting strategies including employer branding and interview process optimization
        • Experience leveraged AI-powered tools (e.g. HiredScore, Paradox or similar) to enhance sourcing and pipeline management; comfort experimenting with emerging AI capabilities to improve recruiting efficiency and candidate experience
        • Experience contributing to the creation and implementation of high-quality, high-volume recruiting plans
        • Highly organized and detail-oriented with strong time-management skills
        • Strong written and verbal communication skills; ability to present visually and orally
        • Creativity and critical thinking; ability to make independent decisions and escalate appropriately
        • Ability to negotiate with and influence diverse stakeholders across the organization
        • Passion for campus recruiting and developing early-career talent
        • Demonstrated leadership and teamwork in a professional setting (military or civilian)
        • Ability and willingness to work in the office and travel as required
        Note about hours/travel: I'll put under Schedule section.

        Schedule

        • May require evening and weekend hours, particularly during the Fall recruiting season
        • Travel to assigned campuses up to 50% during peak periods
        Pay section: include the salary ranges. Since the role is based in Seattle, WA, but the posting lists many states. I'll include all for completeness.

        Pay

        Annual salary ranges by location:

        • California: $70,350 to $154,800
        • Colorado: $63,800 to $133,700
        • Connecticut: $63,800 to $133,700
        • District of Columbia: $68,000 to $142,400
        • Illinois: $59,100 to $133,700
        • Maine: $54,400 to $113,900
        • Maryland: $63,800 to $133,700
        • Massachusetts: $63,800 to $142,400
        • Minnesota: $63,800 to $133,700
        • New York: $66,300 to $154,800