Assistant Manager 207

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. Remove boilerplate: EEO, etc. Must preserve all substantive info. Let's parse the posting. Content: - Who We Are: description about growing Burger King franchise, upward mobility, etc. This is "About the role"? Actually "Who We Are" is about company. Could be "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map sections accordingly. We have: Who We Are: description of company, growth, etc. Could be placed under "About the role" maybe? But "About the role" typically describes the role, not company. However we have no explicit "About the role" heading in source. We could treat "Who We Are" as about the company, but we could still put under "About the role"? Might be okay. But we need to ensure we don't create filler sections. We have substantive content for Who We Are, so we can create a section maybe "About the role" with that content. Next: "Who You Are": Personable, Results-oriented self-starter, etc. That's like qualifications/skills. Could go under "Qualifications" or "Skills". We'll decide. Then: "Here-s What You Will Be Doing": list of responsibilities. That's responsibilities. Then: "HERE-S WHAT Education - Experience YOU WILL NEED": list of requirements: high school diploma, 1-2 years supervisory experience, etc. That's requirements/qualifications. Then: "SOME Perks - Benefits (Based On Eligibility Requirements)": list of benefits: scholarship fund, emergency fund, discount program, provider finder, wellness program, pregnancy planning tool. Also mention background check, equal opportunity employer (boilerplate to remove). Location: address. No explicit Pay or Schedule info. So we should NOT create Pay or Schedule sections because they are not stated. Thus we will have sections: About the role (from Who We Are), Responsibilities (from Here-s What You Will Be Doing), Requirements (from Education - Experience YOU WILL NEED), Benefits (from SOME Perks - Benefits). Possibly also Skills? Could combine Who You Are into Skills or Qualifications. But we already have Requirements covering education/experience; Who You Are is more about personal attributes (skills). Could create a Skills section for that. However we must avoid thin sections. Who You Are has several bullet-like sentences: Personable, Results-oriented self-starter, a go-getter. Team contributor and leader who thrives in a fast-paced setting. That's a few lines; could be a Skills section. We need to decide: we have four substantive sections: About the role, Responsibilities, Requirements, Benefits. Plus maybe Skills. That's five sections. The instruction: "Prefer a few substantive sections over many thin ones." Who You Are is not super thin but could be merged into Requirements or Skills. Since we already have Requirements for education/experience, we could put personal attributes under Skills. That would be a separate section. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits. We must not include Pay or Schedule. Now format: Use

for each heading. Use

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

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract each piece. About the role (Who We Are): "We are a GROWING Burger King franchise with upward mobility. As one of the largest Burger King franchises, we are dedicated to achieving customer satisfaction as well as providing career opportunities for our employees. As our company grows, we look for employees who share our passion for achieving exceptional results. At Burger King, employees have an opportunity to contribute to the success of our growing organization. If you're looking for a chance at a fast-paced, hands-on career, you've come to the right place. From Team Member to Restaurant Assistant Manager, the job opportunities in BURGER KING- restaurants are challenging and fun." We need to keep that as prose (

  ). Possibly we could break into multiple paragraphs but one is fine. Responsibilities (Here-s What You Will Be Doing): list of duties. The text includes many items separated by line breaks? It appears as a paragraph with many items separated by line breaks? Actually it's a long sentence with many items separated by line breaks? Let's copy: "Develop Servant Leaders-Puts your people and restaurant first-not yourselfCreate Memorable Experiences-Creates a service experience so good the guest can-t wait to come back to Burger KingAdministration-Maintains the balance between providing a high-quality employee and guest experience, and achieving financial goalsWelcomes new team members and provides them with the training needed to do their jobLeads inspiring team huddles that motivate and inform the teamEnsures team members receive ongoing training and coachingBuilds the capability of the shift supervisors and prepares them for their next levelConsistently thanks the team and celebrates successActively coaches brand service behaviors-train, observe, provide feedback and celebrateMonitors Speed of Service to ensure delivery of guest expectationsEnsures the restaurant is welcoming and cleanEnsures product quality and operations standards are consistently deliveredPartners with the Restaurant General Manager and team to create action plans to improve guest metricsReviews sales and scheduling to ensure Quality, Service and Cleanliness (QSC) will be metEnsures accuracy of daily numbers, cash handling and HACCP LogsReviews inventory efficiencies to create product ordersEvaluates and implements cost controlsMonitors people charts and production planning and makes necessary adjustmentsCreates and monitors schedule and manages new team members on-boarding processImplements action plans to address employee needs and Operational Assessments" It seems each duty is separated by a hyphen? Actually format: "Develop Servant Leaders-Puts your people and restaurant first-not yourself" maybe the dash is part of the phrase. Hard to parse. But we need to preserve all substantive information; we can keep as a list where each duty is a separate

