Team Member 40100
or drop it." Location is minor metadata; we could include in a short
maybe under About the role? Or we could drop it. Probably include as a short paragraph after About the role. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: we have description of role: assisting with daily operations, ensuring friendly service, etc. That's substantive. So we can put that in About the role. - Responsibilities: the list of duties (the bullet list). That's substantive. - Requirements: maybe the "Who You Are" part: Personable, Results-oriented self-starter, etc. Also maybe "Minimum age of 16 years 18 years old to work opening and closing shifts" etc. That could be Requirements. - Qualifications: maybe "Good written, math and interpersonal skills. Reliable transportation. Possess all documents and permits required by state - federal law. Flexible work availability. Results oriented and customer focused. Previous customer service work experience helpful." Could be Qualifications. - Skills: The "Skills - Knowledge YOU WILL NEED" list: ability to work well in fast-paced environment, dependable, reliable, good written, math and interpersonal skills, reliable transportation, minimum age, etc. Actually overlapping with qualifications. But we need to avoid duplication. The instruction: preserve ALL substantive information; do not invent or summarize away detail. We need to keep all info but can organize into sections; duplication may be okay if it's in original? But we should not repeat same content unnecessarily? Not explicitly forbidden, but we should aim to avoid filler. Might be okay to have overlapping but better to split logically. Let's map: Original sections: - Who We Are (description) -> About the role. - Who You Are (personable, results-oriented self-starter, team contributor, leader, fast-paced) -> maybe Requirements or Qualifications. - Here-s What You Will Be Doing (list) -> Responsibilities. - HERE-S WHAT Skills - Knowledge YOU WILL NEED (list) -> Skills. - SOME Perks - Benefits (Based on eligibility requirements:) (list) -> Benefits. - Receive Daily Pay - On-demand pay ... -> Pay. - Schedule? Not explicitly mentioned. There's "Flexible work availability" but that's not schedule specifics. No explicit schedule like shifts, hours. So we should NOT create a Schedule section because no specific content. - Qualifications? Could be the "Minimum age of 16 years 18 years old to work opening and closing shifts Possess all documents and permits required by state - federal law Flexible work availability Results oriented and customer focused Previous customer service work experience helpful". That could be Qualifications. But we also have "Who You Are" which is more about personal traits. Could be Qualifications as well. We need to avoid thin sections. Let's decide: About the role: paragraph describing role. Responsibilities: ul list of duties. Requirements: maybe the "Who You Are" traits (personable, results-oriented self-starter, team contributor and leader who thrives in a fast-paced setting). Also maybe "Dependable and reliable" etc? Actually those are in Skills list. Let's see. Skills list includes: ability to work well in fast-paced environment and under pressure, Dependable and reliable, Good written, math and interpersonal skills, Reliable transportation, Minimum age of 16 years 18 years old to work opening and closing shifts, Possess all documents and permits required by state - federal law, Flexible work availability, Results oriented and customer focused, Previous customer service work experience helpful. Thus Skills list already covers many. So we could treat Skills as that list. Qualifications maybe empty? But we need to avoid empty headings. So we could omit Qualifications if no distinct content beyond what's covered. Requirements maybe the "Who You Are" traits. Let's extract "Who You Are": "Personable, Results-oriented self-starter, a go-getter.Team contributor and leader who thrives in a fast-paced setting." That's a short sentence. We could also include "Self-motivated, dynamic team player" from earlier? Actually earlier: "We are looking for a self-motivated, dynamic team player to join our team!" That's part of Who We Are? It's after "We are looking for a self-motivated, dynamic team player to join our team!" That could be part of About the role or Requirements. But we already used About the role for description; we could incorporate that trait there. Better: About the role includes the hiring statement and description. We'll keep that. Requirements: "Personable, Results-oriented self-starter, a go-getter. Team contributor and leader who thrives in a fast-paced setting." Now Skills: the list from "HERE-S WHAT Skills - Knowledge YOU WILL NEED". We'll output as ul. Benefits: the list from "SOME Perks - Benefits (Based on eligibility requirements:)". We'll output as ul. Pay: the paragraph about Receive Daily Pay - On-demand pay ... We'll output as p. Schedule: none, so omit. Now we need to ensure we don't include boilerplate: "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 condition; could be considered part of Requirements? It's a condition of employment. Could be included in Requirements or maybe a separate note. But it's not a heading; we could fold into Requirements as a short p. However it's not a list; we could add a p after Requirements. Also "We are an equal opportunity employer." Remove. Location: we could drop or include as a p under About the role. Probably drop as minor metadata. Now we need to output only HTML fragment, no html/body tags, no markdown. Structure:
About the role
...
Responsibilities
- ... ...
Requirements
...
... maybe background check note
Skills
- ... ...
Benefits
- ... ...
Pay
...
Make sure to preserve all substantive information. Let's extract each piece precisely. About the role text: Original: "Who We Are Ayvaz Pizza (Franchisee of Pizza Hut) is hiring Team Members who will be responsible for assisting with the daily operations of the restaurant. The Team Member 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 Team Member 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 need to preserve all that. We'll combine into a paragraph. Responsibilities list items (as given): - Friendly demeanor. Greets guests with a smile, receives orders, processes payments, and responds appropriately to customer issues. - Operates cash register or point of sale devices, as needed, and uses value-added suggestive-selling techniques to generate additional sales opportunities. - Communicates in a positive manner with customers, peers, and managers - Verifies the accuracy of guests- orders. - Prepares and packages food and drink products. - Cleans kitchen area, counters, food preparation areas and utensils. - Cleans dining room, restrooms, and exterior grounds. - Maintains Health and Safety standards in work areas. - Unloads and stocks inventory items as needed. - Performs duties at multiple workstations - Prompt and regular attendance on assigned shifts. - Follows uniform and grooming standards and policies. - Works with management to resolve issues that may arise in the restaurant. - Learns team effectiveness skills; works with others to achieve team goals. We need to keep punctuation as is. Requirements: "Personable, Results-oriented self-starter, a go