General Manager

for prose. We need to parse the posting. First, we have Role: Restaurant General Manager (title). Employer: Capriotti’s Sandwich Shop. Location: Capriotti’s Sandwich Shop in Las Vegas, NV. Compensation: Competitive Salary (Based on Experience). Benefits list: Competitive pay, Medical, dental, and vision insurance, 401(k) plan, Flexible Spending Accounts (FSAs), Employee Assistance Program (EAP), Referral bonus program, Opportunities for advancement and career growth. Then paragraphs: "Join a Fast-Growing, Award-Winning Restaurant Brand ..." etc. Then Position Overview paragraph. Then Responsibilities with bullet list (multiple subheadings? Actually they have headings like "Lead and Develop Your Team", "Operational Excellence", "Guest Experience", "Business & Financial Management", "Communication & Leadership". Those are subheadings within responsibilities. According to rules, we should use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have a top-level section "Responsibilities" with

. Under that we can have sub-items maybe as

• with paragraphs? The subheadings inside responsibilities could be treated as list items or maybe we could keep them as inside li? 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. So we should treat each duty as a list item. The subheadings like "Lead and Develop Your Team" could be the heading of a list item? Could be

  • Lead and Develop Your Team: ...
  . That seems okay. Similarly for Requirements: we have "What We’re Looking For" bullet list (actually it's a paragraph with bullet-like lines). We'll make a Requirements section with

  and list items. Qualifications? Not separate; maybe we combine Requirements and Qualifications? The instruction says we can have sections like Qualifications, Skills. But we only have content for Requirements (experience, skills). We could put them under Requirements. Skills: maybe we could extract skills from requirements: strong organizational, time management, problem-solving, communication, interpersonal, experience managing operations, scheduling, inventory, labor, comfortable using POS systems and basic computer software. Could be a Skills section. But we already have those in requirements; we could combine. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Skills into one section "Requirements". Or we could have Requirements and Skills separate but they'd be thin. Better to combine. Benefits: we have list; we should create Benefits section with

  and

  • . Pay: we have "Competitive Salary (Based on Experience)". That's not specific numbers; it's vague. According to instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation: Competitive Salary (Based on Experience). That's a statement, albeit vague. Should we include Pay section? It says "Competitive Salary (Based on Experience)". That's a statement about pay. It's not "not specified" but it's vague. The instruction: 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 Salary (Based on Experience)". That's similar to "commensurate with experience". That's considered filler? Likely yes, it's placeholder. So we should NOT create a Pay section because it's just vague. So we omit Pay. Schedule: not mentioned; omit. About the role: we have Position Overview paragraph; could be "About the role" or "Position Overview". Use

    for section headings like About the role, Responsibilities, etc. So we can have About the role section with the overview paragraph. We also have introductory paragraphs about company: "Join a Fast-Growing, Award-Winning Restaurant Brand ..." That could be part of About the role or maybe a separate section "About the company". But not in allowed headings list; we could incorporate into About the role or maybe a separate section "About Capriotti’s". But instruction says use those headings examples; not strict to only those, but we should follow similar pattern. Probably better to have About the role section containing the overview and company description. We also have "Why Join Capriottis?" section with bullet list of reasons. That could be Benefits? Actually it's more like reasons to join, could be part of Benefits or separate section "Why Join". But we already have Benefits section for tangible benefits. The "Why Join" includes: Join a rapidly growing national restaurant brand, Opportunities for career advancement and leadership development, A supportive, team-focused workplace culture, A chance to lead a team delivering award-winning food and exceptional hospitality, At Capriotti’s, we believe in developing future leaders and promoting from within. That's more like benefits/culture. Could be merged into Benefits or a separate section "Why Join". But to keep few sections, we could incorporate those into Benefits as additional list items. However they are not typical benefits like insurance etc. Might be okay to add to Benefits. But we already have Benefits list from earlier: Competitive pay, Medical..., 401(k), FSAs, EAP, Referral bonus program, Opportunities for advancement and career growth. The "Why Join" includes similar items: Opportunities for career advancement and leadership development (duplicate), supportive culture, chance to lead team delivering award-winning food, developing future leaders. We could add those as additional list items under Benefits. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all points. Thus Benefits section will have list items: Competitive pay, Medical, dental, and vision insurance, 401(k) plan, Flexible Spending Accounts (FSAs), Employee Assistance Program (EAP), Referral bonus program, Opportunities for advancement and career growth, Join a rapidly growing national restaurant brand, Opportunities for career advancement and leadership development (maybe duplicate but we keep both?), A supportive, team-focused workplace culture, A chance to lead a team delivering award-winning food and exceptional hospitality, At Capriotti’s, we believe in developing future leaders and promoting from within. But note duplication: "Opportunities for advancement and career growth" appears both in benefits list and why join. We could keep both but it's duplicate; maybe we should deduplicate? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplicate lines: we should remove duplicated lines. It says: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove duplicated lines. So we need to deduplicate. Thus Benefits list: Competitive pay, Medical, dental, and vision insurance, 401(k) plan, Flexible Spending Accounts (FSAs), Employee Assistance Program (EAP), Referral bonus program, Opportunities for advancement and career growth, Join a rapidly growing national restaurant brand, A supportive, team-focused workplace culture, A chance to lead a team delivering award-winning food and exceptional hospitality, At Capriotti’s, we believe in developing future leaders and promoting from within. Now Responsibilities: we have subheadings with bullet points under each. We'll create a list of duties. Each duty could be a list item; we can include the subheading as bold text inside li. Let's extract: Lead and Develop Your Team: - Recruit, hire, train, and retain high-performing restaurant team members - Coach and mentor employees through Capriotti’s structured training programs - Build a positive, motivated, and team-oriented culture - Create schedules and manage staffing levels to support efficient operations Operational Excellence: - Ensure food quality, food safety, and presentation meet Capriotti’s brand standards - Oversee daily restaurant operations including food preparation, service, and cleanliness - Maintain compliance with all health, safety, and sanitation guidelines - Manage cash handling, deposits, and financial reporting accurately Guest Experience: - Deliver exceptional guest service and hospitality on every visit - Model Capriotti’s “CAPtivating Service” culture through leadership and example - Encourage suggestive selling and upselling to enhance the guest experience Business & Financial Management: - Monitor labor costs, food costs, and operational expenses - Analyze restaurant performance metrics and identify opportunities for improvement - Support local marketing initiatives and community engagement efforts Communication & Leadership: - Maintain professional communication with employees, guests, vendors, and leadership - Demonstrate adaptability and problem-solving in a fast-paced environment - Foster accountability, teamwork, and trust across the restaurant team We'll make each bullet as

    . Could also group under subheadings but not required. We'll just list all duties as li. Now Requirements / Qualifications / Skills: We have "What We’re Looking For" paragraph with bullet-like lines: - 2+ years of restaurant management experience (fast casual, quick service, or hospitality leadership preferred) - Proven ability to lead, coach, and motivate restaurant teams - Strong organizational, time management, and problem-solving skills - Excellent communication and interpersonal skills - Experience managing restaurant operations, scheduling, inventory, and labor - Comfortable using POS systems and basic computer software - Must be at least 18 years old Then Physical Requirements: - Ability to work in temperatures ranging from 0°F to 100°F - Ability to stand, walk, and move throughout the restaurant for extended periods - Ability to lift and carry up to 50 lbs. and balance up to 25 lbs. over distances of up to 50 feet We could combine these into Requirements section (including physical requirements). Or we could have a separate "Physical Requirements" section but not in standard headings; but we could still use

    for Physical Requirements if we want. The instruction says 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 follow similar pattern. Physical Requirements could be considered part of Requirements. We'll include them as list items under Requirements. Thus Requirements section list items: all those. Now About the role: we need a paragraph summarizing the role and company description. We'll combine the paragraphs: "Join a Fast-Growing, Award-Winning Restaurant Brand ..." and "Position Overview". Also maybe the opening sentences about seeking a motivated and experienced Restaurant General Manager. We'll include all that prose in

    under About the role. We must not repeat the job title as a heading. So we won't have

    Restaurant General Manager

    . Good. We must not put Job ID/requisition numbers as headings; none present. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. There's no explicit EEO etc. There's "Apply now, if you are a good fit for this role! We look forward to meeting you!" That's application instructions; we should remove that line. Also "Join a Fast-Growing, Award-Winning Restaurant Brand ..." is not boilerplate. Thus final HTML fragment:

    About the role

    ... (combined prose)

    Responsibilities

    • Lead and Develop Your Team: Recruit, hire, train, and retain high-performing restaurant team members; Coach and mentor employees through Capriotti’s structured