Barista
` 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 Text:**
Let me parse the job posting:
"Job Reference Number: 42879 Employment Type: Full-Time, OnsiteSegment: Dining & Events Brand: Corporate-Chefs Location: Mitre One The Role at a glance: We are looking for a motivated Barista to join an experienced catering team at our corporate dining account, Mitre, in McLean, VA! Enjoy a great work-life balance with a Monday-Thursday 6am-2:30pm schedule Daytime hours; no nights & no weekends! What you'll be doing: Preparing various food and beverage items. Interacting with customers in a friendly, helpful, and engaging manner. Operating a cash register. What we're looking for: Must-haves: The ability to work independently and handle multiple tasks using time and task management skills. Excellent communication and organization skills. Excellent attention to detail and service knowledge. Nice-to-haves: At least one years’ experience working in a retail environment. Our Benefits: Weekly PayNo nights & no weekends!Discount ProgramCommuter Benefits (Parking and Transit) EAPSick TimeHoliday Pay (9 paid holidays)Paid Time Off Growth Opportunities #indeedelior #Boost About Corporate Chefs: Offering foodservice management services to businesses across 17 states and the District of Columbia, Corporate Chefs is an on-site restaurant company that works to provide excellent dining solutions to our clients. With over 30 years of industry experience, we pride ourselves on cooking every meal from scratch, sourcing our ingredients locally, and focusing on the health and wellbeing of our clients. About Elior North America: Elior North America is an equal opportunity employer. Qualified applicants will receive consideration for employment without regard to race, color, religion, sex, national origin, sexual orientation, gender identity, disability or protected veteran status. We are committed to diversity and encourage applications from people of all backgrounds and abilities. We take pride in supporting the development of our employees and their skills at all levels and in fostering an environment of growth. At Elior North America, we are committed to offering growth and advancement opportunities for all of our employees. The valuable skills and experience you’ve gained with Elior will propel you further in your career, whether with our corporate office or one of our brand segments. Disclaimer: This job description can be revised by management as needed."
Now, I need to extract relevant sections and format them per rules.
Let's identify the structure that fits the rules:
- 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)
- Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short `
` or drop it
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
- Preserve ALL substantive information; do NOT invent or summarize away detail
- 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
- Prefer a few substantive sections over many thin ones
Let's parse the content into meaningful sections:
- Job Reference Number: 42879 → metadata, fold into short `
` or drop. Rule: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short `
` or drop it." I'll fold it into a `
` at the top or bottom, but not as a heading.
- Employment Type: Full-Time, Onsite
- Segment: Dining & Events
- Brand: Corporate-Chefs
- Location: Mitre One
- "The Role at a glance:" → This is a summary/overview. Could be part of "About the role" or just a paragraph.
- Schedule: Monday-Thursday 6am-2:30pm, Daytime hours; no nights & no weekends! → This is schedule info. Rule: never create Schedule section unless the posting actually states them. It does state them. But the rule also says: "Prefer a few substantive sections over many thin ones." and "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule, so I can include a Schedule section. But I need to be careful: the rule says "include a section ONLY when the posting has real, specific content for it". It has specific schedule. I'll include it.
- What you'll be doing: → Responsibilities
- What we're looking for: → Requirements/Qualifications
- Must-haves: → list
- Nice-to-haves: → list
- Our Benefits: → Benefits section. It lists: Weekly Pay, No nights & no weekends!, Discount Program, Commuter Benefits (Parking and Transit), EAP, Sick Time, Holiday Pay (9 paid holidays), Paid Time Off, Growth Opportunities. Note: "Weekly Pay" is mentioned, but no specific dollar amount. The rule says never create Pay section unless the posting actually states them. It says "Weekly Pay" - that's stating pay frequency, but not amount. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits, so Benefits section is fine. But "Pay" might be tricky. I'll make a Benefits section, and maybe mention pay frequency within it or as part of benefits. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states "Weekly Pay" and schedule and benefits. So I can include Schedule and Benefits sections. Pay section might just be "Weekly Pay" - I'll probably fold it into Benefits or a short paragraph, but not create a separate "Pay" heading with minimal content. The rule prefers few substantive sections over many thin ones. I'll combine pay info into Benefits or a short paragraph.
- #indeedelior #Boost → probably application instructions/boilerplate, remove.
- About Corporate Chefs: → About the company/culture
- About Elior North America: → EEO/equal opportunity text. Rule: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So I should remove this entire block.
- Disclaimer: → remove.
Let's re-evaluate sections to include, based on rules and actual content:
Possible sections with real specific content:
- About the role (or "The Role at a glance"): has specific schedule and role description. I'll use `
About the role
` or maybe "The Role at a glance" as prose. The rule says use `` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I can map the content to these headings, but only if there's real content.
- Responsibilities: "What you'll be doing:" has 3 bullet points.
- Requirements/Qualifications: "What we're looking for:" has Must-haves and Nice-to-haves. I'll structure as Requirements or Qualifications. The rule lists "Requirements, Qualifications, Skills" as examples. I'll pick one or combine. Must-haves and Nice-to-haves are substantive.
- Benefits: lists several benefits including Weekly Pay, No nights & no weekends!, Discount Program, Commuter Benefits, EAP, Sick Time, Holiday Pay, PTO, Growth Opportunities. I'll make a Benefits section.
- Schedule: "Monday-Thursday 6am-2:30pm schedule Daytime hours; no nights & no weekends!" I'll make a Schedule section. But wait, the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. However, "Prefer a few substantive sections over many thin ones." Schedule is thin but specific. I'll include it if it feels substantive. But I need to check: the schedule is "Monday-Thursday 6am-2:30pm". That's specific. I'll include a Schedule section.
- Pay: "Weekly Pay" is mentioned. I could include a Pay section with "Weekly Pay", but the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Weekly Pay", but creating a whole section for just "Weekly Pay" might be considered a thin section. The rule also says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Weekly Pay" is not filler, it's actual content. But I'm concerned about thin sections. I'll probably fold pay into Benefits or a short paragraph, or include a Pay section with just "Weekly Pay" if I think it's substantive enough. Let's see the exact rule: "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." It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't say "don't create them if they're thin", but the overall preference is "Prefer a few substantive sections over many thin ones." I'll evaluate each.
Let's list all extracted substantive blocks:
1. Job Reference Number: 42879 → metadata, fold into `
` at top or bottom, not as heading.
2. Employment Type: Full-Time, Onsite → could be part of a short intro `
`.
3. Segment: Dining & Events → maybe fold into intro or company description.
4. Brand: Corporate-Chefs → fold into company description.
5. Location: Mitre One → fold into intro.
6. "The Role at a glance:" + schedule text → I'll use this as the "About the role" or "The Role" section content, including schedule.
7. "What you'll be doing:" + 3 items → Responsibilities list.
8. "What we're looking for:" + Must-haves (3) + Nice-to-haves (1) →
` 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 Text:** Let me parse the job posting: "Job Reference Number: 42879 Employment Type: Full-Time, OnsiteSegment: Dining & Events Brand: Corporate-Chefs Location: Mitre One The Role at a glance: We are looking for a motivated Barista to join an experienced catering team at our corporate dining account, Mitre, in McLean, VA! Enjoy a great work-life balance with a Monday-Thursday 6am-2:30pm schedule Daytime hours; no nights & no weekends! What you'll be doing: Preparing various food and beverage items. Interacting with customers in a friendly, helpful, and engaging manner. Operating a cash register. What we're looking for: Must-haves: The ability to work independently and handle multiple tasks using time and task management skills. Excellent communication and organization skills. Excellent attention to detail and service knowledge. Nice-to-haves: At least one years’ experience working in a retail environment. Our Benefits: Weekly PayNo nights & no weekends!Discount ProgramCommuter Benefits (Parking and Transit) EAPSick TimeHoliday Pay (9 paid holidays)Paid Time Off Growth Opportunities #indeedelior #Boost About Corporate Chefs: Offering foodservice management services to businesses across 17 states and the District of Columbia, Corporate Chefs is an on-site restaurant company that works to provide excellent dining solutions to our clients. With over 30 years of industry experience, we pride ourselves on cooking every meal from scratch, sourcing our ingredients locally, and focusing on the health and wellbeing of our clients. About Elior North America: Elior North America is an equal opportunity employer. Qualified applicants will receive consideration for employment without regard to race, color, religion, sex, national origin, sexual orientation, gender identity, disability or protected veteran status. We are committed to diversity and encourage applications from people of all backgrounds and abilities. We take pride in supporting the development of our employees and their skills at all levels and in fostering an environment of growth. At Elior North America, we are committed to offering growth and advancement opportunities for all of our employees. The valuable skills and experience you’ve gained with Elior will propel you further in your career, whether with our corporate office or one of our brand segments. Disclaimer: This job description can be revised by management as needed." Now, I need to extract relevant sections and format them per rules. Let's identify the structure that fits the rules: - 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) - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short `
` or drop it - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - Preserve ALL substantive information; do NOT invent or summarize away detail - 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 - Prefer a few substantive sections over many thin ones Let's parse the content into meaningful sections: - Job Reference Number: 42879 → metadata, fold into short `
` or drop. Rule: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short `
` or drop it." I'll fold it into a `
` at the top or bottom, but not as a heading. - Employment Type: Full-Time, Onsite - Segment: Dining & Events - Brand: Corporate-Chefs - Location: Mitre One - "The Role at a glance:" → This is a summary/overview. Could be part of "About the role" or just a paragraph. - Schedule: Monday-Thursday 6am-2:30pm, Daytime hours; no nights & no weekends! → This is schedule info. Rule: never create Schedule section unless the posting actually states them. It does state them. But the rule also says: "Prefer a few substantive sections over many thin ones." and "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule, so I can include a Schedule section. But I need to be careful: the rule says "include a section ONLY when the posting has real, specific content for it". It has specific schedule. I'll include it. - What you'll be doing: → Responsibilities - What we're looking for: → Requirements/Qualifications - Must-haves: → list - Nice-to-haves: → list - Our Benefits: → Benefits section. It lists: Weekly Pay, No nights & no weekends!, Discount Program, Commuter Benefits (Parking and Transit), EAP, Sick Time, Holiday Pay (9 paid holidays), Paid Time Off, Growth Opportunities. Note: "Weekly Pay" is mentioned, but no specific dollar amount. The rule says never create Pay section unless the posting actually states them. It says "Weekly Pay" - that's stating pay frequency, but not amount. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits, so Benefits section is fine. But "Pay" might be tricky. I'll make a Benefits section, and maybe mention pay frequency within it or as part of benefits. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states "Weekly Pay" and schedule and benefits. So I can include Schedule and Benefits sections. Pay section might just be "Weekly Pay" - I'll probably fold it into Benefits or a short paragraph, but not create a separate "Pay" heading with minimal content. The rule prefers few substantive sections over many thin ones. I'll combine pay info into Benefits or a short paragraph. - #indeedelior #Boost → probably application instructions/boilerplate, remove. - About Corporate Chefs: → About the company/culture - About Elior North America: → EEO/equal opportunity text. Rule: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So I should remove this entire block. - Disclaimer: → remove. Let's re-evaluate sections to include, based on rules and actual content: Possible sections with real specific content: - About the role (or "The Role at a glance"): has specific schedule and role description. I'll use `
About the role
` or maybe "The Role at a glance" as prose. The rule says use `` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I can map the content to these headings, but only if there's real content. - Responsibilities: "What you'll be doing:" has 3 bullet points. - Requirements/Qualifications: "What we're looking for:" has Must-haves and Nice-to-haves. I'll structure as Requirements or Qualifications. The rule lists "Requirements, Qualifications, Skills" as examples. I'll pick one or combine. Must-haves and Nice-to-haves are substantive. - Benefits: lists several benefits including Weekly Pay, No nights & no weekends!, Discount Program, Commuter Benefits, EAP, Sick Time, Holiday Pay, PTO, Growth Opportunities. I'll make a Benefits section. - Schedule: "Monday-Thursday 6am-2:30pm schedule Daytime hours; no nights & no weekends!" I'll make a Schedule section. But wait, the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. However, "Prefer a few substantive sections over many thin ones." Schedule is thin but specific. I'll include it if it feels substantive. But I need to check: the schedule is "Monday-Thursday 6am-2:30pm". That's specific. I'll include a Schedule section. - Pay: "Weekly Pay" is mentioned. I could include a Pay section with "Weekly Pay", but the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Weekly Pay", but creating a whole section for just "Weekly Pay" might be considered a thin section. The rule also says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Weekly Pay" is not filler, it's actual content. But I'm concerned about thin sections. I'll probably fold pay into Benefits or a short paragraph, or include a Pay section with just "Weekly Pay" if I think it's substantive enough. Let's see the exact rule: "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." It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't say "don't create them if they're thin", but the overall preference is "Prefer a few substantive sections over many thin ones." I'll evaluate each. Let's list all extracted substantive blocks: 1. Job Reference Number: 42879 → metadata, fold into `
` at top or bottom, not as heading. 2. Employment Type: Full-Time, Onsite → could be part of a short intro `
`. 3. Segment: Dining & Events → maybe fold into intro or company description. 4. Brand: Corporate-Chefs → fold into company description. 5. Location: Mitre One → fold into intro. 6. "The Role at a glance:" + schedule text → I'll use this as the "About the role" or "The Role" section content, including schedule. 7. "What you'll be doing:" + 3 items → Responsibilities list. 8. "What we're looking for:" + Must-haves (3) + Nice-to-haves (1) →