Assistant Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes description of company, then responsibilities? Let's parse. Content: - Intro about Flynn Group, Flynn Wendy's, etc. That's about company, maybe "About the role"? Not exactly. The job posting likely includes "About the role" describing responsibilities: "As an Assistant Manager, you will lead by example in your restaurant, coaching and developing team members so you and your store are successful. You will help run the business through high energy and standards. Effective time management, organizational skills, and communication skills are also essential." That's responsibilities. Then "What else is in it for you?" list: Same Day Pay, Flexible Schedules, Growth and Development, Free Meals, Retirement Plan (eligibility requirements), Group Health Insurance (eligibility requirements). Then compensation line: "Compensation: Wendy's® Assistant Manager $17.25 to $22.50 per hour based on experience and restaurant location. Plus, eligible for profit share bonuses". Then "Flexible schedules, Monthly profit share bonus, Medical/Dental/Vision, 401k with match, Free meals, PTO, Paid Sick Leave". Some duplication. We need sections: About the role? Could be "About the role" maybe not needed. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Thus we need to decide which sections to include. We have: - About the role: maybe a brief description of the role? The posting includes a description of the company and then the role description. Could treat "About the role" as the paragraph describing the Assistant Manager responsibilities? Actually "About the role" could be a short overview: "As an Assistant Manager, you will lead by example..." That's more responsibilities. But we can have sections: Responsibilities, Benefits, Pay, Schedule. Possibly also Qualifications? Not explicit qualifications listed besides skills: effective time management, organizational skills, communication skills. Could be under Skills. Let's extract: Responsibilities: "lead by example in your restaurant, coaching and developing team members so you and your store are successful. You will help run the business through high energy and standards." Also maybe "Effective time management, organizational skills, and communication skills are also essential." That could be Skills. Benefits: list: Same Day Pay, Flexible Schedules, Growth and Development, Free Meals, Retirement Plan (eligibility requirements), Group Health Insurance (eligibility requirements). Also later: Monthly profit share bonus, Medical/Dental/Vision, 401k with match, Free meals, PTO, Paid Sick Leave. Some duplication. Pay: "$17.25 to $22.50 per hour based on experience and restaurant location. Plus, eligible for profit share bonuses". Also "Monthly profit share bonus" maybe part of benefits. Schedule: "Flexible Schedules" mentioned. We should avoid duplication. Provide unique items. We need to output HTML fragment only. Let's craft sections:

  Responsibilities

  • Lead by example in the restaurant, coaching and developing team members to ensure store success.
  • Help run the business with high energy and standards.

  Skills

  • Effective time management
  • Organizational skills
  • Communication skills

  Benefits

  • Same Day Pay
  • Flexible Schedules
  • Growth and Development opportunities
  • Free meals
  • Retirement Plan (eligibility requirements apply)
  • Group Health Insurance (eligibility requirements apply)
  • Monthly profit share bonus
  • Medical, Dental, Vision coverage
  • 401(k) with company match
  • Paid Time Off (PTO)
  • Paid Sick Leave

  Pay

  Wendy's® Assistant Manager: $17.25 to $22.50 per hour, based on experience and restaurant location. Eligible for profit share bonuses.

  We could also include Schedule section but we already have Flexible Schedules in benefits. The instruction says only create Schedule section if posting actually states them. It does mention Flexible Schedules as a benefit. Could still include Schedule section but might be duplicate. Better to keep Benefits includes flexible schedules; no separate Schedule section. We also might include About the role? Not needed if we have Responsibilities. We must not include boilerplate like EEO, privacy notice, etc. Check for duplication: We listed Free meals twice? We have Free meals in benefits and also later free meals; we only list once. We listed Flexible Schedules in benefits; good. We listed Monthly profit share bonus; also profit share bonuses in pay; we can keep both but maybe mention in pay only. However we already have profit share bonus in pay; we could keep it in benefits as well but might be duplication. To avoid duplication, maybe keep profit share bonus only under Pay. But the posting also mentions "Monthly profit share bonus" separate from profit share bonuses? It says "Plus, eligible for profit share bonuses" and later "Monthly profit share bonus". Could be same. To avoid duplication, we can list profit share bonus under Pay only, and not duplicate in Benefits. However we also have "Monthly profit share bonus" as a separate bullet; we could keep it under Benefits but then Pay also mentions profit share bonuses. Might be okay but risk duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay if it's in the source; but we should avoid repeating same info? It says "Remove duplicated lines". So we should remove duplicated lines. So we need to deduplicate. Thus we need to identify duplicate items: "Flexible schedules" appears both in "What else is in it for you?" list and later "Flexible schedules, Monthly profit share bonus, Medical/Dental/Vision, 401k with match, Free meals, PTO, Paid Sick Leave". So we should keep only one instance. "Free meals" appears twice. "Monthly profit share bonus" appears in both lists. "Profit share bonuses" appears in compensation line. Thus we need to keep each unique benefit once. Let's compile unique benefits: - Same Day Pay - Flexible Schedules - Growth and Development - Free Meals - Retirement Plan (eligibility requirements) - Group Health Insurance (eligibility requirements) - Monthly profit share bonus (or profit share bonuses) - Medical/Dental/Vision - 401k with match - PTO (Paid Time Off) - Paid Sick Leave We could combine profit share bonus and profit share bonuses as same. Now Pay: "$17.25 to $22.50 per hour based on experience and restaurant location. Plus, eligible for profit share bonuses." Since we already have profit share bonus in benefits, we might not repeat. But we need to preserve ALL substantive information; if we remove profit share from Pay, we lose the mention that it's eligible for profit share bonuses (though we have it in benefits). However the compensation line also includes the hourly range. So we need to keep that. We could keep Pay section with hourly range and note profit share bonus eligibility (but we already have it in benefits). To avoid duplication, we could mention profit share bonus only in Pay and not in Benefits. But the benefits list also includes Monthly profit share bonus; we could keep it there and not repeat in Pay. However the compensation line also says "Plus, eligible for profit share bonuses." That is substantive; if we omit it, we lose that detail. But we could keep it in Pay and remove from Benefits to avoid duplication. However the benefits list also includes "Monthly profit share bonus" which is essentially same. Which one to keep? The instruction: "Remove duplicated lines". So we need to decide which occurrence to keep. Probably keep the benefit list and drop the duplicate mention in compensation line? But compensation line also includes the hourly range, which is unique. So we can keep Pay section with hourly range and maybe note "eligible for profit share bonuses" but that duplicates benefit. Could we rephrase Pay to just hourly range and mention that profit share bonus is detailed in Benefits? That would be summarizing, not allowed. Better to keep both but note duplication? The instruction says remove duplicated lines, not necessarily remove duplicate meaning if phrased differently. But "Monthly profit share bonus" and "eligible for profit share bonuses" are similar but not identical lines. Might be considered duplicate content. Safer to keep only one mention. I'd keep the benefit list includes Monthly profit share bonus, and in Pay section just give hourly range. However we lose the explicit statement that it's eligible for profit share bonuses, but we have it in benefits. That should be okay. Thus Pay section:

  Wendy's® Assistant Manager: $17.25 to $22.50 per hour, based on experience and restaurant location.

  Now Benefits section includes Monthly profit share bonus. Now we need to ensure we didn't miss any other substantive info: The company intro about Flynn Group, Flynn Wendy's, etc. That's not a job responsibility but could be "About the company". The instruction only gave examples of headings but we could add an "About the company" section if we want, but not required. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings, but we should stick to those examples. Probably better to include only those sections that have content. The company intro could be considered "About the role"? Not really. Could be omitted as it's not a heading about the role. The instruction says do NOT repeat the job title as a heading. It doesn't say we must include company description. But we should preserve ALL substantive information. If we omit company description, we lose substantive info about the company. However the instruction says to output only HTML fragment; we could include a

  with that company info without a heading. That's allowed: use

  for prose. So we can include a paragraph at the start with the company background. Thus output:

  Flynn Group, founded by Greg Flynn started its journey with the acquisition of 8 Applebee’s in 1999. Over the next two decades we grew by building new stores and acquiring other franchise operators to become the largest Applebee’s franchisee in the world. This strong foundation is what allowed Flynn Group to expand into other brands, countries, and industries. We have over 460 Applebee’s restaurants in 24 states. Established in 2021, Flynn Wendy’s has swiftly become a key player within the Flynn Group, owning and operating 300 + Wendy’s restaurants across 8 states. With a diverse and dedicated team of over 6,000 employees, Flynn Wendy’s stands as the 5th largest Wendy’s franchise in the entire Wendy’s system. Our success is