Carhop

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Posting text: "Hot burgers, cold shakes, and little moments of magic right in the neighborhood. At SONIC, we do things a little differently. We find the fun, the moment of chill in the every-day. Working at SONIC, you’ll spark moments of delightful possibility. Feelin’ these good vibes? Let’s do this. Start with a Job, Spark a Career As a SONIC Drive-In Carhop, you will deliver a friendly, and fast experience to every customer. Your menu genius skills and ability to resolve customer concerns will guarantee every customer leaves satisfied. Moments of Magic You Bring to the Crew At least 16 years of age Eligible to work in the U.S. Not sure if your experience aligns? We encourage you to apply. Cherry Limeade-lover or not, all backgrounds are welcome here. Feelin’ these good vibes? The opportunity to discover all our different drink combinations on your list? How about all these benefits? We have you covered. Weekly Pay Flexible Schedule Shift Meal Discount and Family Dining Discount* Best-in-Class Training & Continuous Learning Advancement Opportunities Referral Bonus Program Medical, Dental, Vision* 401(k) Retirement Program* Paid Time Off* Well-Being Program* Employee Assistance Program* Perkspot Discount Program Recognition Program Slip Resistant Shoes Program Community & Charitable Involvement Champions of Hope* Yearly Contests SONIC is an equal opportunity employer. Subject to availability and eligibility requirements." We need to remove boilerplate: equal opportunity employer line, maybe also "Subject to availability and eligibility requirements." Also remove duplicated lines? Not many duplicates. We need to preserve all substantive info. We need to identify sections: - About the role: maybe the first paragraph describing SONIC and role: "Hot burgers, cold shakes, and little moments of magic right in the neighborhood. At SONIC, we do things a little differently. We find the fun, the moment of chill in the every-day. Working at SONIC, you’ll spark moments of delightful possibility. Feelin’ these good vibes? Let’s do this. Start with a Job, Spark a Career As a SONIC Drive-In Carhop, you will deliver a friendly, and fast experience to every customer. Your menu genius skills and ability to resolve customer concerns will guarantee every customer leaves satisfied." That's prose. - Responsibilities: maybe "deliver a friendly, and fast experience to every customer. Your menu genius skills and ability to resolve customer concerns will guarantee every customer leaves satisfied." Could be responsibilities. - Requirements: "At least 16 years of age Eligible to work in the U.S." Also maybe "Not sure if your experience aligns? We encourage you to apply." That's not a requirement but encouragement. - Qualifications: maybe none specific. - Skills: "menu genius skills and ability to resolve customer concerns" could be skills. - Benefits: list: Weekly Pay, Flexible Schedule, Shift Meal Discount and Family Dining Discount*, Best-in-Class Training & Continuous Learning, Advancement Opportunities, Referral Bonus Program, Medical, Dental, Vision*, 401(k) Retirement Program*, Paid Time Off*, Well-Being Program*, Employee Assistance Program*, Perkspot Discount Program, Recognition Program, Slip Resistant Shoes Program, Community & Charitable Involvement, Champions of Hope*, Yearly Contests. - Pay: "Weekly Pay" is mentioned; we could have a Pay section with that detail. - Schedule: "Flexible Schedule" maybe. But we need to avoid thin sections. We could combine Pay and Schedule into Benefits? But guidelines: Use headings only when posting has real specific content. We have Weekly Pay and Flexible Schedule as specific content. Could create separate sections for Pay and Schedule, each with a

containing that line. But we also have "Shift Meal Discount and Family Dining Discount*" which is a benefit. We need to ensure we don't create sections with filler like "not specified". We have actual content. We need to output only HTML fragment, no /, no markdown. We'll produce something like:

About the role

Hot burgers, cold shakes, and little moments of magic right in the neighborhood. At SONIC, we do things a little differently. We find the fun, the moment of chill in the every-day. Working at SONIC, you’ll spark moments of delightful possibility. Feelin’ these good vibes? Let’s do this. Start with a Job, Spark a Career As a SONIC Drive-In Carhop, you will deliver a friendly, and fast experience to every customer. Your menu genius skills and ability to resolve customer concerns will guarantee every customer leaves satisfied.

Responsibilities

• Deliver a friendly and fast experience to every customer.
• Use menu genius skills to resolve customer concerns and ensure satisfaction.

But we need to preserve all substantive info; we can't invent. The original says "Your menu genius skills and ability to resolve customer concerns will guarantee every customer leaves satisfied." That's a statement, not necessarily a responsibility list. Could be phrased as responsibility. We could keep as prose:

Deliver a friendly, and fast experience to every customer. Your menu genius skills and ability to resolve customer concerns will guarantee every customer leaves satisfied.

But guidelines: Use

