Team Manager

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Content: - Intro: "Lead with purpose..." etc. That's about culture, perks. Could be "About the role"? Actually it's more about company culture and perks. Could be "About the role" or "Benefits". We'll need to decide. - Then "What’s In It for You?" list of benefits: Competitive pay & eligible for quarterly bonuses, Free on-shift meals & unlimited fountain beverages, Paid vacation, sick time, and holidays, Medical, dental, vision, life insurance, pet insurance & 401(k) with match available, Career advancement & leadership development opportunities, Tuition discounts, Perks & rewards for team members, Team member assistance program, And much, much more! That's benefits. - Then "As a Team Manager, you’ll be part of the bakery-cafe’s leadership team, helping to run great shifts, support team development, and maintain the high standards our guests expect." - Then "As a Team Manager at Panera, Your Role Includes:" then bullet list (actually sentences separated by periods). We'll treat as list items. - Then "This Opportunity Is for You If:" then list of requirements: Minimum age: 18 years of age. 1+ years of restaurant management experience preferred. Proven ability to lead great shifts while directing, motivating, coaching and developing others in a fast-paced environment. ServSafe certification (or ability to achieve certification). This role requires flexible hours including nights and weekends in a fast-paced environment with shifting priorities. Any job offer for this position is conditional upon the results of a background check. - Then "While performing this job, the Team Manager role is regularly required to:" then list of physical requirements: Ability to lift, carry, push, or pull objects 25 pounds. Capability to stand and walk for up to 6 hours. Must be able to clearly communicate and quickly understand guests and associates’ directions in a loud environment. Be an ambassador of our Guiding Values and Behaviors by making people smile, learning and growing together, finding solutions and taking initiative, working (and winning) as a team, having fun and celebrating success, and seeing the best in others! - Then EEO boilerplate to remove. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we drop the final EEO line. We need to not repeat job title as heading. The job title is "Team Manager". Not to put as heading. We need to include sections only when posting has real specific content. So we can have sections: About the role (maybe intro), Responsibilities, Requirements (maybe combine qualifications and skills), Benefits. Pay? The posting mentions "Competitive pay & eligible for quarterly bonuses" under benefits. So we could include Pay within Benefits or separate Pay section. The rule: include Pay section only if posting actually states them. It does state competitive pay & quarterly bonuses. So we could have a Pay section. However we also have benefits list includes many items. Could combine Pay and Benefits into one Benefits section? The rule says prefer a few substantive sections over many thin ones. So maybe combine Pay and Benefits into a single "Benefits" section that includes pay info. Or we could have separate Pay and Benefits but that would be thin. Better to combine. Schedule: posting mentions flexible hours including nights and weekends. That's schedule info. Could be a Schedule section. Thus sections: About the role (intro), Responsibilities, Requirements (including qualifications, skills, physical demands), Benefits (including pay, bonuses, meals, vacation, insurance, etc.), Schedule. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep each bullet point as is. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Let's craft. First, About the role: The intro paragraphs: "Lead with purpose. Grow with support. At Panera, our leaders are celebrated for bringing out the best in their teams. Enjoy great perks, a welcoming culture, and the opportunity to make a real impact—every day.Get ready to rise and come join the fun where you will be a part of making the familiar fantastic! Because at Panera, the best thing of bread is sharing it!" That's a bit run-on. We'll keep as prose in

  . Might split into two

  for readability but not required. We'll keep as one

  . Second, Responsibilities: Under "As a Team Manager at Panera, Your Role Includes:" then list items. We'll make

  Responsibilities

  then
  • each item. List items: - Make sure every guest is delighted by the quality of our food, service, and staff. - Build engaging relationships that lead to long-term, loyal guests. - Lead, manager and develop team members by coaching, inspiring, and motivating them to exceed goals in sales, speed, order accuracy, and guest experience – and celebrate their achievements along the way. - Participate in the interviewing and selection process. - Train the team in food safety standards and ensure they are maintained. - Help build our Culture of warmth, belonging, growth, and trust. Note there is a typo "Lead, manager". We'll keep as is. Third, Requirements: This includes "This Opportunity Is for You If:" and also the physical requirements list. Could combine into one Requirements section with sublists? But we need to use
    • for any list. We could have two lists: one for qualifications, another for physical demands. Or we could combine all into one list but that might mix types. Better to have two subheadings? But we only allowed

      for section headings; we could have nested

      ? Not specified. Probably better to keep one Requirements section with two

      lists, each preceded by a

      describing. That's acceptable. So

      Requirements

      then maybe a

      for the qualifications intro: "This Opportunity Is for You If:" then

      with items: - Minimum age: 18 years of age. - 1+ years of restaurant management experience preferred. - Proven ability to lead great shifts while directing, motivating, coaching and developing others in a fast-paced environment. - ServSafe certification (or ability to achieve certification). - This role requires flexible hours including nights and weekends in a fast-paced environment with shifting priorities. - Any job offer for this position is conditional upon the results of a background check. Then another

      for physical demands: "While performing this job, the Team Manager role is regularly required to:" then

      with items: - Ability to lift, carry, push, or pull objects 25 pounds. - Capability to stand and walk for up to 6 hours. - Must be able to clearly communicate and quickly understand guests and associates’ directions in a loud environment. - Be an ambassador of our Guiding Values and Behaviors by making people smile, learning and growing together, finding solutions and taking initiative, working (and winning) as a team, having fun and celebrating success, and seeing the best in others! Note the last item is long; keep as is. Fourth, Benefits: Include the "What’s In It for You?" list plus maybe the intro about perks? Already used intro in About the role. We'll keep benefits list. So

      Benefits

      then
      • each item: - Competitive pay & eligible for quarterly bonuses - Free on-shift meals & unlimited fountain beverages - Paid vacation, sick time, and holidays - Medical, dental, vision, life insurance, pet insurance & 401(k) with match available - Career advancement & leadership development opportunities - Tuition discounts - Perks & rewards for team members - Team member assistance program - And much, much more! We could drop the "And much, much more!" as it's vague but it's part of the posting; it's not filler like "N/A". It's a statement but vague. Might be considered filler? 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. "And much, much more!" is not specific detail; it's filler. Better to omit it to avoid filler. We'll omit that line. Thus benefits list without that line. Fifth, Schedule: The posting mentions flexible hours including nights and weekends. That's schedule info. Could be a short

        under Schedule heading. We'll include

        Schedule

        then

        Flexible hours including nights and weekends in a fast-paced environment with shifting priorities.

        But note that flexible hours already appears in Requirements list. Might be duplicate. However we can keep it in Schedule section as a summary; but we must preserve all substantive information; we already have it in Requirements list. Duplicating is okay but we might avoid duplication. The rule says remove duplicated lines. So we should not duplicate the same sentence. Since we already have flexible hours in Requirements list, we should not repeat it in Schedule section. Instead we could note schedule info is covered; but we need a Schedule section only if posting has real specific content for it. The posting does mention flexible hours including nights and weekends. That's schedule-specific. Even if we also have it in Requirements, we could still include Schedule section but we must avoid duplicating lines. We could rephrase: "This role requires flexible hours including nights and weekends." That's same as in Requirements. To avoid duplication, we could omit Schedule section and rely on Requirements to convey schedule. But the rule says prefer a few substantive sections over many thin ones. Having a Schedule section with just that line might be thin. Better to omit Schedule section and keep schedule info within Requirements. However the rule says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. If we make a Schedule section with just that line, it's specific content but thin. The rule says prefer a few substantive sections over many thin ones. So we could combine schedule into Requirements or Benefits? It's not benefit. So we keep it in Requirements. Thus we will not have a separate Schedule section. Thus final sections: About the role, Responsibilities, Requirements, Benefits. Check if any other sections like Qualifications/Skills needed? We have Requirements covering qualifications and physical demands. Could split into Qualifications and Skills but that would be thin. We'll keep as Requirements. Now produce HTML. We need to ensure proper nesting. Let's write:

        About the role

        Lead with purpose. Grow with support. At Panera, our leaders are celebrated for bringing out the best in their teams. Enjoy great perks, a welcoming culture, and the opportunity to make a real impact—every day. Get ready to rise and come join the fun where you will be a part of making the familiar fantastic! Because at Panera, the best thing of bread is sharing it!

        Responsibilities

        • Make sure every guest is delighted by the quality of our food, service, and staff.
        • Build engaging relationships that lead to long-term, loyal guests.
        • Lead, manager and develop team members by coaching, inspiring, and motivating them to exceed goals in sales, speed, order accuracy, and guest experience – and celebrate their achievements along the way.
        • Participate in the interviewing and selection process.
        • Train the team in food safety standards and ensure they