Team Member 40092

We need to output HTML fragment with sections: About the role? The posting includes "Who We Are", "Who You Are", "Here-s What You Will Be Doing", "HERE-S WHAT Skills - Knowledge YOU WILL NEED", "SOME Perks - Benefits". We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each section heading. Only include sections with real content. No Pay or Schedule unless present. The posting does not mention pay or schedule specifics. So omit Pay and Schedule sections. We need to include

for prose,

• for any list of duties/requirements/benefits. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, equal-opportunity, scam-warning, cookie/navigation/legal, duplicated lines, application instructions. Also remove "The Company reserves the right to conduct a background check..." maybe that's not boilerplate? It's a statement about background check; could be considered substantive? It's not a list; it's a statement. Might keep as prose. However "We are an equal opportunity employer." is boilerplate EEO; remove. Also "Location: 222 W Aztec Blvd, Aztec, New Mexico 87410" is metadata; we can fold into short

  maybe. We need to avoid repeating job title as heading. Not needed. We need to include sections: About the role (maybe from "Who We Are" and description). Responsibilities (list of duties). Requirements (maybe age, transportation, documents). Qualifications (maybe skills). Skills (maybe list). Benefits (list of perks). Ensure not to duplicate. Let's parse content: 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. That's about the role. Who You Are: Personable, Results-oriented self-starter, a go-getter. Team contributor and leader who thrives in a fast-paced setting. That's maybe qualifications or skills. Here-s What You Will Be Doing: list of duties. HERE-S WHAT Skills - Knowledge YOU WILL NEED: list of skills/requirements. SOME Perks - Benefits (Based on eligibility requirements:): list of benefits. Also mention: Receive Daily Pay - On-demand pay allows employees to access their pay on their schedule... That's about pay and schedule? It mentions daily pay, on-demand pay. That is pay info. So we should include Pay section? The rule: include Pay section only if posting actually states them. It does state "Receive Daily Pay - On-demand pay allows employees to access their pay on their schedule." That's pay info. Also mentions schedule? It says "on their schedule". Not explicit schedule like shifts. But we have pay info. So we should include a Pay section with that content. Also schedule? Not explicit shift times. So omit Schedule. Now we need to avoid duplication: The "Receive Daily Pay" appears also maybe in benefits? It's under perks? Actually it's listed under "SOME Perks - Benefits (Based on eligibility requirements:)". It appears after list of perks? Let's see: The text: "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." Thus Daily Pay is part of benefits/perks. So we could include it in Benefits section. But we also have a Pay section maybe redundant. The rule: Prefer a few substantive sections over many thin ones. So we could combine pay info into Benefits section, as it's a benefit. However they said include Pay section only if posting actually states them. It does state pay info, but we could still put it under Benefits. But they said "Prefer a few substantive sections over many thin ones." So better to not create a separate Pay section if we can incorporate into Benefits. However they also said "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if we create Pay section, we need to put the pay content there. That's specific. But we could also put it under Benefits. Which is better? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect those headings. They say "Prefer a few substantive sections over many thin ones." So we should include only those sections that have content. If we have pay content, we could include Pay section. But we also have benefits content. Could we combine Pay and Benefits into one Benefits section? The heading list includes both Benefits and Pay as separate options. But we can choose to not include Pay if we incorporate its content into Benefits. However they said "Prefer a few substantive sections over many thin ones." So if we can avoid a thin Pay section by merging, that's preferable. But we need to ensure we don't lose any info. The pay info is specific: "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 a benefit. So we can include it under Benefits. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly also "Who You Are" could be Qualifications or Skills. Let's map: - About the role: from Who We Are paragraph(s). - Responsibilities: list from "Here-s What You Will Be Doing". - Requirements: maybe age, transportation, documents, reliable transportation, minimum age, etc. Also "Possess all documents and permits required by state - federal law". Also "Flexible work availability". Also "Previous customer service work experience helpful" maybe qualification. - Qualifications: maybe "Personable, Results-oriented self-starter, a go-getter. Team contributor and leader who thrives in a fast-paced setting." Could be Qualifications. - Skills: list from "HERE-S WHAT Skills - Knowledge YOU WILL NEED": 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. Some of these overlap with requirements. We need to avoid duplication but preserve all info. Could combine requirements and qualifications and skills into one? But headings distinct. We need to decide. We could treat: - Requirements: minimum age, transportation, documents, flexible availability. - Qualifications: personable, results-oriented self-starter, team contributor, leader, thrives in fast-paced. - Skills: ability to work well in 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. But there is overlap: "results oriented and customer focused" appears both in skills and qualifications? Actually qualifications had "Results-oriented self-starter". Skills includes "results oriented and customer focused". Slightly different. We need to preserve all info, not invent. Duplication is okay? The instruction: "Remove duplicated lines". So we should avoid repeating same exact line. But similar but not identical lines may be okay. However we should try to avoid redundancy. Let's extract exact lines: From "Who You Are": "Personable, Results-oriented self-starter, a go-getter. Team contributor and leader who thrives in a fast-paced setting." From "HERE-S WHAT Skills - Knowledge YOU WILL NEED": - 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 Also earlier: "We are looking for a self-motivated, dynamic team player to join our team!" That's in Who We Are. Now we need to decide sections. Option: About the role (Who We Are + maybe the self-motivated line). Responsibilities (list). Requirements (age, transportation, documents, flexible availability). Qualifications (personable, results-oriented self-starter, team contributor, leader, thrives in fast-paced, self-motivated, dynamic team player). Skills (ability to work well in fast-paced environment under pressure, dependable and reliable, good written, math and interpersonal skills, results oriented and customer focused, previous customer service work experience helpful). Benefits (list of perks including daily pay). Also maybe include location as a short p. We must not repeat job title as heading. Not needed. Now we need to output HTML fragment: use

  for each section heading,

  for prose,

  • for lists. We need to ensure we don't include boilerplate: EEO, equal-opportunity, scam-warning, cookie/navigation/legal, duplicated lines, application instructions. 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 could be considered a statement; it's not a list. Might keep as prose under About the role or maybe a separate note? It's not a heading; we could include as a paragraph under About the role or maybe under Requirements? It's about background check. It's substantive? It's a condition of employment. Could be included. However it's not explicitly a benefit or requirement. Might be considered a requirement? It's a condition. Could be placed under Requirements as a note. But it's not a typical requirement. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it. Where to put? Could be a short p under About the role or maybe under Requirements as a note. I'd put it under About the role as a separate paragraph after the description. Also "We are an equal opportunity employer." is boilerplate EEO; remove. Now let's craft. HTML:

    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. The Company reserves the right to conduct a background check of its