Shift Manager
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need sections only when posting has real specific content. So we can have sections: About the role (maybe not needed as heading? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role, Responsibilities, Requirements, Benefits. Possibly also Pay and Schedule if mentioned: Weekly Pay, Flexible Schedule are mentioned under benefits. Could create separate Pay and Schedule sections? The instruction: prefer a few substantive sections over many thin ones. So maybe combine Pay and Schedule into Benefits? But they said use headings like Pay, Schedule if posting actually states them. The posting states Weekly Pay and Flexible Schedule. So we could have separate Pay and Schedule sections. However they also said prefer a few substantive sections over many thin ones. Having many sections may be thin. But we can still include them if they have content. Let's think: Pay: Weekly Pay. Schedule: Flexible Schedule. Benefits: list of other benefits. Could combine Pay and Schedule into Benefits? But they are separate headings in the list of possible headings. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings if content exists. It says "include a section ONLY when the posting has real, specific content for it". So we can have Pay section with Weekly Pay. Schedule section with Flexible Schedule. Benefits section with the rest.
We also need About the role: prose describing role. Responsibilities: list of duties (providing quality food, assisting with hiring, training, developing team members). Requirements: list (at least 18, eligible to work in US, preferably six months restaurant experience). Possibly also "Not sure if your experience aligns? We encourage you to apply." That's more encouragement, maybe not a requirement. Could be part of About the role? Might be boilerplate? It's not duplicated. Could be considered a call to action; but we should remove application instructions. That line is encouraging to apply, maybe considered application instruction? It says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Also "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The line "Not sure if your experience aligns? We encourage you to apply." is an application instruction? It's encouraging to apply, maybe considered application instruction. Safer to drop it.
Also "Cherry Limeade-lover or not, all backgrounds are welcome here." That's a welcoming statement, maybe not boilerplate but could be considered EEO? It's about inclusivity, maybe okay to keep? It's not duplicated. Could be part of About the role? Might be considered EEO but not exactly equal-opportunity boilerplate. It's a welcoming statement. Might keep as prose.
We also have "Moments of Magic You Bring to the Crew" heading in original. Could be a section? Not in the list of headings but we could treat as About the role? Might be better to keep as a heading? The instruction only gave examples; we can use other headings if needed? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those. Safer to stick to those.
Thus we will create sections:
About the role
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.
Maybe also include the welcoming line: "Cherry Limeade-lover or not, all backgrounds are welcome here." Could add to same .
Responsibilities
- Provide quality food in a clean, safe, and efficient manner
- Assist with hiring, training, and developing team members
Requirements
- At least 18 years of age
- Eligible to work in the U.S.
- Preferably, you have six months or more of restaurant experience
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
We should not include asterisks? They are part of the original; we keep them.
Check for duplicated lines: we removed duplicate "Feelin’ these good vibes?" lines. Also removed EEO line. Also removed "Subject to availability and eligibility requirements." That's boilerplate; remove.
Check for any other duplicated: "Moments of Magic You Bring to the Crew" heading we didn't use; we incorporated its content into About the role? Actually that heading preceded the requirements list. We didn't include that heading; we just used Requirements. That's fine.
We need to ensure we didn't miss any substantive info: The posting also had "Start with a Job, Spark a Career". That's a tagline; maybe not needed. Could be considered boilerplate? It's marketing. Might be okay to include in About the role? But it's not a duty. Could be omitted as it's not specific to role. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Is "Start with a Job, Spark a Career" substantive? It's a tagline; maybe not essential. Could be considered boilerplate. I'd drop it.
Also "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." That's introductory marketing fluff. Could be considered boilerplate? It's not specific to role. Might be considered fluff but it's substantive about company culture. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It's not boilerplate like legal/EEO. It's describing the vibe. Could keep as part of About the role? Might be okay to include a short paragraph about the company vibe. However the instruction about sections: we have About the role; we could include that fluff there. But it's not about the role specifically; it's about the company. Might still be okay.
But we need to avoid duplication; we already have a paragraph about role. We could add another paragraph after that about the vibe. Let's include: 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.
We already used "Feelin’ these good vibes? Let’s do this." That's duplicated; we have only one occurrence? We have that line in the intro? Actually the intro includes "Feelin’ these good vibes? Let’s do this." We'll keep that as part of the vibe paragraph? But we need to avoid duplication; we have only one occurrence if we include it once. The intro also had "Feelin’ these good vibes? Let’s do this." Later there is another "Feelin’ these good vibes? The opportunity to discover all our different drink combinations on your list? How about all these benefits?" We'll drop the second occurrence. So we keep the first.
Thus we can have About the role section with two paragraphs: first the vibe/intro, second the role description.
Let's craft:
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.
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.
That seems good.
Now Responsibilities: we have two items.
Requirements: three items.
Pay: Weekly Pay.
Schedule: Flexible Schedule.
Benefits: list as above.
Check for any other specifics: "Shift Meal Discount and Family Dining Discount*" we kept.
Now ensure we didn't include any boilerplate like "SONIC is an equal opportunity employer." Removed.
Check for any leftover duplicated lines: we removed the second "Feelin’ these good vibes?" line. Also removed "Cherry Limeade-lover or
for prose. We need sections only when posting has real specific content. So we can have sections: About the role (maybe not needed as heading? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role, Responsibilities, Requirements, Benefits. Possibly also Pay and Schedule if mentioned: Weekly Pay, Flexible Schedule are mentioned under benefits. Could create separate Pay and Schedule sections? The instruction: prefer a few substantive sections over many thin ones. So maybe combine Pay and Schedule into Benefits? But they said use headings like Pay, Schedule if posting actually states them. The posting states Weekly Pay and Flexible Schedule. So we could have separate Pay and Schedule sections. However they also said prefer a few substantive sections over many thin ones. Having many sections may be thin. But we can still include them if they have content. Let's think: Pay: Weekly Pay. Schedule: Flexible Schedule. Benefits: list of other benefits. Could combine Pay and Schedule into Benefits? But they are separate headings in the list of possible headings. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings if content exists. It says "include a section ONLY when the posting has real, specific content for it". So we can have Pay section with Weekly Pay. Schedule section with Flexible Schedule. Benefits section with the rest.
We also need About the role: prose describing role. Responsibilities: list of duties (providing quality food, assisting with hiring, training, developing team members). Requirements: list (at least 18, eligible to work in US, preferably six months restaurant experience). Possibly also "Not sure if your experience aligns? We encourage you to apply." That's more encouragement, maybe not a requirement. Could be part of About the role? Might be boilerplate? It's not duplicated. Could be considered a call to action; but we should remove application instructions. That line is encouraging to apply, maybe considered application instruction? It says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Also "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The line "Not sure if your experience aligns? We encourage you to apply." is an application instruction? It's encouraging to apply, maybe considered application instruction. Safer to drop it. Also "Cherry Limeade-lover or not, all backgrounds are welcome here." That's a welcoming statement, maybe not boilerplate but could be considered EEO? It's about inclusivity, maybe okay to keep? It's not duplicated. Could be part of About the role? Might be considered EEO but not exactly equal-opportunity boilerplate. It's a welcoming statement. Might keep as prose. We also have "Moments of Magic You Bring to the Crew" heading in original. Could be a section? Not in the list of headings but we could treat as About the role? Might be better to keep as a heading? The instruction only gave examples; we can use other headings if needed? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those. Safer to stick to those.
Thus we will create sections:
About the role
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.
Maybe also include the welcoming line: "Cherry Limeade-lover or not, all backgrounds are welcome here." Could add to same.
Responsibilities
- Provide quality food in a clean, safe, and efficient manner
- Assist with hiring, training, and developing team members
Requirements
- At least 18 years of age
- Eligible to work in the U.S.
- Preferably, you have six months or more of restaurant experience
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
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.
We already used "Feelin’ these good vibes? Let’s do this." That's duplicated; we have only one occurrence? We have that line in the intro? Actually the intro includes "Feelin’ these good vibes? Let’s do this." We'll keep that as part of the vibe paragraph? But we need to avoid duplication; we have only one occurrence if we include it once. The intro also had "Feelin’ these good vibes? Let’s do this." Later there is another "Feelin’ these good vibes? The opportunity to discover all our different drink combinations on your list? How about all these benefits?" We'll drop the second occurrence. So we keep the first. Thus we can have About the role section with two paragraphs: first the vibe/intro, second the role description. Let's craft: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.
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.
That seems good. Now Responsibilities: we have two items. Requirements: three items. Pay: Weekly Pay. Schedule: Flexible Schedule. Benefits: list as above. Check for any other specifics: "Shift Meal Discount and Family Dining Discount*" we kept. Now ensure we didn't include any boilerplate like "SONIC is an equal opportunity employer." Removed. Check for any leftover duplicated lines: we removed the second "Feelin’ these good vibes?" line. Also removed "Cherry Limeade-lover or