Busser

Here's a thinking process: 1. **Analyze the Request:** - User wants me to 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 (page already shows it) - 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") - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Analyze the Input Text:** Let me extract the content from the provided job posting text. I'll go through it carefully. Text: "At Fogo de Chão, we strive to give our guests an unforgettable dining experience of discovery while showcasing the Culinary Art of Churrasco. Our mission is to ignite fire and joy to care for our team, our guests, and our communities. We believe better futures start when we bring our best to the table every day to Feed a Purposeful Future – starting with our team members. We feed our teams with fulfilling job opportunities, making space around the table so everyone feels welcome. At Fogo, we’ll provide you with a fulfilling career with professional and personal growth opportunities at every level. Our values of teamwork, integrity, excellence, humility and Deixa Comigo (we’ve got you!) are more than just words, it’s how we do things every day. Now Hiring / Immediately Hiring Busser / Bussers Essential Duties and Responsibilities include the following. Other duties may be assigned. Provides Server support by maintaining the ice water, cheese rolls, side dishes and any other items as directed at each table. Executes table clean up and setup in an efficient manner. Transports trays from the dining room to the dishwashing area. Completes any beginning or closing shift duties. Assists in maintaining each service station. Manages competing demands while putting the guest first. Requirements Must be able to stand and walk for long periods of time and transport objects up to 25 lbs. Must be able to work weekends and holidays. Medical, Dental, and Vision insurance are available for full-time, hourly Team Members on the first of the month following 60 days of employment. Additionally, company-paid Life Insurance and Short-Term Disability are provided where allowed. We offer a comprehensive voluntary benefits package including Critical Illness, Hospital Indemnity, Accident Coverage, Permanent Life, and Pet Insurance. Part-Time Team Members are offered a Minimum Essential Coverage (MEC) Health plan in addition to Dental, Vision, Short-Term Disability, and Life Insurance. Coverage for these plans can start as early as the first of the month following your hire date. Additionally, Part-Time Team Members are offered enrollment in voluntary benefits, including Pet Insurance, Legal, and ID Protection. Fogo de Chão is an Equal Opportunity & E Verify Employer This position has a fixed rate of $12.77 and is also eligible to receive tips. Additional details regarding tips will be made available during onboarding or upon request." Now, I need to identify sections, headings, lists, prose, and filter out boilerplate. Let's parse and categorize: - Opening paragraph about mission, values, culture: This is prose/culture content. It doesn't fit neatly into the specified headings unless I create an "About the role" or similar section. The rules say use `

  ` for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I should use these only if there's real content. The opening is substantive about the company mission/values. I could put it under "About the role" or just as prose before the sections. But the rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I need to decide which sections to include based on actual content. Let's list what has clear content: - About/Company mission/values: present - Responsibilities/Duties: present (list of essential duties) - Requirements: present (stand/walk, transport up to 25 lbs, work weekends/holidays) - Qualifications/Skills: The "Requirements" section seems to cover this. No separate "Skills" section with specific skills beyond requirements. - Benefits: present (insurance details for full-time and part-time, voluntary benefits) - Pay: present ("fixed rate of $12.77 and is also eligible to receive tips") - Schedule: mentioned "Must be able to work weekends and holidays" - this is a scheduling requirement, but not a detailed schedule. I'll consider if it warrants a "Schedule" section. The rules say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". "Must be able to work weekends and holidays" is specific, but it's a requirement, not a schedule per se. I might fold it into Requirements or have a brief Schedule note. But rules prefer a few substantive sections over many thin ones. I'll likely fold weekend/holiday requirement into Requirements, or maybe include a Schedule section if there's actual schedule info. There's no specific schedule (like "8am-5pm", "rotating shifts", etc.), just "weekends and holidays". I'll probably not create a separate Schedule section, or maybe a very brief one. Let's see. - Pay: explicitly stated "$12.77 fixed rate + tips". This is real content. I'll include a Pay section. - Benefits: detailed insurance info for full-time and part-time, voluntary benefits. Real content. Include Benefits section. - EEO/Fogo de Chão is an Equal Opportunity & E Verify Employer: this is boilerplate to remove per instructions: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So I remove the "Fogo de Chão is an Equal Opportunity & E Verify Employer" line, and the "This position has a fixed rate of $12.77 and is also eligible to receive tips. Additional details regarding tips will be made available during onboarding or upon request." Wait, the pay info is substantive. The tips note is additional but maybe I should include the pay rate. The instructions say "Remove ... legal/EEO/equal-opportunity/scam-warning boilerplate". The "Equal Opportunity & E Verify Employer" is legal/EEO boilerplate. I'll remove it. The pay and tips info: "This position has a fixed rate of $12.77 and is also eligible to receive tips. Additional details regarding tips will be made available during onboarding or upon request." The pay rate is substantive. The tips note is somewhat meta but contains real info. I'll include the pay rate in Pay section, and maybe note tips eligibility but not the "additional details" part if it's just procedural. Actually, the rule: "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should keep the $12.77 and tips eligibility. I'll put Pay as a section with the rate and tips info. I'll fold the "Additional details..." into a

  or drop it if it's just application instructions. The rule says "Remove ... application instructions". So I'll drop "Additional details regarding tips will be made available during onboarding or upon request." Let's restructure: Heading structure per rules:

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I need to map the content to these. I should not create headings that have placeholder/filler text. I'll only create sections that have real, specific content. Let's map: - "About the role" / company mission/values: The posting starts with a paragraph about mission, values, culture. I'll create an "About the role" section with that prose. It's substantive. - "Responsibilities": The list of essential duties. I'll use

  • for each duty. - "Requirements": The must-able-to statements. I'll use
    • or keep as prose? Rules say "Use
      • for any list of duties/requirements/benefits". So requirements should be a list. - "Qualifications": Not explicitly separate from requirements here. The requirements section covers qualifications. I could either fold into Requirements or have a Qualifications section if there's distinct content. There's no separate qualifications beyond requirements. I'll not create a thin Qualifications section. I'll either include qualifications under Requirements or skip. Rules: "Prefer a few substantive sections over many thin ones." So I'll combine or skip. I think I'll just have Requirements as a section, and maybe note qualifications within it. But the heading list includes "Qualifications" as an example. I'll check if there's content that fits Qualifications distinct from Requirements. "Must be able to stand and walk for long periods of time and transport objects up to 25 lbs. Must be able to work weekends and holidays." That's requirements. I'll keep it as Requirements. I won't create a Qualifications section without distinct content. - "Skills": Not really present. No separate skills list. I'll skip. - "Benefits": Detailed insurance info. I'll create a Benefits section with lists for full-time and part-time. - "Pay": "$12.77 fixed rate + tips". I'll create a Pay section. - "Schedule": "Must be able to work weekends and holidays." This is a scheduling requirement. I could put it in a Schedule section, but it's really a requirement. I'll fold it into Requirements or maybe create a brief Schedule section with that one line. But rules say "never emit a heading followed by filler/placeholder text". If I create Schedule, I need specific content. "Must be able to work weekends and holidays" is specific, but it's a requirement. I'll probably not create a Schedule section, or I'll include it as a

        under Requirements. I'll decide after mapping. Let's re-read the input carefully and extract exact wording for lists. Opening prose (About the role/mission/values): "At Fogo de Chão, we strive to give our guests an unforgettable dining experience of discovery while showcasing the Culinary Art of Churrasco. Our mission is to ignite fire and joy to care for our team, our guests, and our communities. We believe better futures start when we bring our best to the table every day to Feed a Purposeful Future – starting with our team members. We feed our teams with fulfilling job opportunities, making space around the table so everyone feels welcome. At Fogo, we’ll provide you with a fulfilling career with professional and personal growth opportunities at every level. Our values of teamwork, integrity, excellence, humility and Deixa Comigo (we’ve got you!) are more than just words, it’s how we do things every day." Then: "Now Hiring / Immediately Hiring Busser / Bussers Essential Duties and Responsibilities include the following. Other duties may be assigned." Duties list: - Provides Server support by maintaining the