Team Member 39331

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

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. From posting: - Who We Are: description of company and role. Could be "About the role". We'll put that in

About the role

with paragraph(s). - Who You Are: personal attributes. Could be part of Requirements or Qualifications. We'll treat as Requirements. - Here-s What You Will Be Doing: list of duties. That's Responsibilities. - HERE-S WHAT Skills - Knowledge YOU WILL NEED: list of skills/knowledge. That's Skills. - SOME Perks - Benefits (Based on eligibility requirements:): list of benefits. That's Benefits. - No explicit Pay or Schedule info. There's mention of "Receive Daily Pay - On-demand pay allows employees to access their pay on their schedule." That's about pay schedule? It mentions daily pay, on-demand pay. That could be considered Pay info. Also schedule: "Flexible work availability". Not specific schedule. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. For Pay: we have mention of daily pay, on-demand pay. That's a statement about pay. So we can include Pay section with that content. For Schedule: we have "Flexible work availability". That's somewhat schedule info but vague. Might be considered schedule. However instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "Flexible work availability" is a statement about schedule, albeit vague but still states something. Could include Schedule section with that. But we need to decide if it's substantive enough. It says "Flexible work availability". That's a statement. Might be okay. But we also have "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 definitely pay info. Thus we can include Pay and Schedule sections. Benefits we have list. Now we need to avoid repeating job title as heading. Not needed. We need to remove boilerplate: EEO, equal opportunity, background check, etc. Also remove "We are an equal opportunity employer." and "The Company reserves the right to conduct a background check..." and location? Location maybe minor metadata; we can fold into short p or drop. 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 a short p at end maybe. We need to preserve all substantive information. So we need to keep the description of role, responsibilities, skills, benefits, pay, schedule, maybe location. We must not invent or summarize away detail. Keep details. We need to use

• for any list of duties/requirements/benefits. For prose use

  . We need to decide which content is list vs prose. Let's extract sections: About the role: "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 can put that as

  maybe multiple sentences. Requirements/Qualifications: "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 list of attributes. Could be

  • each. But also there are requirements like "Minimum age of 16 years18 years old to work opening and closing shifts" (typo). Also "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 "Reliable transportation". "Good written, math and interpersonal skills". "Dependable and reliable". "Ability to work well in a fast-paced environment and under pressure". Those are in Skills-Knowledge section. Thus we need to separate: Skills-Knowledge section includes ability to work fast-paced, dependable, good written math interpersonal skills, reliable transportation, minimum age, etc. Also "Results oriented and customer focused". "Previous customer service work experience helpful". So we can put those under Skills. Requirements maybe just the personal attributes: Personable, Results-oriented self-starter, a go-getter, Team contributor and leader who thrives in a fast-paced setting. Could be under Requirements. But we also have "Who You Are" which is personal attributes. We'll treat as Requirements. Responsibilities: list of duties from "Here-s What You Will Be Doing". We'll extract each bullet. Let's list them: - 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'll make each as
  • . Skills-Knowledge: list from "HERE-S WHAT Skills - Knowledge YOU WILL NEED". Let's extract: - 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 make each as
  • . Benefits: list from "SOME Perks - Benefits (Based on eligibility requirements:)". Extract: - 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 bullet includes pay info; but we already have Pay section. Might duplicate. However we could keep it in Benefits as it's a benefit. But we also need Pay section. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state pay info. So we can have Pay section with that detail. The benefit list also includes that; we could keep it there as part of benefits but might duplicate. To avoid duplication, we could keep the pay detail only in Pay section and not repeat in Benefits. However the benefit list includes that as a benefit; removing it would lose substantive info. But we could keep it in Benefits and also have Pay section referencing same? That would duplicate. Better to keep it in Benefits and not create separate Pay section unless there is additional pay info beyond that. The posting only mentions pay via that benefit. So we could treat that as Benefits only, and not create Pay section. However the instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay info (via benefit). So we could create Pay section with that info, but then we would be duplicating. The instruction didn't forbid duplication, but we should preserve all substantive information; duplication is okay but maybe not ideal. However we could avoid duplication by putting pay info only in Pay section and not in Benefits. But then we lose the benefit context (it's a benefit). However the benefit list includes many other items; we could keep them and move the pay line to Pay section, but then we would lose it from Benefits list. Could we keep it in both? It's not prohibited but might be considered redundant. I'd prefer to keep it in Benefits only and not create Pay section, because the pay info is presented as a benefit. The instruction says we can create Pay section only if posting actually states them. It does state them, but we could also choose not to create Pay section if we feel it's covered under Benefits. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine pay into Benefits and not have separate Pay section. That reduces number of sections. Similarly Schedule: we have "Flexible work availability" which is a schedule-related statement. Could be included under Benefits or Requirements? It's more about availability. Could be under Requirements or Skills. But we have a Schedule section possible. However we could avoid Schedule section by putting that info under Requirements or Skills. Since it's about availability, maybe under Requirements. But we already have Requirements for personal attributes. Could add a bullet there. Thus we can have sections: About the role, Responsibilities, Requirements, Skills, Benefits. That's 5 sections. We need to ensure we don't create empty sections. Let's draft:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Requirements

    • Personable
    • Results-oriented self-starter, a go-getter
    • Team contributor and leader who thrives in a fast-paced setting
    But we also have other requirements like reliable transportation, minimum age, etc. Those are more like qualifications/skills. We'll put them under Skills.

    Skills

    • 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 and federal law
    • Flexible work availability
    • 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