SPECIAL PROGRAMS ELIGIBILITY SPECIALIST - 10132026-81678

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: - Job Information (metadata like dates, salary, location, department) - Qualifications (Education and Experience, Substitution of Experience for Education, Necessary Special Qualifications) - Overview - Responsibilities (multiple bullet points) - Competencies (KSA's) - includes Competencies, Knowledge, Skills, Abilities, Tools & Equipment 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 - fold minor metadata into short

  or drop - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning) - Include section ONLY when posting has real, specific content - 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 Looking at the content: - Job Information: Opening/Closing dates, Salary (monthly/annually), Job Type, City/State, Department, Location details, background check note. This is metadata. I should fold into a short

  or maybe a section? The rules say "fold minor metadata into a short

  or drop it." But salary is substantive. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states salary, so maybe a Pay section? But the rules also say "Prefer a few substantive sections over many thin ones." I think I'll include a "Job Details" or "Position Information" section with a

  for the metadata, but the rules say use

  for section headings like "Pay", "Schedule". However, the posting doesn't have a "Benefits" section. It has salary info. I could create a "Pay" section with the salary details. But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state salary. So I can create a Pay section. But also there's schedule info? It says "Full-Time" and "hybrid work environment". That could be Schedule. But the rules say only if posting actually states them. The posting states "Full-Time" and "hybrid work environment". That's schedule info. But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. However, the rules also say "Prefer a few substantive sections over many thin ones." I'll combine into a "Position Details" section maybe? But the rules specify using

  for section headings like "Pay", "Schedule". I think I'll create a "Position Details" section with a

  for the metadata, and maybe a "Pay" section for salary. But the salary is part of the metadata. Let's see examples: The user gave a list of example headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So they expect those headings if content exists. The posting has: - Salary (Monthly) $3,667.00 Salary (Annually) $44,004.00 -> Pay - Job Type Full-Time -> Schedule - Hybrid work environment -> Schedule - Location -> maybe not a heading - Department -> maybe not a heading - Opening/Closing dates -> maybe not a heading (application instructions? but they said remove application instructions). The dates are part of job information. Could be folded into a

  . I think I'll create a "Position Details" section with a

  summarizing the metadata, but the rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say "Position Details". But they said "e.g." so other headings are allowed? The rules: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the typical headings. But we can use others if needed. However, they also say "include a section ONLY when the posting has real, specific content for it". So I can create a "Job Details" heading if there's content. But the metadata is not a list of duties/requirements/benefits. It's prose. I'll put it in a

  under a "Position Information" heading? But the rules say "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So maybe I should just fold the metadata into a short

  at the top, not as a section. But the salary is important. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states salary and schedule (full-time, hybrid). So I should create Pay and Schedule sections. But the salary is given as monthly and annually. That's pay. The schedule: full-time, hybrid. That's schedule. I'll create those sections. But also there is "Overview" which describes the role. That could be "About the role". The posting has "Overview" section. I'll use "About the role" as heading. "Qualifications" section with education/experience, substitutions, special qualifications. That's "Qualifications" heading. "Responsibilities" section with many bullet points. That's "Responsibilities" heading. "Competencies (KSA's)" includes Competencies, Knowledge, Skills, Abilities, Tools & Equipment. That could be "Skills" or "Competencies". The rules mention "Skills" as a heading. I'll use "Competencies" as heading, but the rules say "Skills". However, the posting has "Competencies (KSA's)" with subcategories. I'll create a "Competencies" section with sub-lists. Now, I need to output only HTML fragment. Let's structure:

  About the role

  ...overview text...

  Qualifications

  • ...education and experience...
  • ...substitution...
  • ...special qualifications...

  Responsibilities

  • ...each responsibility...

  Competencies

  • ...competencies list...
  Maybe separate Knowledge, Skills, Abilities, Tools & Equipment as sub-lists? But the rules say use
  • for any list. I can make a list of competencies, then maybe subheadings? But only

    for section headings. Could use

    ? Not specified. The rules only mention

    for section headings. Probably keep it flat: one

    with all items, or separate
    for each category. I'll do separate
    for each category with a

    label? But the rules say use

    • for any list of duties/requirements/benefits, and

      for prose. I can use

      for category names and then

      . But that might be okay. Alternatively, I can make a single list with all items grouped. But the posting has distinct categories: Competencies, Knowledge, Skills, Abilities, Tools & Equipment. I'll create a

      Competencies

      then for each category a

      Knowledge

      then
      ... but the rules say use

      for section headings only. Not

      . So maybe just include as list items with category prefixes. But that loses structure. I think it's acceptable to have a

      for category and then

      . The rules don't forbid

      for prose. The category names are prose. So I'll do:

      Competencies

      Competencies

      • Manages Complexity
      ...

      Knowledge

      • Communication and Media
      ...
      etc. But the rules say "use
      • for any list of duties/requirements/benefits, and

        for prose." So that's fine. Now, Pay and Schedule sections:

        Pay

        Monthly: $3,667.00; Annually: $44,004.00

        Schedule

        Full-time; hybrid work environment (combination of work from home and work in office, varies by position, department, and business need).

        But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states them, so okay. Now, the metadata like opening/closing dates, location, department, background check note. Should I include? The rules say "fold minor metadata into a short

        or drop it." I'll drop opening/closing dates (application instructions). Location and department maybe include in a "Position Details" section? But the rules say "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." So I'll fold into a short

        at the top maybe under a "Position Information" heading? But that would be a heading not in the example list. However, 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 "Prefer a few substantive sections over many thin ones." So maybe I'll just include a

        at the beginning with the key details: "Location: Nashville, TN; Department: TennCare; Division of TennCare, Davidson County. This position requires a criminal background check." And not make a heading for it. But the rules say "Output ONLY the HTML fragment". It doesn't say we must have a heading for everything. We can have a

        without a heading. But the structure expects sections. I think it's okay to have a leading

        with metadata. But the user might expect sections only. Let's see the instruction: "You reformat a job posting into clean, well-structured semantic HTML. Rules: use

        for section headings... Use

        • for any list... and

          for prose." It doesn't say we cannot have a

          before any heading. But typical HTML fragment would start with a heading. I'll start with "About the role" heading. I'll include the metadata in the "About the role" section? The overview already describes the hybrid work environment. I can add a sentence about location and department. But the overview is separate. I'll keep the overview as is, and add a

          before the first heading? Might be okay. Better: Create a "Position Details" section with

          Position Details

          and a

          with the metadata. But the rules didn't list that as an example. However, they said "e.g." so it's not exhaustive. I'll do that. But the rules also say "Do NOT repeat the job title as a heading (the page already shows it)". The job title is not given in the input? The input starts with "Job Information State of Tennessee Job Information". That might be the title? Actually, the job title might be "Managed Care Specialist 3" or something? Not explicitly given. The posting mentions "