Team Member 39478

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No metadata like Job ID. Remove boilerplate: EEO, equal opportunity, scam warning, navigation, cookie, legal, duplicated lines, application instructions. Also remove "We are an equal opportunity employer." etc. We need to parse the posting: - Who We Are: description of company and role. Could be "About the role" maybe. The posting includes "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. So we can put that in with heading

About the role

and paragraphs. - 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"? Could be "Qualifications". We'll treat as "Qualifications". - Here-s What You Will Be Doing: list of duties. That's responsibilities. So we need a

• list. - HERE-S WHAT Skills - Knowledge YOU WILL NEED: list of skills/knowledge. That's "Skills". So we need a
  • list. - SOME Perks - Benefits (Based on eligibility requirements:): list of benefits. That's "Benefits". So we need a
    • list. - Pay: Not mentioned explicitly. There's "Receive Daily Pay - On-demand pay allows employees to access their pay on their schedule." That's about pay frequency. Could be considered Pay section. The posting mentions "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 can include a Pay section with that description. - Schedule: Not explicitly mentioned. There's "Flexible work availability" but not schedule specifics. No explicit schedule like full-time/part-time, shift times. So we should not create Schedule section unless posting actually states them. It says "Flexible work availability" but that's not a schedule detail. Probably we should not include Schedule. - Also there is mention of minimum age, transportation, etc. Those could be Requirements. We'll put those under Requirements. We need to preserve all substantive information, not invent or summarize away detail. So we need to include each bullet point exactly as given (maybe rephrase slightly but preserve meaning). Must not invent. Let's extract details: About the role paragraph(s): - "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 can combine into one or multiple

      . Probably one paragraph is fine. Who You Are (Qualifications): - "Personable, Results-oriented self-starter, a go-getter." - "Team contributor and leader who thrives in a fast-paced setting." We could put as

      or

      . Since it's a list of traits, could be
      . But the instruction: Use
      • for any list of duties/requirements/benefits, and

        for prose. These are qualifications, maybe treat as list? Could be either. Safer to use

        for prose. But we have two short phrases; could be a sentence: "Personable, results-oriented self-starter, a go-getter; team contributor and leader who thrives in a fast-paced setting." That is prose. Responsibilities (Here-s What You Will Be Doing): List items: - 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 preserve punctuation and hyphens etc. Some have weird hyphens like "guests- orders". We'll keep as is. 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 Note: Some items are duplicated? Minimum age and 18 years old for opening/closing shifts. We'll keep both. 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 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 benefit also mentions Daily Pay; but we also have a Pay section. Might duplicate. However the instruction: include a section ONLY when posting has real specific content for it. Pay is mentioned in benefits as "Receive Daily Pay - On-demand pay...". That's about pay. So we could either put that under Benefits or Pay. Since we already have a Benefits section, we could keep that benefit there and not create a separate Pay section. But the instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Pay (Daily Pay). So we could create a Pay section with that detail. However then we would duplicate the same content if we also keep it under Benefits. To avoid duplication, we could move the Daily Pay detail to Pay section and remove from Benefits. But we must preserve ALL substantive information; we can't remove it. We could keep it in both places? That would be duplication, which might be considered repeating detail but not inventing. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but we should avoid unnecessary duplication? Not explicitly forbidden. However better to not duplicate; we can place Daily Pay under Pay and keep other benefits under Benefits. That way we preserve all info without duplication. Thus Benefits list will exclude the Daily Pay item. Pay section: "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." Schedule: Not present; we will not include. Now we need to output HTML fragment: sections with

        headings and content. We'll structure like:

        About the role

        ...

        Qualifications

        ...

        Responsibilities

        • ...
        ...

        Skills

        • ...
        ...

        Benefits

        • ...
        ...

        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.

        We must not include any extra markup like or . Also no markdown fences. Check for any boilerplate removal: We removed "We are an equal opportunity employer." and "The Company reserves the right to conduct a background check..." and location? Location is substantive? It's location: "Location: 4821 San Bernardo, Laredo, Texas 78040". Should we keep? It's substantive info. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it. Location is minor metadata? Could be considered minor metadata but it's substantive location. Might keep as a short

        maybe under About the role or separate? The instruction says fold minor metadata into a short

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

        after About the role. But we already have About the role paragraph; we could append location as another

        . However we must preserve ALL substantive information; location is substantive. So we should include it. We'll add a

        with the location. Also there is "We are an equal opportunity employer." That's EEO boilerplate; 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 boilerplate; remove. Now check for any duplicated lines: None. Now ensure we didn't include any headings with empty content. Now produce final HTML. Let's craft the About the role paragraph(s): We could combine into one paragraph: "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." Then location paragraph: "Location: 4821 San Bernardo, Laredo, Texas 78040" Qualifications paragraph: "Personable, results-oriented self-starter, a go-getter; team