Shift Manager 39423
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting.
Content:
- Who We Are: description of company and role. Could be "About the role" or maybe "About the role" includes description. The posting includes "Who We Are Ayvaz Pizza (Franchisee of Pizza Hut) is hiring Restaurant Shift Manager, who will be responsible for assisting with the daily operations of the restaurant. The Shift Manager assists with ensuring that each visit by a customer result in a friendly and personalized service with great food that is promptly delivered in a clean and inviting environment. We are looking for a self-motivated, dynamic team player to join our team! The Shift Manager position is responsible for providing exceptional guest service and support, while working closely with the Restaurant Managers and other Team Members to maintain operational standards and procedures."
That's about the role. So we can put that under About the role
with
. - Who You Are: Personable, Results-oriented self-starter, a go-getter. That's maybe "Qualifications" or "Skills"? Could be "Qualifications". But we have separate sections: Requirements, Qualifications, Skills. We need to decide. The posting includes "Here-s What You Will Be Doing" list: Training and supervising crew members; Monitoring and reinforcing food safety standards and procedures; Interacting with our customers in a friendly, polite and professional manner; Executing cost control systems; Delegation of prepping and cleaning assignments as needed throughout the shift. That's responsibilities. Then "HERE-S WHAT Skills - Knowledge YOU WILL NEED": list: The ability to work well in a fast-paced environment and under pressure.; Dependable and reliable.; Good written, math and interpersonal skills.; Reliable transportation.; 18 years old to work in manager role.; Possess all documents and permits required by state - federal law; Flexible work availability; Results oriented and customer focused; Previous customer service work experience helpful; Undergo background screening in accordance with local laws and regulations. That's requirements/qualifications/skills. We need to map. We have "SOME Perks - Benefits (Based on eligibility requirements:)": list of benefits: discount program; provider finder/cost estimation tool; wellness program; pregnancy planning tool; Receive your GED credentials at no cost; Tuition Assistance; Receive Daily Pay - On-demand pay allows employees to access their pay on their schedule; The Company reserves the right to conduct a background check... (that's not a benefit). Also "We are an equal opportunity employer" is boilerplate to remove. Location: address. We need to decide sections: - About the role: description. - Responsibilities: list of duties. - Requirements: maybe combine qualifications and skills? Could have separate sections: Requirements (like age, documents, transportation, background check) and Skills (fast-paced, dependable, etc). But we need to avoid thin sections. Perhaps combine into one "Requirements" section that includes both skills and qualifications. However the instruction says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content. We have content for About the role, Responsibilities, Benefits (specific list). For Requirements/Qualifications/Skills we have content but could split. We need to decide if we should create multiple sections or combine. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections. Perhaps combine Requirements, Qualifications, Skills into one section called "Requirements" (or "Qualifications") that includes all the needed attributes. But we need to use heading exactly as given: we can choose which heading to use. If we combine, we should pick one heading that best fits. Could use "Requirements" as heading and include all the needed attributes (skills, qualifications, etc). That would be substantive. Alternatively we could have "Skills" heading for the list of skills, and "Requirements" for age, documents, transportation, background check. But that would be two sections, each maybe thin but still substantive. Let's see content: Skills list: ability to work well in fast-paced environment and under pressure; dependable and reliable; good written, math and interpersonal skills; reliable transportation; results oriented and customer focused; previous customer service work experience helpful. Requirements list: 18 years old to work in manager role; possess all documents and permits required by state-federal law; flexible work availability; undergo background screening. We could split: Skills section for the first list; Requirements section for the latter. That seems reasonable and each section has multiple items. Benefits: we have list of specific benefits. Pay: we have "Receive Daily Pay - On-demand pay allows employees to access their pay on their schedule. They can track every shift worked and every penny earned, and they can cash out to use that pay whenever they want." That's about pay. So we have specific pay info: on-demand pay. So we should include Pay section. Schedule: not mentioned explicitly; there is flexible work availability but that's more requirement. No explicit schedule details (like full-time, part-time, shifts). So we should not create Schedule section because no specific content. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We must not repeat job title as heading. Good. We need to output only HTML fragment, no /. Use
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "We are an equal opportunity employer". Also remove "The Company reserves the right to conduct a background check of its employees, and your employment may be conditioned on satisfactory results." That's maybe not boilerplate but it's a statement about background check; could be considered part of requirements? It mentions background check already in requirements. Might be considered redundant. We'll keep background check mention under Requirements (we already have). The sentence about company reserves right to conduct background check is maybe boilerplate but it's specific to background check; we can keep it as part of requirements but it's not a list item. Could be included in a paragraph.
We also need to remove duplicated lines. Not seeing duplicates.
Now craft content.
About the role paragraph: combine the description.
Let's extract:
"Ayvaz Pizza (Franchisee of Pizza Hut) is hiring Restaurant Shift Manager, who will be responsible for assisting with the daily operations of the restaurant. The Shift Manager assists with ensuring that each visit by a customer result in a friendly and personalized service with great food that is promptly delivered in a clean and inviting environment. We are looking for a self-motivated, dynamic team player to join our team! The Shift Manager position is responsible for providing exceptional guest service and support, while working closely with the Restaurant Managers and other Team Members to maintain operational standards and procedures."
We'll put that in
.
Responsibilities list:
- Training and supervising crew members
- Monitoring and reinforcing food safety standards and procedures
- Interacting with our customers in a friendly, polite and professional manner
- Executing cost control systems
- Delegation of prepping and cleaning assignments as needed throughout the shift
We'll put each as
- .
Requirements list (age, documents, flexible availability, background check). Also maybe "Possess all documents and permits required by state - federal law". Also "Undergo background screening in accordance with local laws and regulations". Also "Flexible work availability". Also "18 years old to work in manager role."
We'll put as
- .
Skills list:
- The ability to work well in a fast-paced environment and under pressure.
- Dependable and reliable.
- Good written, math and interpersonal skills.
- Reliable transportation.
- Results oriented and customer focused.
- Previous customer service work experience helpful.
We'll put as
- .
Benefits list:
- A discount program that has discounts on things like glasses, hearing aids, weight loss programs, step tracking devices, shoes, etc.
- A provider finder/cost estimation tool, allowing members to find in-network providers and get a cost estimation before the visit
- A wellness program, where earning points for things like achieve step goals, can be redeemed to purchase wellness related items
- A pregnancy planning tool, that helps track fertility, baby growth, milestones, etc.
- Receive your GED credentials at no cost to you.
- Tuition Assistance. We invest in YOU by Empowerment and Building Confidence for your future.
- Receive Daily Pay - On-demand pay allows employees to access their pay on their schedule. They can track every shift worked and every penny earned, and they can cash out to use that pay whenever they want.
Note: The last bullet about Daily Pay overlaps with Pay section; we might want to separate Pay info from Benefits. The benefit list includes Daily Pay as a perk. But we also have a Pay section for on-demand pay. To avoid duplication, we could keep Daily Pay under Pay section and not duplicate in Benefits. However the benefit list includes it as a perk. The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we remove it from Benefits, we are omitting that detail. But we could include it in both sections? That would be duplication. Better to keep it under Pay section and maybe not list it under Benefits, but then we lose the benefit description as part of benefits. However the benefit list includes it as a perk; we could keep it under Benefits but also have Pay section referencing same info? That would be duplication. The instruction says remove duplicated lines. So we should not duplicate the same content. We need to decide where to place it. The benefit list includes many items; the Daily Pay is a specific pay-related benefit. Since we have a Pay section, we could put the Daily Pay description there, and not include it under Benefits. That would avoid duplication and still preserve the info (just moved). The benefit list would then lose that item, but the info is still present elsewhere. Is that acceptable? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Moving it is not inventing or summarizing away; it's still present. So okay.
Thus Benefits list will exclude the Daily Pay item.
Now Pay section: we need to describe on-demand pay. The description: "Receive Daily Pay - On-demand pay allows employees to access their pay on their schedule. They can track every shift worked and every penny earned, and they can cash out to use that pay whenever they want." We'll put that in
.
We might also mention that the company reserves right to conduct background check; but we already have background check in Requirements. Could keep that statement as a sentence in Requirements paragraph? But we already have list items. Could add a
after list: "The Company reserves the right to conduct a background check of its employees, and your employment may be conditioned on satisfactory results." That's not a list item but substantive. We'll include as a
under Requirements.
Now location: The posting includes location at end. Should we include location? The instruction: we can include minor metadata like location in a short
or drop it. It's not a heading. We could add a
at the end with location. But we need to decide if we should include location as part of About the role or separate. Since it's minor metadata, we can include a short
at the end. Not a heading.
Now ensure we don't include any boilerplate: equal opportunity employer, etc.
Now produce HTML.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
The Company reserves the right to conduct a background check of its employees, and your employment may be conditioned on satisfactory results.
for prose. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "We are an equal opportunity employer". Also remove "The Company reserves the right to conduct a background check of its employees, and your employment may be conditioned on satisfactory results." That's maybe not boilerplate but it's a statement about background check; could be considered part of requirements? It mentions background check already in requirements. Might be considered redundant. We'll keep background check mention under Requirements (we already have). The sentence about company reserves right to conduct background check is maybe boilerplate but it's specific to background check; we can keep it as part of requirements but it's not a list item. Could be included in a paragraph. We also need to remove duplicated lines. Not seeing duplicates. Now craft content. About the role paragraph: combine the description. Let's extract: "Ayvaz Pizza (Franchisee of Pizza Hut) is hiring Restaurant Shift Manager, who will be responsible for assisting with the daily operations of the restaurant. The Shift Manager assists with ensuring that each visit by a customer result in a friendly and personalized service with great food that is promptly delivered in a clean and inviting environment. We are looking for a self-motivated, dynamic team player to join our team! The Shift Manager position is responsible for providing exceptional guest service and support, while working closely with the Restaurant Managers and other Team Members to maintain operational standards and procedures." We'll put that in
. Responsibilities list: - Training and supervising crew members - Monitoring and reinforcing food safety standards and procedures - Interacting with our customers in a friendly, polite and professional manner - Executing cost control systems - Delegation of prepping and cleaning assignments as needed throughout the shift We'll put each as
. We might also mention that the company reserves right to conduct background check; but we already have background check in Requirements. Could keep that statement as a sentence in Requirements paragraph? But we already have list items. Could add a
after list: "The Company reserves the right to conduct a background check of its employees, and your employment may be conditioned on satisfactory results." That's not a list item but substantive. We'll include as a
under Requirements. Now location: The posting includes location at end. Should we include location? The instruction: we can include minor metadata like location in a short
or drop it. It's not a heading. We could add a
at the end with location. But we need to decide if we should include location as part of About the role or separate. Since it's minor metadata, we can include a short
at the end. Not a heading. Now ensure we don't include any boilerplate: equal opportunity employer, etc. Now produce HTML. Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
The Company reserves the right to conduct a background check of its employees, and your employment may be conditioned on satisfactory results.