Cashier

We need to output HTML fragment with sections only if there is real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We have company description, pay rates, benefits, job description, qualifications, additional info. Need to map. We need to preserve all substantive info, no boilerplate (EEO, etc). Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop the EEO line and "Military encouraged to apply." Also drop "All qualified applicants will receive consideration..." etc. We need to include sections only when posting has real specific content. We have: - Company Description: includes description of Pilot Company, environment, inclusive atmosphere, etc. Could be "About the role"? Actually "Company Description" is about the company, not the role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have "Pay Rates Starting between: $12.20 - $16.53 / hour". That's pay info -> we can create a Pay section with that. We have Benefits list: Weekly Pay, 15 cent fuel discount, Free daily meals, $10 low-cost health plans (for full-time team members), Paid time off, Family leave. Also Additional Information includes Wellness Program, Reward and Recognition Program, Professional development, 401(k) retirement savings plan, Adoption Assistance. Those are also benefits. So combine into Benefits section. We have Job Description bullet list: Provide guests fast, friendly, and clean service; Maintain inventory; Operate cash registers; Maintain the overall appearance and cleanliness of the restaurant; Provide excellent guest service. That's responsibilities. We have Qualifications: Required Qualifications list: Incredible guest service skills and ability to maintain a guest focused culture; Ability to complete accurate sales transactions; Ability to use computers, telephones, and other equipment as needed; Ability to work as part of a team. Preferred Qualifications: Experience in a similar position; Ability to work a flexible schedule of nights, days, weekends, and holidays. We could put Required Qualifications under Requirements or Qualifications? The headings list includes Requirements and Qualifications separate. Usually Requirements = required qualifications, Qualifications = maybe preferred? But we can decide. Since we have both required and preferred, we could put Required under Requirements, Preferred under Qualifications (or Skills). But we also have Skills heading. Could put skills under Skills. However we have "Incredible guest service skills" etc. Might be better to put skills under Skills. But we need to preserve all info. We have no explicit Schedule info besides "Ability to work a flexible schedule of nights, days, weekends, and holidays." That's schedule info. Could put under Schedule section. We have no explicit About the role section besides company description? Could use About the role to describe the role: maybe summarise from job description? But we must not invent or summarize away detail. We could put a short paragraph describing the role based on the job description bullets? That would be summarizing, which might be disallowed? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we cannot create a summary that is not directly in the posting. However we could use the company description as About the role? That's not exactly role but company. Might be okay to put under About the role? But the heading is About the role, not About the company. Might be considered inaccurate. Better to omit About the role if no specific content. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we should not create About the role if we don't have specific role description beyond the responsibilities list. However we could put the responsibilities under Responsibilities heading, which we have. So we can skip About the role. Thus sections we will output: Responsibilities, Requirements (required qualifications), Qualifications (preferred qualifications), Benefits, Pay, Schedule (if we have schedule info). Also maybe Skills? We could put skills under Skills but we already have required qualifications includes skills. Might be redundant. Better to follow headings list but only include those with content. Let's map: - Responsibilities: the list of duties from Job Description. - Requirements: Required Qualifications list. - Qualifications: Preferred Qualifications list. - Benefits: list of benefits (Weekly Pay, 15 cent fuel discount, Free daily meals, $10 low-cost health plans (for full-time team members), Paid time off, Family leave, Wellness Program, Reward and Recognition Program, Professional development, 401(k) retirement savings plan, Adoption Assistance). Ensure we keep all. - Pay: "Starting between: $12.20 - $16.53 / hour" - Schedule: "Ability to work a flexible schedule of nights, days, weekends, and holidays." (from preferred qualifications). Could also be considered schedule. We should not duplicate content: the schedule ability appears also under Preferred Qualifications; if we put it under Schedule, we should maybe remove from Qualifications to avoid duplication? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay? It says remove duplicated lines. So we should avoid duplicating the same line. So we need to decide where to place that line. Since it's about schedule, better to put under Schedule and not duplicate under Qualifications. Then Qualifications (preferred) would only have "Experience in a similar position". That seems thin but still specific. Could we combine? We could keep Qualifications heading with just that line. That's okay. Thus: Responsibilities: list. Requirements: list of required qualifications. Qualifications: list containing "Experience in a similar position". Benefits: list. Pay: paragraph. Schedule: paragraph. Now we need to format with

