Shift Manager

We need to output HTML fragment with headings

for sections: 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 Restaurant Shift Manager, you will be responsible for assisting the General Manager and Assistant General Manager in managing the daily operations of the restaurant. You will provide quality food in a clean, safe, and efficient manner so that guests will have an enjoyable experience every time. You will also assist with hiring, training, and developing team members helping them spark moments of delightful possibility for our customers. Moments of Magic You Bring to the Crew At least 18 years of age Eligible to work in the U.S. Preferably, you have six months or more of restaurant experience 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 sections: About the role (maybe intro paragraph). Responsibilities (list of duties). Requirements (age, eligibility, experience). Qualifications? Might be overlapping with requirements. Skills? Not explicit. Benefits: list of benefits. Pay: "Weekly Pay". Schedule: "Flexible Schedule". Also "Shift Meal Discount and Family Dining Discount*" etc. We need to preserve all substantive info. Not invent. We need to use

for each section heading. Use

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

  for prose. We must not repeat job title as heading. The page already shows it, so we don't add a heading for "Restaurant Shift Manager". Also do not put Job ID/requisition numbers as headings (none present). We need to include sections only when posting has real specific content. Let's extract content: Intro paragraph: "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". That's about the role/company. Could be "About the role". We'll put that in

  . Responsibilities: "As a Restaurant Shift Manager, you will be responsible for assisting the General Manager and Assistant General Manager in managing the daily operations of the restaurant. You will provide quality food in a clean, safe, and efficient manner so that guests will have an enjoyable experience every time. You will also assist with hiring, training, and developing team members helping them spark moments of delightful possibility for our customers." We can break into bullet list? It's prose but could be list. The instruction: Use

  • for any list of duties/requirements/benefits. The responsibilities are more like sentences; we could still put them as list items. Probably better to list each duty as
  • . Let's extract duties: - Assist the General Manager and Assistant General Manager in managing the daily operations of the restaurant. - Provide quality food in a clean, safe, and efficient manner so that guests have an enjoyable experience every time. - Assist with hiring, training, and developing team members helping them spark moments of delightful possibility for our customers. That seems fine. Requirements: "At least 18 years of age", "Eligible to work in the U.S.", "Preferably, you have six months or more of restaurant experience". Also "Not sure if your experience aligns? We encourage you to apply." That's encouragement, not a requirement. Also "Cherry Limeade-lover or not, all backgrounds are welcome here." That's inclusion statement, maybe not requirement. We'll keep requirements as those three. Qualifications: Might be same as requirements; but we could combine. Since we have both Requirements and Qualifications sections, we need to see if there is distinct content for Qualifications. The posting doesn't separate qualifications; it's just requirements. So we might not create a Qualifications section if no specific content beyond requirements. The instruction: Prefer a few substantive sections over many thin ones. So we could combine requirements and qualifications into one section called "Requirements". Or we could have Requirements and Qualifications both but they'd be similar; better to just have Requirements. Skills: Not explicitly listed. Could infer but not given. So we skip 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". Also note asterisks maybe indicate eligibility. We'll keep them as is. Pay: "Weekly Pay" is a benefit but also could be separate Pay section. The instruction: include Pay section only if posting actually states them. It does state "Weekly Pay". So we can have a Pay section with that line. Schedule: "Flexible Schedule" also stated. So we can have Schedule section. We need to avoid duplication: If we list Weekly Pay and Flexible Schedule also in Benefits, we might duplicate. Better to keep them in their own sections and not repeat in Benefits. However Benefits list includes those items; we could keep them in Benefits but then also have separate Pay and Schedule sections; duplication would be repeating same info. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. However we need to follow the rule: Use

    for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include. If we include Benefits, we should include all benefits, including Weekly Pay and Flexible Schedule. If we also include Pay and Schedule sections, we would duplicate. The instruction says "Prefer a few substantive sections over many thin ones." So maybe better to combine Pay and Schedule into Benefits section, and not create separate Pay and Schedule sections. But the rule says we can include those headings only if posting has real specific content for them. It does have specific content for Pay and Schedule, but we could still include them as sub-items under Benefits. However 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 could include Pay and Schedule sections with the specific content (Weekly Pay, Flexible Schedule). That would be specific. But then Benefits section would still have other benefits. That would cause some duplication but not necessarily forbidden. However "Prefer a few substantive sections over many thin ones." Having Pay and Schedule as separate thin sections might be considered thin. Better to incorporate them into Benefits. But the instruction about headings list includes Pay and Schedule as possible headings; we are not required to use them. So we can choose not to include Pay and Schedule sections if we think they'd be thin. However we must preserve all substantive info; we can still include Weekly Pay and Flexible Schedule as items under Benefits. That preserves them. Thus sections: About the role (intro), Responsibilities (list), Requirements (list), Benefits (list). Possibly also Qualifications? Not needed. We need to ensure we don't include boilerplate: equal opportunity employer line, "Subject to availability and eligibility requirements." Remove. Also remove "Feelin’ these good vibes?" lines that are promotional but not substantive? They are part of intro maybe. We'll keep some of the motivational lines as part of About the role. Let's craft HTML:

    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.

    Responsibilities

    • Assist the General Manager and Assistant General Manager in managing the daily operations of the restaurant.
    • Provide quality food in a clean, safe, and efficient manner so that guests have an enjoyable experience every time.
    • Assist with hiring, training, and developing team members helping them spark moments of delightful possibility for our customers.

    Requirements

    • At least 18 years of age
    • Eligible to work in the U.S.
    • Preferably, six months or more of restaurant experience

    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
    We should also maybe include "Cherry Limeade-lover or not, all backgrounds are welcome here." Could be part of About the role or Requirements as inclusion statement. Might be considered substantive. We could add a sentence in About the role: "Cherry Limeade-lover or not, all backgrounds are welcome here." Or we could add a separate line under Requirements? It's more about inclusivity. Let's add to About the role paragraph at end. Thus About the role paragraph: include that line. Now ensure no boilerplate: removed equal opportunity line and "Subject to availability and eligibility requirements." Also removed duplicated lines like "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 promotional but maybe part of About the role? It mentions benefits; we already have benefits list. Could include a sentence about discovering drink combos? That's not essential; but it's part of posting. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that line if it's substantive. It's