Field Service Representative

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: 1. About the role / Summary - there's a "Summary" section 2. Responsibilities - "ESSENTIAL DUTIES AND RESPONSIBILITIES" 3. Requirements/Qualifications - "Qualification Requirements" with subsections: Education/Experience, Other Skills and Abilities, Technical skills, Language Skills, Reasoning Ability, Certificates/Licenses/Registrations 4. Physical Demands 5. Work Environment I should use

for section headings,

• for lists,

  for prose. I need to NOT repeat the job title (not given anyway), not include Job ID/requisition numbers (none present). Remove boilerplate - there's no cookie/navigation/legal/EEO/scam-warning text here. No application instructions to remove. Preserve ALL substantive information. Don't invent or summarize. Include section ONLY when real specific content exists. No filler. Let me structure:

  About the role

  Summary text...

  Responsibilities

  • ...

  Requirements

  or

  Qualifications

  - the heading says "Qualification Requirements". I'll use "Qualifications" as heading. Under Qualifications, there are subsections. Should I make them subheadings? The rules say use

  for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It doesn't mention subheadings. But the content has clear subsections: Education/Experience, Other Skills and Abilities, Technical skills, Language Skills, Reasoning Ability, Certificates/Licenses/Registrations. I could make them

  but the instruction only mentions

  . However, the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other heading levels, but to keep it simple, maybe I should keep them as part of the Qualifications section with

  or

  labels. But they are distinct categories. I think using

  would be appropriate for subsections, but the instruction doesn't specify. However, the example only shows

  . To be safe, I'll keep them as

  ? But that would make many

  headings. The instruction says "Prefer a few substantive sections over many thin ones." So maybe I should combine them under Qualifications with sub-lists. But the content is quite detailed. Let me see: The posting has "Qualification Requirements" then "EDUCATION And/or EXPERIENCE", "OTHER SKILLS And ABILITIES", "Technical skills: Essentials", "Language Skills", "Reasoning Ability", "Certificates, Licenses, Registrations". These are all part of qualifications. I could make them separate

  sections: Education & Experience, Skills & Abilities, Technical Skills, Language Skills, Reasoning Ability, Certificates & Licenses. But that might be too many thin sections. However, each has substantial content. The instruction says "include a section ONLY when the posting has real, specific content for it". Each of these has specific content. But they are subsections of qualifications. I think it's okay to have multiple

  sections for each major category. The example list includes "Skills" as a possible heading. So I could have "Education & Experience", "Skills & Abilities", "Technical Skills", "Language Skills", "Reasoning Ability", "Certificates & Licenses". That's six sections. Might be okay. Alternatively, I could have one "Qualifications" section with subheadings using

  . But the instruction doesn't mention

  . However, HTML allows it. The instruction says "use

  for section headings". It doesn't say you cannot use other headings. But to follow the spirit, maybe use

  for each major section. The posting has clear major sections: Summary, Essential Duties, Qualification Requirements (with subsections), Physical Demands, Work Environment. I'll treat each top-level as

  . For the subsections under Qualification Requirements, I'll make them

  as well? That would be many. Let me count: Education/Experience, Other Skills/Abilities, Technical Skills, Language Skills, Reasoning Ability, Certificates/Licenses. That's 6. Plus Summary, Responsibilities, Physical Demands, Work Environment = 10 sections. That's a lot but each has content. The instruction: "Prefer a few substantive sections over many thin ones." But these are not thin; each has multiple bullet points. However, they are all under "Qualification Requirements". Maybe I should keep them as a single "Qualifications" section with internal structure using

  and

  with bold labels? But the instruction says use

  • for any list of duties/requirements/benefits. The subsections are lists. I could do:

    Qualifications

    Education & Experience

    ...

    Skills & Abilities

    ...
    etc. But the instruction doesn't mention

    . However, it's valid HTML. The user didn't forbid it. The system prompt says "use

    for section headings". It doesn't say "only use

    ". I think using

    for subsections is fine. But to be safe, I'll use

    for all major sections, and for subsections I'll use

    ? The instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It lists "Skills" as a possible heading separate from "Qualifications". So maybe they expect "Skills" as a separate section. In this posting, "OTHER SKILLS And ABILITIES" and "Technical skills" could be "Skills". "Education & Experience" could be "Requirements". "Certificates, Licenses, Registrations" could be "Certifications". "Language Skills" and "Reasoning Ability" could be separate. I'll structure as:

    About the role

    ...

    Responsibilities

    ...

    Requirements

    (for Education/Experience)
    ...

    Skills

    (for Other Skills and Abilities, Technical skills)
    ...

    Language skills

    ...

    Reasoning ability

    ...

    Certifications

    ...

    Physical demands

    ...

    Work environment

    ...

    But "Requirements" and "Qualifications" are similar. The example includes both "Requirements" and "Qualifications". I'll use "Requirements" for education/experience, "Skills" for skills, "Certifications" for licenses. Let me parse the content. First, Summary: "Responsible for all areas of field services repair and product delivery and supplies to customer locations, maintaining and repairing equipment, making sure the overall needs of each customer are met, and representing KASCO LLC. in a professional and experienced manner." That's a paragraph. Essential Duties: list of bullet points. I'll convert each line to
  • . There are many. I'll keep them as separate list items. Qualification Requirements: intro paragraph: "To perform this job successfully, an individual must be able to perform each essential duty satisfactorily. The requirements listed below are representative of the knowledge, skill and/or ability required. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." Then EDUCATION And/or EXPERIENCE: three bullet points? Actually it's lines: "Accredited High School diploma, Business or trade school or GED.", "Excellent mechanical/electrical/electronic aptitude.", "Related technician repair skills." I'll make them list items. OTHER SKILLS And ABILITIES: list of traits: "Ability to sell", "Strong interpersonal skills - Able to create relationships", etc. Each line is a bullet. Technical skills: Essentials: list of technical skills. Language Skills: paragraph. Reasoning Ability: paragraph. Certificates, Licenses, Registrations: "Valid, clear driver's license in the state he/she resides." Physical Demands: paragraph. Work Environment: paragraph. Now, I need to output ONLY the HTML fragment, no /, no markdown code fences. Let me write the HTML. I'll start with

    About the role

    then

    Summary...

    Then

    Responsibilities

    with each duty as
    • . Then

      Requirements

      for education/experience. But the heading "Requirements" might be confused with overall qualifications. The example includes "Requirements" and "Qualifications". I'll use "Requirements" for education/experience. Then

      Skills

      for other skills and technical skills. But there are two distinct lists: "OTHER SKILLS And ABILITIES" and "Technical skills: Essentials". I could combine under Skills with two sub-lists. Or separate. I'll combine under Skills with two
      groups, each preceded by a

      label? But the instruction says use

      • for any list. I can have multiple
        under same heading. Better:

        Skills & abilities

        then

        Core skills

        ... then

        Technical skills

        ... But again

        . I'll just use

        Core skills

        then

        , then

        Technical skills

        then
        . That avoids extra headings. Similarly for Language Skills and Reasoning Ability: they are prose, not lists. I'll make them separate sections with

        Language skills

        ... and

        Reasoning ability

        ... Certifications:

        Certifications

        • Valid, clear driver's license in the state of residence.
        Physical Demands:

        Physical demands

        ... Work Environment:

        Work environment

        ... Now, ensure no boilerplate. The text includes "Reasonable accommodations may be made..." in two places. That's part of the job posting, not boilerplate. Keep it. Also, the first paragraph about KASCO history: "For more than 120 years, KASCO has been the industry leader..." That's company description. Should I include it? The summary is separate. The posting starts with that paragraph, then "Summary". I think the company description is part of "About the role" or maybe a separate "About the company". But the instruction says "About the role" as example. I'll include the company description in the About the role section as a paragraph before the summary. Let me structure:

        About the role

        For more than 120 years, KASCO has been the industry leader in providing quality products, parts, repairs, and service to the meat processing and retail institutional food industries. Our cutting edge products include band saw blades, meat grinder plates and knives, and cutlery. We also offer a vast range of butcher supplies, seasonings