Team Member

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

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting. Given content: - Role: Restaurant Team Member (title) - Employer: Capriotti’s Sandwich Shop - Location: Honolulu, HI - Compensation: Competitive Hourly Pay (Based on Experience) - Job Type: Full-Time or Part-Time - This is an entry-level position! - Benefits list: Employee Assistance Program (EAP), Health benefits (for eligible team members), Free meals and employee discounts, Flexible scheduling, Paid training and ongoing development, Opportunities for advancement - Then a paragraph about brand. - Position Overview paragraph. - Responsibilities list (bullets) - What We’re Looking For list (bullets) - Why Join Capriotti’s? list (bullets) - At Capriotti’s, you’ll find more than just a job... paragraph. We need to map to sections. We should not repeat job title as heading. We can include employer and location maybe in a short

metadata. We need to include sections only if real specific content. Potential sections: - About the role: could be the Position Overview paragraph (maybe also brand description). Could combine brand description and position overview. - Responsibilities: list of duties. - Requirements: maybe "What We’re Looking For" includes requirements (age, skills, etc). Could be Requirements. - Qualifications: maybe not separate; we could combine with Requirements. - Skills: maybe not needed. - Benefits: list of benefits. - Pay: we have "Competitive Hourly Pay (Based on Experience)" - that's vague but it's specific content? It says Competitive Hourly Pay (Based on Experience). That's not a specific number but it's still content. The rule says: 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. Here they state "Competitive Hourly Pay (Based on Experience)". That's somewhat vague but it's still stating something about pay. Is that considered filler? It's similar to "commensurate with experience". The rule says "commensurate with experience" is placeholder. "Competitive Hourly Pay (Based on Experience)" is similar. Might be considered placeholder. Safer to not create Pay section unless we have actual numbers or range. So we omit Pay. - Schedule: they mention Flexible scheduling in benefits and also "Availability for flexible scheduling including evenings, weekends, and holidays" under What We’re Looking For. That's schedule info. Could we create a Schedule section? The rule: never create Schedule section unless posting actually states them. They do mention flexible scheduling. That's specific enough? It's not a specific schedule but mentions flexibility. Might be okay. However we already have flexible scheduling listed under Benefits. Could combine. But we could create a Schedule section with that info. However we need to avoid filler like "varies". "Flexible scheduling including evenings, weekends, and holidays" is somewhat specific. I'd include a Schedule section. - Benefits: we have list. - About the role: we have brand description and position overview. - Responsibilities: list. - Requirements/Qualifications/Skills: we have "What We’re Looking For" list (age, skills, etc). Could split into Requirements (must be at least 16, availability) and Skills (customer service, communication, math, teamwork). But we can just have one Requirements section with all. We need to avoid creating sections with filler. Ensure each heading has substantive content. Let's craft:

Employer: Capriotti’s Sandwich Shop
Location: Honolulu, HI
Job Type: Full-Time or Part-Time

Then sections:

About the role

Capriotti’s Sandwich Shop is a fast-growing fast-casual restaurant brand with over 100 locations nationwide and exciting expansion plans ahead. Known for award-winning sandwiches, fresh ingredients, and friendly service, we seek an enthusiastic Restaurant Team Member to join our team. As a Restaurant Team Member, you will help deliver our mission of “Sharing Our Passion One Sandwich at a Time.” You’ll prepare high-quality food, provide excellent guest service, and maintain a clean and welcoming restaurant environment.

Responsibilities

• Provide friendly and professional customer service to every guest
• Take orders accurately at the register or drive-thru (where applicable)
• Prepare sandwiches, salads, and menu items according to Capriotti’s recipes and quality standards
• Maintain cleanliness and organization throughout the restaurant, including kitchen and dining areas
• Follow food safety, sanitation, and health guidelines at all times
• Handle cash and credit card transactions accurately
• Work collaboratively with team members and shift leaders to ensure efficient service
• Complete required training programs and develop new skills
• Help create a positive, high-energy team environment

Requirements

• Must be at least 16 years of age
• Strong customer service and communication skills
• Ability to work quickly and efficiently in a fast-paced restaurant environment
• Dependable, adaptable, and team-oriented work ethic
• Basic math skills for cash handling and transactions
• Availability for flexible scheduling including evenings, weekends, and holidays
• Positive attitude and commitment to Capriotti’s standards of Quality, Passion, and Pride

Benefits

• Employee Assistance Program (EAP)
• Health benefits (for eligible team members)
• Free meals and employee discounts
• Flexible scheduling
• Paid training and ongoing development
• Opportunities for advancement

Schedule

Flexible scheduling is offered, with availability for evenings, weekends, and holidays.

