Team Member 39503

We need to output HTML fragment with sections only if content exists. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting. Content: - Who We Are: description of Ayvaz Pizza, hiring Team Members, responsibilities. Could be "About the role" or maybe "Who We Are". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings as appropriate. We need to decide which sections have real content. Let's extract: About the role: Could be "Who We Are" description: 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. That's about the role. Responsibilities: The list under "Here-s What You Will Be Doing". Many bullet-like sentences. We'll put them in

• . Requirements: Possibly "Who You Are": Personable, Results-oriented self-starter, a go-getter. Team contributor and leader who thrives in a fast-paced setting. That's more like qualifications/skills. Could be "Qualifications". But we have separate headings: Requirements, Qualifications, Skills. We need to decide. The posting includes: "HERE-S WHAT Skills - Knowledge YOU WILL NEED" then list: 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. That's skills/knowledge. Also "SOME Perks - Benefits (Based on eligibility requirements:)" then list of benefits: discount program, provider finder/cost estimation tool, wellness program, pregnancy planning tool, receive GED credentials at no cost, tuition assistance, receive daily pay - on-demand pay allows employees to access their pay on schedule, etc. Also mention: The Company reserves the right to conduct a background check... We are an equal opportunity employer. Location: address. We should not include boilerplate like EEO, equal opportunity, background check maybe? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop the equal opportunity employer line and background check maybe considered legal? It says "The Company reserves the right to conduct a background check of its employees, and your employment may be conditioned on satisfactory results." That's somewhat legal boilerplate; maybe we should drop it. Also location maybe we keep as part of About the role? Could be a short p. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep location. We need to avoid sections with filler like "commensurate with experience". Not present. We need to include Pay/Schedule/Benefits sections only if posting actually states them. Benefits are stated (list). Pay: mention "Receive Daily Pay - On-demand pay allows employees to access their pay on their schedule." That's about pay. So we can include a Pay section with that detail. Schedule: Not explicitly stated besides flexible work availability; maybe not specific schedule. The posting does not give specific schedule like full-time/part-time, shift times. So we should not create a Schedule section unless there is real specific content. "Flexible work availability" is more about availability, not schedule. So we skip Schedule. Now we need to decide headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also "Qualifications" vs "Requirements". The posting has "Who You Are" (personable, results-oriented self-starter...). That could be Qualifications. The "HERE-S WHAT Skills - Knowledge YOU WILL NEED" is Skills. The "Minimum age..." etc could be Requirements. Let's map: - Requirements: Minimum age of 16 years, 18 years old to work opening and closing shifts, possess all documents and permits required by state - federal law, reliable transportation, flexible work availability, results oriented and customer focused, previous customer service work experience helpful. Also maybe dependable and reliable? That's more skill. But we need to avoid duplication. Let's parse the "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. - 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 that list includes many items that could be considered requirements. The earlier "Who You Are" list: Personable, Results-oriented self-starter, a go-getter. Team contributor and leader who thrives in a fast-paced setting. Thus we could have: - About the role (description) - Responsibilities (list of duties) - Qualifications (personal attributes: Personable, Results-oriented self-starter, go-getter, Team contributor and leader who thrives in fast-paced setting) - Skills (the list from HERE-S WHAT Skills - Knowledge YOU WILL NEED) - Benefits (list) - Pay (daily pay on-demand) - Possibly Requirements could be merged into Skills or Qualifications. But we have both headings; we need to avoid thin sections. Maybe we combine Requirements into Skills or Qualifications. However the instruction: Prefer a few substantive sections over many thin ones. So we should not create many sections with little content. Let's see how much content each would have. If we make Qualifications: Personable, Results-oriented self-starter, a go-getter. Team contributor and leader who thrives in a fast-paced setting. That's 4 bullet points. Skills: The list of 10 items. Requirements: Could be empty if we incorporate into Skills. But we need to decide if we need a Requirements heading. The posting does not have a separate "Requirements" label; it's all under Skills-Knowledge. So we could skip Requirements heading. Thus sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. Check if any content for Benefits: yes list. Pay: yes. Schedule: none. Now we need to format. We need to use

  for each section heading. Inside each section, we need

  for prose,

  • for lists. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract exact phrasing. About the role: We'll combine the paragraphs: "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 keep punctuation as is? Slight grammar issues but we keep. Responsibilities: The list under "Here-s What You Will Be Doing". Let's extract each bullet: - 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. Note some have trailing periods, some not. We'll keep as is. Qualifications: "Who You Are Personable, Results-oriented self-starter, a go-getter.Team contributor and leader who thrives in a fast-paced setting." We need to split into list items maybe: Personable; Results-oriented self-starter; a go-getter; Team contributor and leader who thrives in a fast-paced setting. We'll make
    • each. Skills: The list from "HERE-S WHAT Skills - Knowledge YOU WILL NEED". Let's extract each: - The ability to work well in a 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 We'll keep as list items. Benefits: "SOME Perks - Benefits (Based on eligibility requirements:) 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 visitA wellness program, where earning points for things like achieve step goals, can be redeemed to purchase wellness related itemsA 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." We need to split into list items. The text runs together without spaces after periods. We need to parse manually. Let's separate: - 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 one overlaps with Pay section; but we already have Pay section for daily pay. However the benefit list includes daily pay as a perk. We might want to avoid duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we separate Pay section, we might duplicate the daily pay info. But