headings and

• for lists,

  for prose. We must not include any other headings like About the role, Skills. We must output only HTML fragment. Let's craft:

  Responsibilities

  • Provide guests fast, friendly, and clean service
  • Maintain inventory
  • Operate cash registers
  • Maintain the overall appearance and cleanliness of the restaurant
  • Provide excellent guest service

  Requirements

  • Incredible guest service skills and ability to maintain a guest focused culture
  • Ability to complete accurate sales transactions
  • Ability to use computers, telephones, and other equipment as needed
  • Ability to work as part of a team

  Qualifications

  • Experience in a similar position

  Benefits

  • Weekly Pay
  • 15 cent fuel discount
  • Free daily meals
  • $10 low-cost health plans (for full-time team members)
  • Paid time off
  • Family leave
  • Wellness Program
  • Reward and Recognition Program
  • Professional development
  • 401(k) retirement savings plan
  • Adoption Assistance

  Pay

  Starting between: $12.20 - $16.53 / hour

  Schedule

  Ability to work a flexible schedule of nights, days, weekends, and holidays.

  Check for any boilerplate removed: we removed EEO line, military encouraged, etc. Also removed "Company Description" heading? We used its content? Actually we didn't include company description anywhere. The company description paragraph about Pilot Company is substantive; we omitted it. That would be losing substantive info. The instruction says preserve ALL substantive information. So we need to include that company description somewhere. Where could it fit? Possibly under About the role? But it's about the company, not the role. However we could treat it as "About the role" loosely? But the instruction says headings like About the role, Responsibilities, etc. It didn't forbid using About the role for company description if no other suitable heading. But it's about the role, not company. However we could create a section like "About the company" but not in allowed headings. The allowed headings list is given as examples; we could still use other headings? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But they say "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when appropriate. It doesn't forbid other headings, but to be safe we should stick to those. Could we put company description under About the role? It's not exactly role but maybe acceptable as description of the role's context. However we risk being inaccurate. Another option: we could create a

  without heading for company description, as prose. The instruction: Use

  for prose. So we could just put a

  with the company description before any headings. That would preserve it without a heading. That seems acceptable: we are not required to wrap all content in headings; we can have prose paragraphs. The instruction says use

  for prose. So we can lead with a

  containing the company description. Thus we will output:

  [company description text]

  then the sections. Let's extract company description exactly: "Company Description Pay Rates Starting between: $12.20 - $16.53 / hour Are you passionate about team building, customer service, and meeting new people? Pilot Company offers a dynamic environment where no two days are the same. Team members have the opportunity to build an inclusive atmosphere with their co-workers and make a better day for every type of guest – whether it’s the professional driver stopping for a clean shower, the commuter grabbing their morning coffee, or the vacationer needing their go-to snack along their journey. We embrace and celebrate our diverse guests and team members, who fuel creativity, innovation, and positivity. We strive to make every stop on your career journey — and our guests’ journey — a great one! Also, there are a number of opportunities to work in other roles within our travel centers and restaurants so while we may be hiring for a specific role, we always look to train and offer experience for other roles we have. We hope your next career stop is with us! Join our team and start your journey with Pilot Company." But note that "Company Description Pay Rates Starting between: $12.20 - $16.53 / hour" appears as a line; we need to separate pay rates. The company description includes that phrase? Actually the text seems concatenated: "Company Description Pay Rates Starting between: $12.20 - $16.53 / hour Are you passionate..." So we need to parse: The company description likely is everything before "Pay Rates". But the given snippet: "Company Description Pay Rates Starting between: $12.20 - $16.53 / hour Are you passionate about team building, customer service, and meeting new people? Pilot Company offers a dynamic environment..." So it's ambiguous. Probably the intended structure: There's a heading "Company Description", then a line "Pay Rates Starting between: $12.20 - $16.53 / hour", then a paragraph starting "Are you passionate...". So we should treat "Company Description" as a heading? But we are not to repeat job title as heading; but "Company Description" is not job title. However the allowed headings