• for any list of duties/requirements/benefits. If we have a list, we should use list. If not list, use

  . The responsibilities could be a list of two items: deliver friendly/fast experience; use menu genius skills to resolve concerns. That's derived but maybe okay. However we must not invent detail; we are just splitting the sentence into two bullet points, which is still preserving the info. That's acceptable. Requirements: At least 16 years of age; Eligible to work in the U.S. We could make a list. Skills: menu genius skills; ability to resolve customer concerns. But we already used that in responsibilities; maybe we can put skills separate. But we need to avoid duplication? Not prohibited but we should preserve all info; duplication okay if it's in original? The original mentions those skills only once. If we put them in both responsibilities and skills, we duplicate. Better to assign to one section. We could treat "menu genius skills and ability to resolve customer concerns" as skills, and responsibilities as delivering friendly/fast experience. Thus: Responsibilities: Deliver a friendly and fast experience to every customer. Skills: Menu genius skills; Ability to resolve customer concerns. Requirements: At least 16 years of age; Eligible to work in the U.S. Benefits: list all benefits. Pay: Weekly Pay. Schedule: Flexible Schedule. We need to ensure we don't create sections with placeholder like "not specified". We have actual. Now format. We'll output:

  About the role

  Hot burgers, cold shakes, and little moments of magic right in the neighborhood. At SONIC, we do things a little differently. We find the fun, the moment of chill in the every-day. Working at SONIC, you’ll spark moments of delightful possibility. Feelin’ these good vibes? Let’s do this. Start with a Job, Spark a Career As a SONIC Drive-In Carhop, you will deliver a friendly, and fast experience to every customer. Your menu genius skills and ability to resolve customer concerns will guarantee every customer leaves satisfied.

  Responsibilities

  • Deliver a friendly and fast experience to every customer.

  Skills

  • Menu genius skills
  • Ability to resolve customer concerns

  Requirements

  • At least 16 years of age
  • Eligible to work in the U.S.

  Benefits

  • Weekly Pay
  • Flexible Schedule
  • Shift Meal Discount and Family Dining Discount*
  • Best-in-Class Training & Continuous Learning
  • Advancement Opportunities
  • Referral Bonus Program
  • Medical, Dental, Vision*
  • 401(k) Retirement Program*
  • Paid Time Off*
  • Well-Being Program*
  • Employee Assistance Program*
  • Perkspot Discount Program
  • Recognition Program
  • Slip Resistant Shoes Program
  • Community & Charitable Involvement
  • Champions of Hope*
  • Yearly Contests
  But note we duplicated Weekly Pay and Flexible Schedule also in Benefits list; we also have separate Pay and Schedule sections. To avoid duplication, we could not include them in Benefits list, but the original lumps them together with other benefits. The instruction: "Use
  • for any list of duties/requirements/benefits". If we make Pay and Schedule sections, we still need to list them somewhere. Could either keep them only in Pay/Schedule sections and not repeat in Benefits. But the original says "Weekly Pay Flexible Schedule Shift Meal Discount and Family Dining Discount* ..." It's a sentence listing benefits. It's okay to split them. We need to preserve ALL substantive information; not duplicate is fine as long as we don't lose info. If we put Weekly Pay and Flexible Schedule only under Pay and Schedule sections, we still have them. So we can omit them from Benefits list to avoid duplication. Thus Benefits list will start from Shift Meal Discount etc. Let's craft:

    Pay

    Weekly Pay

    Schedule

    Flexible Schedule

    Benefits

    • Shift Meal Discount and Family Dining Discount*
    • Best-in-Class Training & Continuous Learning
    • Advancement Opportunities
    • Referral Bonus Program
    • Medical, Dental, Vision*
    • 401(k) Retirement Program*
    • Paid Time Off*
    • Well-Being Program*
    • Employee Assistance Program*
    • Perkspot Discount Program
    • Recognition Program
    • Slip Resistant Shoes Program
    • Community & Charitable Involvement
    • Champions of Hope*
    • Yearly Contests
    Now check we haven't missed any info: The posting also mentions "Cherry Limeade-lover or not, all backgrounds are welcome here." That's a statement about inclusivity; could be part of About the role or maybe a separate section like "Equal Opportunity" but we removed EEO boilerplate. However this line is not boilerplate; it's a welcoming statement. Should we preserve? It's substantive: "Cherry Limeade-lover or not, all backgrounds are welcome here." Could be included in About the role paragraph. We can add that sentence to About the role. Also "Not sure if your experience aligns? We encourage you to apply." That's encouragement; could be part of About the role or maybe a separate "Encouragement" but we can incorporate. Also "Feelin’ these good vibes? The opportunity to discover all our different drink combinations on your list? How about all these benefits? We have you covered." That's marketing fluff; we could incorporate into About the role or Benefits intro. We need to preserve all substantive information; we can embed