Team Member 39363

We need to output HTML fragment with sections using

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, equal opportunity, etc. Also remove application instructions (none). Keep substantive info. Let's parse the posting. Who We Are: description of company and role. Could be "About the role" or "Who We Are". The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map sections accordingly. We have: - Who We Are: description of Ayvaz Pizza, hiring Team Members, responsibilities: assisting daily operations, ensuring friendly personalized service, etc. Could be "About the role" or maybe "Who We Are". But we need to use headings from list; we can choose "About the role" for that. - Who You Are: Personable, Results-oriented self-starter, go-getter, team contributor and leader who thrives in fast-paced setting. That's like "Qualifications" or "Skills"? Could be "Qualifications". We'll decide. - Here-s What You Will Be Doing: list of duties. That's "Responsibilities". - HERE-S WHAT Skills - Knowledge YOU WILL NEED: list of abilities: ability to work fast-paced, dependable, good written, math and interpersonal skills, reliable transportation, minimum age 16, 18 to work opening/closing shifts, possess documents, flexible availability, results oriented, previous customer service experience helpful. That's "Skills" or "Requirements". We'll map to "Skills". - SOME Perks - Benefits (Based on eligibility requirements:) list: 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). Also mention background check, equal opportunity employer (boilerplate to remove). So we have Benefits section. - Pay: The posting mentions "Receive Daily Pay - On-demand pay allows employees to access their pay on their schedule." That's pay info. So we can have a Pay section. - Schedule: Not explicitly mentioned besides flexible work availability, but not specific schedule. No explicit schedule details like full-time/part-time, shift times. So we should not create Schedule section unless posting actually states them. It mentions flexible work availability, but not specific schedule. Probably we should not create Schedule section because it's not specific. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Benefits we have content. For Pay we have content (daily pay). For Schedule we don't have explicit schedule; we have flexible work availability but not a schedule description. Might be considered not specific enough. Safer to omit Schedule. - Requirements: Could be separate from Skills. The posting includes minimum age, reliable transportation, documents, etc. Those could be Requirements. But we already used Skills for abilities. We could split: Requirements: minimum age, reliable transportation, documents, flexible availability. Skills: ability to work fast-paced, dependable, good written math interpersonal, results oriented, customer focus, previous experience helpful. However the instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Skills into one section? But we have headings list; we can choose to include both if they have substantive content. However we need to avoid thin sections. Let's see if we can make two substantive sections: Responsibilities (substantial), Requirements/Qualifications (substantial), Benefits (substantial), Pay (substantial). That's four sections. That's okay. We need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (who we are). Responsibilities (list). Requirements (minimum age, transportation, documents, flexible availability). Qualifications maybe similar to Skills? Could combine Requirements and Qualifications? But we have both headings; we could use Requirements for the hard requirements (age, transport, docs, availability) and Skills for the soft skills. That seems reasonable. Benefits: we have list. Pay: we have daily pay. We should not include Schedule. Now we need to format lists using

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

  for prose. We must preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include boilerplate like EEO, equal opportunity, background check? The background check line: "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 boilerplate but maybe considered legal? It's not EEO but still maybe considered boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Background check could be considered legal boilerplate. Safer to remove it. Also "We are an equal opportunity employer." Remove. Also "Location: 2135 Cliff Rd, Eagan, Minnesota 55122" is substantive? It's location info. Should we keep? It's not a heading but we can include as a short

  maybe under About the role or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Location is minor metadata; we can include as a short

  maybe after About the role. We need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

  About the role

  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 results 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.

  Location: 2135 Cliff Rd, Eagan, Minnesota 55122

  Responsibilities

  • 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.

  Requirements

  • Minimum age of 16 years; 18 years old to work opening and closing shifts.
  • Reliable transportation.
  • Possess all documents and permits required by state and federal law.
  • Flexible work availability.

  Skills

  • Ability to work well in a fast-paced environment and under pressure.
  • Dependable and reliable.
  • Good written, math and interpersonal skills.
  • Results oriented and customer focused.
  • Previous customer service work experience helpful.

  Benefits

  • 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.

  Pay

  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.

  But note we already included Daily Pay in Benefits list; we might duplicate. The Benefits section includes that line. The Pay section could be separate but we might not need both. The instruction: Prefer a few substantive sections over many thin ones. Having both Benefits and Pay with overlapping content may be thin. Better to keep Pay separate only if we have distinct pay info not already in Benefits. The Benefits list includes "Receive Daily Pay - On-demand pay..." which is essentially pay info. So we could either move that to Pay section and remove from Benefits, or keep Benefits without that line and have Pay section. Let's decide: Keep Benefits without the daily pay line, and have Pay section for that detail. That avoids duplication. Thus adjust Benefits list to exclude the daily pay line. Benefits list: - discount program... - provider finder/cost estimation tool... - wellness program... - pregnancy planning tool... - Receive your GED credentials at no cost to you. - Tuition Assistance. We invest in YOU by Empowerment and Building Confidence for your future. Pay section: the daily pay description. Now ensure we haven't missed any substantive info: The posting also mentions "The Company reserves the right to conduct a background check of its employees, and your employment may be conditioned on satisfactory results." We removed as boilerplate. Also "We are an equal opportunity employer." removed. Check for any other info: "Here-s What You Will Be Doing As an integral member of the Operations Team, this position is responsible for:" we captured responsibilities. "Here-s What Skills - Knowledge YOU WILL NEED" we captured skills. "SOME Perks - Benefits (Based on eligibility requirements:)" we captured benefits. Now ensure we didn't miss any responsibility like "Works with management to resolve issues that may arise in the restaurant." included. Check for any other: "Learns team effectiveness skills; works with others to achieve team goals." included. Now ensure we didn't include any filler like "commensurate with experience" etc. Not present. Now output HTML fragment. Make sure to use proper apostrophes: we have some hyphens and apostrophes in original text like "Here-s". We should keep as is? Probably keep original wording but we can correct typographically? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Changing "Here-s" to "Here's" could be considered altering detail? It's minor but could be considered inventing? Safer to keep as given. However the text includes "Here-s" and "HERE-S". We'll keep them exactly as in source. But we used "Friendly demeanor. Greets guests with