• . We need to split logically at points where there is a capital letter after a period? There are no periods. The text uses hyphens to separate duty title and description? Eg "Develop Servant Leaders-Puts your people and restaurant first-not yourself". Could treat each item before a capital letter that starts a new duty? Let's attempt to split by looking for pattern: a capital letter after a lowercase letter? Not reliable. Simpler: we can keep the whole block as a single

  preserving the text. But instruction says use

  • for any list of duties/requirements/benefits. This is a list of duties, so we should make a list. We need to split into items. We can approximate by splitting at each occurrence of a capital letter that follows a lowercase letter and is preceded by a space? Not present. Actually there are no spaces between items; they are concatenated. Eg "...yourselfCreate Memorable Experiences-Creates...". There's no space before "Create". So we could insert a space before each capital letter that follows a lowercase letter? But we must not invent content. However we can keep as a single paragraph; the instruction says use
    • for any list. If we don't split, we violate that rule. But maybe we can treat the whole block as a prose description (

      ) and not a list. The rule says "Use

      • for any list of duties/requirements/benefits". If we don't have a clear list, we could keep as prose. The source appears as a list but not formatted with line breaks or bullets. It's ambiguous. Safer to keep as

        preserving the exact text. That preserves all info and doesn't invent structure. The rule is a preference but not absolute? It says "Use

        • for any list of duties/requirements/benefits". If we treat it as not a list, we might be okay. However it's clearly a list of duties. But we lack clear delimiters. Could we insert
        • for each sentence separated by a period? There are no periods. So we cannot reliably split. Thus we will output a

          with the responsibilities text exactly as given. Similarly for Requirements: "Must have a high school diploma or equivalentMinimum of 1-2 years supervisory experienceExcellent guest service skills requiredAbility to work in a fast-paced environmentAbility to communicate effectively with guests and team membersAbility to resolve issues in compliance with Burger King standardsAbility to keep employees motivates, resolve conflicts, and make hard decisionsAvailable to work all shifts; open, close, weekends and holidays" Again no delimiters. We'll keep as

          . Skills (Who You Are): "Personable, Results-oriented self-starter, a go-getter. Team contributor and leader who thrives in a fast-paced setting." That's two sentences; we can keep as

          . Benefits: list of benefits: Scholarship Fund Program..., Burger King emergency fund..., discount program..., provider finder/cost estimation tool..., wellness program..., pregnancy planning tool... Also mention background check and equal opportunity employer (boilerplate to remove). We'll remove EEO boilerplate. Also "The Company reserves the right to conduct a background check of its employees, and your employment may be conditioned on satisfactory results." That's not a benefit; it's a condition. Should we keep? It's substantive info about background check. It's not a benefit but could be included under Benefits? Might be better to put under Requirements? Actually it's a condition of employment. Could be placed under Requirements? But it's not a requirement for the candidate; it's a company policy. The instruction says remove EEO/equal-opportunity/... boilerplate. Background check is not EEO; it's a condition. Might be okay to keep as a

          under Benefits or maybe a separate section? There's no heading for "Background check". We could include it in Benefits section as a note. But the instruction says include a section ONLY when posting has real, specific content for it. Background check is specific content. Could we create a section "Background check"? Not in allowed headings list. So we must fold into existing allowed headings. Could put under Requirements? Not really a requirement. Could put under Benefits? Not a benefit. Could put under About the role? Not appropriate. Could put under Responsibilities? No. Maybe we can omit it because it's not a benefit, requirement, etc. But the instruction says preserve ALL substantive information. So we need to keep it somewhere. Perhaps we can add a

          after the Benefits section without a heading, just a paragraph. That's allowed: we can have prose outside headings. The instruction only says use headings for sections; we can have extra paragraphs. So we can keep the background check statement as a

          after Benefits. Similarly location: "Location: 2700 S Kedzie, Chicago, Illinois 60623". That's substantive. We can put as a

          after Benefits or after background check. Now we need to ensure we don't include boilerplate: "We are an equal opportunity employer" remove. Also "The Company reserves the right to conduct a background check..." we keep. Also maybe "Scholarship Fund Program provides scholarships ranging from $1000 to $50,000 to Burger King team members, their families and high school seniors." etc. Now craft HTML. Structure:

          About the role

          ... (Who We Are text)

          Responsibilities

          ... (Here-s What You Will Be Doing text)

          Requirements

          ... (Education - Experience YOU WILL NEED text)

          Skills

          ... (Who You Are text)

          Benefits

          • Scholarship Fund Program provides scholarships ranging from $10