Dandan Noodle Server

Here's a thinking process: 1. **Analyze User Request:** - **Goal:** Reformat a job posting into clean, well-structured semantic HTML. - **Rules:** - Use `

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

• ` for lists of duties/requirements/benefits - Use `

  ` for prose - Do NOT repeat job title as heading (already shown) - Do NOT put Job ID / requisition numbers as headings - fold minor metadata into short `

  ` or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Analyze the Input Job Posting:** Let me extract the content from the provided text. It starts with "Job Description The Server is responsible..." and goes on. I need to parse it into sections. Input text: "Job Description The Server is responsible for always providing prompt and friendly food and beverage service to all guests. Responsible for meeting or exceeding sales performance objectives as determined, communicated, and monitored by management. Maintain a welcoming and friendly attitude, while contributing to a teamwork-based work environment.Learn the menu to explain offerings, make recommendations and suggestively sell to our Guests.Provide each guest with a friendly welcome and memorable farewell to ensure a positive, memorable visit and promote repeat visits.Suggestively sell and let guests know about current features and promotions.Ensure Guests' order is accurately recorded in a timely manner.Deliver food to guests within and outside of your section.Check back with guests, provide refills and pre-bus throughout the guest experience.Partner with other Team Members to ensure Guests all guests needs are met.Perform opening and closing duties as well as running side work.Ensure the highest quality preparation and presentation of food and beverage items are delivered to Guest.Responsible for attention and prompt response to the guests' needs and requests throughout their entire visit.Present an accurate guest check, accept payment, and quickly complete the transaction.Answer the phone and assist with answering guests' questions in a friendly, courteous manner.Serve alcoholic beverages in accordance with the policy.Immediately notify management of incidents involving possible excessive alcohol consumption or an impaired condition.Process guest checks and payments in compliance with cash handling, credit card and accounting policies and proceduresReport all tips in compliance with company policy and IRS regulations.Consistent professional and positive attitude and actions when communicating with guests and team.Other duties as assigned. Responsibilities Ability to stand/walk for long periods of time.Repetitive lifting of up to 15 lbs.Work area is subject to variable temperatures.May be subject to smoking environment and moderate noise. Qualifications High School Diploma or High School equivalency preferredAbility to uphold and demonstrate the highest level of integrity in all situations and recognize standards required by a regulated business.Must be able to obtain a required Non-Gaming License. Hourly Rate: $6.76 per hour plus tips" Let me break it down structurally: - It starts with "Job Description" then body text. - Then "Responsibilities" section with bullet points/lines. - Then "Qualifications" section with lines. - Then "Hourly Rate: $6.76 per hour plus tips" There's no explicit "About the role", "Skills", "Benefits", "Schedule", "Pay" (though Pay is mentioned as hourly rate). I need to map to the requested headings but only include sections with real content. Requested headings examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Let's map what we have: - "Responsibilities" is clearly there, with specific duties listed line-by-line. - "Qualifications" is there with specific requirements. - "Hourly Rate: $6.76 per hour plus tips" -> this is Pay/Compensation. I should include a Pay section with this specific info. No placeholder. - There's no explicit "About the role" separate from the job description text, but the initial paragraphs could be "About the role" or just integrated. The rules say: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it). So I shouldn't create an "About the role" heading if it's just repeating the job title. The initial text is the job description prose. I could either put it under a heading or as prose before headings. But the rule says: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So I need to be careful. Let me re-read the input carefully and extract only real content, no fluff. Structure analysis: - Opening prose: "The Server is responsible for always providing prompt and friendly food and beverage service to all guests. Responsible for meeting or exceeding sales performance objectives as determined, communicated, and monitored by management. Maintain a welcoming and friendly attitude, while contributing to a teamwork-based work environment." This is prose. I'll put it in a

  or maybe not use a heading for it, or use "About the role" if there's substantive content beyond just the title. But the rule says: Do NOT repeat the job title as a heading (the page already shows it). It doesn't forbid using "About the role" as a heading if there's real content. The initial paragraphs describe the role's duties and attitude expectations. I think I can either group them under a heading or just as prose. To be safe, I'll maybe not create an "About the role" section unless I feel it's distinctly different from the responsibilities. Actually, the rule says: Prefer a few substantive sections over many thin ones. and include a section ONLY when the posting has real, specific content for it. The opening text is real content, but is it a section? I could put it as a

  before the first h3, or I could create an "About the role" h3 with that prose. But the examples given for headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I need to decide. Let's look at the responsibilities list: "Responsibility Ability to stand/walk for long periods of time.Repetitive lifting of up to 15 lbs.Work area is subject to variable temperatures.May be subject to smoking environment and moderate noise." These are clearly responsibilities/working conditions. Qualifications: "High School Diploma or High School equivalency preferredAbility to uphold and demonstrate the highest level of integrity in all situations and recognize standards required by a regulated business.Must be able to obtain a required Non-Gaming License." Pay: "Hourly Rate: $6.76 per hour plus tips" There's no "Skills" section per se, no "Benefits", no "Schedule". I should not create those sections. Now, how to structure HTML per rules: - Use

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

  • for any list of duties/requirements/benefits - Use

    for prose - Do NOT repeat the job title as a heading - Do NOT put Job ID / requisition numbers as headings - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text and never create Pay/Schedule/Benefits sections unless the posting actually states them - Output ONLY the HTML fragment — no /, no markdown code fences I need to decide on section headings. The posting has: - Prose introduction/description - Responsibilities (with specific duty lines) - Qualifications (with specific lines) - Pay/Hourly Rate I could structure as: -

    Responsibilities

    with
    • items -

      Qualifications

      with
      • items -

        Pay

        with

        $6.76 per hour plus tips

        What about the opening prose? It's not under a clear heading in the input. It starts with "Job Description The Server is responsible...". I could either put it as a

        before any h3, or create an "About the role" h3. But the rule says: include a section ONLY when the posting has real, specific content for it. The opening text is real content, but is it a "section"? I think it's safer to not force a heading for it, or maybe use it as prose before the first heading. However, the rule also says: use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say I must use all of them, only that when I use an h3, it should be one of those (or similar). And I should only include a section if there's real content. Let me re-read carefully: "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This means if I create a section, use an h3 with one of those labels (or similar meaningful ones). "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them." So I will only create sections that have specific content. The posting has specific content for Responsibilities, Qualifications, and Pay (hourly rate). It does not have specific content for Benefits, Schedule, Skills (maybe some skills are implied but not listed as a section). I should not invent them. How to handle the opening prose? I'll put it as a

        at the top, or maybe integrate it into a section? The input starts with "Job Description The Server is responsible...". The "Job Description" might be the title of the posting, but the rule says do NOT repeat the job title as a heading. Since the page already shows the job title (Server), I shouldn't make "Job Description" an h3. I'll treat the initial paragraphs as prose introduction. Let me parse the responsibilities lines. The input says: "Responsibilities Ability to stand/walk for long periods of time.Repetitive lifting of up to 15 lbs.Work area is subject to variable temperatures.May be subject to smoking environment and moderate noise." These are likely part of the responsibilities section