Barista

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. The posting has: - SECTION ONE: MCR Universal Role Standards (with subsections: Executive Summary, Areas of Excellence, Duties and Expectations with sub-subsections: Happy Guests, Spotless Cleanliness, Product Consistency & Quality, Teamwork) - SECTION TWO: Role Specific Duties and Expectations (with Responsibilities and Requirements) - Our Company (about MCR) - What we offer/What's in it for you? (benefits) Rules: - Use

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

• for lists,

  for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning), duplicated lines, application instructions - Include section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, I need to map the content to appropriate headings. The job title is "Barista at Hilton Miami Blue Lagoon" but we shouldn't repeat it as heading. Possible sections: - About the role (could be the executive summary/role description) - Responsibilities (from Section Two) - Requirements (from Section Two) - Qualifications (maybe same as requirements? But we have specific requirements listed) - Skills (maybe from the universal standards) - Benefits (from "What we offer") - Company (about MCR) But the rules say use headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". We should only include sections that have real content. Let's structure: 1. About the role: Could include the executive summary and role specific description. The posting has "EXECUTIVE SUMMARY" and then "The Barista at Hilton Miami Blue Lagoon will create..." That's a good "About the role" section. 2. Responsibilities: The bullet list under "Responsibilities:" 3. Requirements: The bullet list under "Requirements:" 4. Standards & Expectations: The universal role standards (Happy Guests, Spotless Cleanliness, Product Consistency & Quality, Teamwork) are specific to the company's standards. Could be a section "Standards & Expectations" or "Role Standards". But the rules suggest headings like "Qualifications, Skills". However, these are not exactly qualifications but standards. I think we should include them as they are substantive. Maybe "Universal Role Standards" as a heading? But the rules say use

  for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It doesn't forbid other headings, but says "e.g." So we can use other relevant headings. However, we should prefer the standard ones. But the universal standards are a big part of the posting. I'll create a section "Universal Role Standards" with subsections? But we can only use

  for headings, not nested headings. We could make it a single section with lists. Alternatively, we could incorporate the universal standards into "About the role" or "Qualifications". But they are distinct. I think we should include a section "Standards & Expectations" or "Role Standards". The rules say "include a section ONLY when the posting has real, specific content for it". This posting has a lot of content for universal standards. So I'll include a section "Universal Role Standards" with the four areas as sub-lists. But we must not use headings below h3. We can use

  for each area? The rules say "use

  for section headings". It doesn't say we can't have multiple h3s. We can have multiple h3 sections. So we could have:

  Universal Role Standards

  then maybe

  ? But we shouldn't use h4. The rules only mention h3 for section headings. Probably we should keep it flat: each major section as h3. The universal standards could be one section with the four areas as sub-lists using

  with
  • containing bold or something? But we need to preserve structure. We can use

    for each area? That would be many h3s. The rules say "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we cannot have other h3s. But we should prefer a few substantive sections over many thin ones. The universal standards have four areas, each with multiple bullet points. That's substantive. Could make one section "Universal Role Standards" and then use

    with nested lists? But HTML doesn't allow nested ul inside li without sublists. We can do:

    Universal Role Standards

    Executive summary...

    Happy Guests

    but we shouldn't use h4. The rules don't explicitly forbid h4, but they say "use

    for section headings". Might be okay to use h3 for each area? That would be many sections. Let's see: The posting has "SECTION ONE: MCR Universal Role Standards" with "EXECUTIVE SUMMARY", "AREAS OF EXCELLENCE", "Duties and Expectations" with four subsections. That's a lot. But we can condense. Maybe we can create a section "Universal Role Standards" and then use

    for each area with the area name as a strong element inside li? But that would lose the heading structure. However, the rules don't require preserving heading hierarchy, just to use h3 for section headings. We can treat each area as a section? But they are subsections of Section One. The user might expect the universal standards to be included. Let's look at the example headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". The universal standards could be considered "Qualifications" or "Skills"? Not exactly. They are company-wide standards. I think we should include them as a separate section "Universal Role Standards" with the content as prose and lists. We'll do:

    About the Role

    Executive summary...

    The Barista at Hilton Miami Blue Lagoon will create...

    Universal Role Standards

    Executive summary: Cleanliness and friendliness...

    Happy Guests

    but we can't use h4. We'll use

    for each area? That would be many h3s. The rules say "use

    for section headings". It doesn't say we can't have multiple h3s. But they'd be subsections. Might be okay. However, the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine into one section with lists. Let's think: The universal standards have four areas: Happy Guests, Spotless Cleanliness, Product Consistency & Quality, Teamwork. Each has bullet points. We can present as:

    Universal Role Standards

    The MCR standard is to provide clean, friendly, well-organized and safe hotels for our guests.

    Happy Guests

    but we can't. We'll use Happy Guests and then
    ... But that's not semantic. However, the rules don't forbid using for subheadings. But they said "use

    for section headings". It doesn't say we can't use other tags for subheadings. But to be safe, we can make each area a separate

    section? That would be four additional sections. That might be too many thin sections. But each area has multiple bullet points, so they are substantive. Let's count: Happy Guests has 6 bullet points, Spotless Cleanliness has 3, Product Consistency & Quality has 4, Teamwork has 3. That's decent. But the rules say "include a section ONLY when the posting has real, specific content for it". Each area has specific content. So we could have:

    Happy Guests

    ...

    Spotless Cleanliness

    ...
    etc. But then we lose the grouping "Universal Role Standards". We could have a parent section "Universal Role Standards" with a paragraph, then the four subsections as h3? But that would be nested h3s, which is not typical. Usually you'd have h2 for parent, h3 for children. But we are only allowed to output fragment, no html/body. We can use h3 for all top-level sections. The universal standards could be one section with sub-lists using
    and
    • with bold labels. I think the best is to create a section "Universal Role Standards" and then use
      with each area as a list item containing a nested list. For example:
      • Happy Guests
        • Greet guests happily...
        ...
      ...
      That preserves structure and uses only one h3. That seems acceptable. Now, "Our Company" section: That's about MCR. Could be "About the Company" or "Company Overview". The rules don't list that as a standard heading, but we can include it as a section with real content. We'll use

      About the Company

      . "What we offer/What's in it for you?" is Benefits. So

      Benefits

      with a list. Now, Pay and Schedule: The posting mentions "Weekly Pay" and "flexible schedule that allows availability early mornings, evenings, weekends, and holidays". That's schedule information. But the rules say never create Pay/Schedule sections unless the posting actually states them. It states "Weekly Pay" and schedule requirements. So we could include a "Pay" section and "Schedule" section? But the rules say "Prefer a few substantive sections over many thin ones." Weekly Pay is one line, schedule is mentioned in requirements. Might be thin. But we can include them in Benefits? Weekly Pay is a benefit. Schedule is a requirement. We'll keep Benefits for the list of offerings. Pay and Schedule might be separate if they have more detail. Here, pay is just "Weekly Pay". That's thin. Schedule is described in requirements. So we can omit separate Pay and Schedule sections. Now, we must remove boilerplate: There's no EEO/legal/scam-warning in the provided text. The text ends with benefits. No application instructions. So we keep all. Now, we need to output only HTML fragment. Let's draft:

      About the Role

      The MCR standard is to provide clean, friendly, well-organized and safe hotels for our guests. Areas of excellence include happy guests, spotless cleanliness, product consistency & quality, and teamwork.

      The Barista at Hilton Miami Blue Lagoon will create, prepare, and serve specialty coffee, tea, and other beverages, either hot or cold. The Barista will educate guests on the drink menu and make recommendations based on their preferences. This person will have excellent service skills and be knowledgeable on how to operate brewing equipment. The overall goal is to ensure an excellent drinking experience offered to all our guests.

      Universal Role Standards