We should not include Pay section. Check for any duplicated lines: we have flexible scheduling both in Benefits and Schedule; that's okay but maybe redundant. Could remove Schedule section and keep flexible scheduling under Benefits only. However the rule says prefer few substantive sections over many thin ones. Having Schedule section might be thin (just one sentence). Better to incorporate schedule info into Benefits or Requirements. Since we already have flexible scheduling in Benefits, we can drop Schedule section. Thus sections: About the role, Responsibilities, Requirements, Benefits. We need to ensure we didn't miss any substantive content: The "Why Join Capriotti’s?" list overlaps with Benefits and maybe also with About the role. It includes opportunities for career growth, flexible scheduling, supportive environment, paid training, award-winning sandwiches. Some of that is already covered. But we should not lose that info. The "Why Join Capriotti’s?" list includes: Opportunities for career growth and promotion from within, Flexible scheduling for school, family, or other commitments, Supportive and team-focused work environment, Paid training and leadership development opportunities, Work for a brand known for award-winning sandwiches and exceptional hospitality. Some of these are not captured elsewhere: "Opportunities for career growth and promotion from within" (similar to Opportunities for advancement but more specific), "Supportive and team-focused work environment", "Paid training and leadership development opportunities" (similar to Paid training and ongoing development but leadership development), "Work for a brand known for award-winning sandwiches and exceptional hospitality" (brand description). We could incorporate these into Benefits or About the role. We should preserve all substantive information. So we need to include those points somewhere. We can add to Benefits: Opportunities for career growth and promotion from within, Supportive and team-focused work environment, Paid training and leadership development opportunities, Work for a brand known for award-winning sandwiches and exceptional hospitality. But we already have Opportunities for advancement (similar). We can keep both but maybe combine. Let's create Benefits list with all distinct items: - Employee Assistance Program (EAP) - Health benefits (for eligible team members) - Free meals and employee discounts - Flexible scheduling - Paid training and ongoing development - Opportunities for advancement - Opportunities for career growth and promotion from within - Supportive and team-focused work environment - Paid training and leadership development opportunities (maybe redundant with Paid training) - Work for a brand known for award-winning sandwiches and exceptional hospitality We might have duplicates: Paid training and ongoing development vs Paid training and leadership development opportunities. Could combine as "Paid training and ongoing development, including leadership opportunities". But we must not invent or summarize away detail. We can keep both as separate items; it's okay if similar. But we should avoid excessive duplication. However the rule says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep each distinct statement. If they are similar but not identical, we keep both. Let's list them as separate

items. Now About the role: we already have brand description and position overview. Could also include the mission statement "Sharing Our Passion One Sandwich at a Time." Already included. Now Responsibilities: we have list. Requirements: we have list. Now we need to ensure we didn't miss any other info: The "Position Overview" paragraph we used. The "Join a Growing Fast-Casual Restaurant Brand" paragraph we used in About the role. The "At Capriotti’s, our team members are the heart..." we used partly. The "Position Overview As a Restaurant Team Member..." we used. The "What We’re Looking For" we used as Requirements. The "Why Join Capriotti’s?" we used as Benefits (some). The final paragraph "At Capriotti’s, you’ll find more than just a job—you’ll discover a place to learn, grow, and be part of something special. Apply now! Join our team and help us deliver unforgettable guest experiences one sandwich at a time." That's promotional; we could incorporate into About the role or maybe a closing paragraph. But we should preserve substantive information; that's basically a call to action and tagline. Could add a

after sections: "At Capriotti’s, you’ll find more than just a job—you’ll discover a place to learn, grow, and be part of something special." That's substantive. We'll add a final

after sections. We must not include application instructions like "Apply now!"? The rule says remove application instructions. "Apply now!" is application instruction. So we should strip that. Keep the motivational sentence but not "Apply now!". The sentence: "At Capriotti’s, you’ll find more than just a job—you’ll discover a place to learn, grow, and be part of something special." That's fine. Then "Join our team and help us deliver unforgettable guest experiences one sandwich at a time." That's also motivational but not instruction to apply. Keep. Thus final

after sections. Now ensure we didn't include any boilerplate like EEO etc. Not present. Now produce HTML fragment. Let's craft:

Employer: Capriotti’s Sandwich Shop
Location: Honolulu, HI
Job Type: Full-Time or Part-Time

About the role

Capriotti’s Sandwich Shop is a fast-growing fast-casual restaurant brand with over 100 locations nationwide and exciting expansion plans ahead. Known for award-winning sandwiches, fresh ingredients, and friendly service, we seek an enthusiastic Restaurant Team Member to join our team. As a Restaurant Team Member, you will help deliver our mission of “Sharing Our Passion One Sandwich at a Time.” You’ll prepare high-quality food, provide excellent guest service, and maintain a clean and welcoming restaurant environment.

Responsibilities

• Provide