Kitchen Team Member

We need to output HTML fragment with sections: headings

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to parse the job posting. The posting includes: - Intro: "Why Maple Street Biscuit Company At Maple Street, our mission is simple: Help People, Serve Others, Be a Part of the Community. We take pride in our food, but above all, we take pride in our community—starting with our team. Our Maple Street Team Members are the foundation of our culture, so we’re committed to providing them with a great work environment and opportunities to grow with us. Whether you like to spend time interacting with our guests or showing off your culinary skills, you’ll enjoy opportunities to showcase your talent and have plenty of room to grow. Grow your community—and grow with us." That's like "About the role" or "About Us". Could be "About the role" or "About Us". We'll decide. - Then "WHAT YOU’LL DO | THE OPPORTUNITY" with description: "We know you want to start your day right, so start it with us. Whether you’re scratch-making our one-of-a-kind flaky biscuits or adding the final touches to each delicious dish that goes out, you’ll have a hand in creating an inspirational culinary experience for each guest! No matter where your experience lies, we’ll provide the training you need to thrive. The best part? We close after lunch, so Maple Street has no night shifts!" That's responsibilities/duties. - Then "What You’ll Need Ability to thrive within a collaborative environmentA genuine passion for serving your communityThe desire for personal and professional development". This is requirements/qualifications. - Then "What’s In It For You Medical insurance eligibility on day 1Weekly pay and same-day pay access Free meal every shift 35% team member discount on food and retailNo night shifts Community involvement". This is benefits. - Then "About Us Our mission is this: Help People, Serve Others, Be a Part of the Community. We mean this in the context of our community-facing stores and our guests, but we also mean this in terms of our internal community. We are serious about providing our team members with opportunities to grow with us. From our Ambassadors and Baristas all the way up to our Community Leaders (that’s what we call our store managers – are you sensing a theme?), our team works hard to train, encourage, and uplift one another so that your time here as one of the Maple Street crew becomes a valuable part of your identity. BECOME A PART OF OUR COMMUNITY. APPLY NOW! We are an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, national origin, disability status, protected veteran status, or any other characteristic protected by law." We need to remove EEO boilerplate, application instructions, etc. So we should drop the "BECOME A PART OF OUR COMMUNITY. APPLY NOW!" and the EEO statement. Also drop duplicated lines. We need to preserve all substantive information. Thus we need sections: - About the role (or About Us) - combine intro and About Us? The intro is about mission and team. The About Us repeats mission. Could combine into one "About the role" or "About Us". Since we cannot repeat job title as heading, but we can have About the role. We need to decide headings: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only those with real content. We have: - About the role: mission, team, work environment, growth opportunities. - Responsibilities: what you'll do (scratch-making biscuits, adding final touches, creating culinary experience, training, no night shifts). - Requirements/Qualifications: ability to thrive in collaborative environment, passion for serving community, desire for personal/professional development. - Benefits: medical insurance eligibility day 1, weekly pay and same-day pay access, free meal every shift, 35% team member discount, no night shifts, community involvement. We might also have Pay? Not explicitly stated beyond weekly pay and same-day pay access (that's pay frequency). Could be considered Pay section but we already have weekly pay in Benefits. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine pay info into Benefits. Schedule: we have "no night shifts" and "close after lunch". That's schedule info. Could be a Schedule section. But we already have no night shifts in Benefits. Might be better to have Schedule section with "No night shifts; close after lunch." However we must not create Schedule unless posting actually states them. It does state "We close after lunch, so Maple Street has no night shifts!" That's schedule. So we could have a Schedule section. But we also have "No night shifts" listed under benefits. Could be duplicate. We should avoid duplication. Perhaps we put schedule info in Schedule section, and benefits exclude that. Thus: - About the role (h3) with paragraph(s) about mission, team, work environment, growth. - Responsibilities (h3) with ul list of duties? The posting says "Whether you’re scratch-making our one-of-a-kind flaky biscuits or adding the final touches to each delicious dish that goes out, you’ll have a hand in creating an inspirational culinary experience for each guest! No matter where your experience lies, we’ll provide the training you need to thrive. The best part? We close after lunch, so Maple Street has no night shifts!" That's prose, not a list. Could be

. - Requirements (h3) with ul list: Ability to thrive within a collaborative environment, A genuine passion for serving your community, The desire for personal and professional development. - Benefits (h3) with ul list: Medical insurance eligibility on day 1, Weekly pay and same-day pay access, Free meal every shift, 35% team member discount on food and retail, Community involvement. - Schedule (h3) with p: No night shifts; close after lunch. We must not repeat job title as heading. Not needed. We must not include Pay or Schedule if not real; we have schedule. We must not include empty sections. We must remove boilerplate: EEO, apply now, etc. We must not include duplicated lines. Now produce HTML fragment: only the sections, no or . Use

headings,

for prose,

• for lists. We need to ensure we preserve all substantive information. Let's craft:

  About the role

  At Maple Street Biscuit Company, our mission is simple: Help People, Serve Others, Be a Part of the Community. We take pride in our food, but above all, we take pride in our community—starting with our team. Our Maple Street Team Members are the foundation of our culture, so we’re committed to providing them with a great work environment and opportunities to grow with us. Whether you like to spend time interacting with our guests or showing off your culinary skills, you’ll enjoy opportunities to showcase your talent and have plenty of room to grow. Grow your community—and grow with us.

  Responsibilities

  Whether you’re scratch‑making our one‑of‑a‑kind flaky biscuits or adding the final touches to each delicious dish that goes out, you’ll have a hand in creating an inspirational culinary experience for each guest! No matter where your experience lies, we’ll provide the training you need to thrive. The best part? We close after lunch, so Maple Street has no night shifts.

  Requirements

  • Ability to thrive within a collaborative environment
  • A genuine passion for serving your community
  • The desire for personal and professional development

  Benefits

  • Medical insurance eligibility on day 1
  • Weekly pay and same‑day pay access
  • Free meal every shift
  • 35% team member discount on food and retail
  • Community involvement

  Schedule

  No night shifts; close after lunch.

  Check for any missing info: The About Us paragraph about mission repeated; we included mission in About the role. The About Us also includes details about internal community, Ambassadors, Baristas, Community Leaders, training, encourage, uplift, valuable part of identity. We missed that. Need to include that substantive info. So we should add that to About the role or maybe a separate About Us section. Since we already have About the role, we can expand it to include that. Thus About the role paragraph should include: "We are serious about providing our team members with opportunities to grow with us. From our Ambassadors and Baristas all the way up to our Community Leaders (that’s what we call our store managers – are you sensing a theme?), our team works hard to train, encourage, and uplift one another so that your time here as one of the Maple Street crew becomes a valuable part of your identity." Add that after the first paragraph maybe as another

  under same heading. Thus About the role will have two

  elements. Now check for any other info: The posting also said "Whether you like to spend time interacting with our guests or showing off your culinary skills, you’ll enjoy opportunities to showcase your talent and have plenty of room to grow." Already included. Now ensure we didn't include any boilerplate: removed "BECOME A PART OF OUR COMMUNITY. APPLY NOW!" and EEO statement. Now check for duplicate content: We have "No night shifts" appears in Responsibilities and Schedule. In Responsibilities we mentioned "The best part? We close after lunch, so Maple Street has no night shifts." That's part of responsibilities description. In Schedule we have "No night shifts; close after lunch." That's duplicate but maybe okay as it's schedule specifics. However we might consider moving the schedule info solely to Schedule and remove from Responsibilities to avoid duplication. But the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we remove the sentence from Responsibilities, we lose that detail (though it's still in Schedule). But we could keep it in both places; it's not invented, it's just duplicated. Might be okay but better to avoid duplication? The instruction says remove duplicated lines. So we should avoid duplicate lines. The sentence about no night shifts appears in both sections; we should keep it only once. Where does it belong more? It's about schedule, but also part of responsibilities (the best part). Could keep in Responsibilities as it's part of the opportunity description, and then Schedule could just say "Close after lunch." But we need to convey no night shifts. Could say Schedule: "Close after lunch (no night shifts)." That captures both. Thus adjust: Responsibilities: keep the sentence about scratch-making biscuits, training, and maybe mention no night shifts? We could keep it there but then Schedule just says "Close after lunch." However we need to preserve the info that there are no night shifts. If we put it only in Responsibilities, we still have it. Schedule can be just "Close after lunch." That still conveys schedule but not explicitly no night shifts. But we can add "(no night shifts)" in Schedule to avoid duplication? That would be duplication again. Let's think: The sentence "We close after lunch, so Maple Street has no night shifts!" is a single statement. If we split it, we risk altering meaning. Better to keep it whole in one place. Which section is more appropriate? The "What You'll Do | The Opportunity" section includes that sentence as part of the opportunity. So it's part of responsibilities/opportunity. The schedule is derived from that. So we could keep it in Responsibilities and not have a separate Schedule section. But the instruction says include a section