Restaurant General Manager

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules: 1. Use

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

• for lists of duties/requirements/benefits, and

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

  or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: - "About Wonder" - company description, not a section heading per rules (they want About the role, Responsibilities, etc.) - "About The Role" - this is the "About the role" section - "Responsibilities" - with multiple sub-sections: Lead Day-to-Day Operations with Excellence, Manage Team and Partner Performance, Drive Business Results & Own the P&L, Grow the Business, Manage Partnerships & Represent the Wonder Brand - "Who You Are" - this seems like qualifications/requirements - "Requirements" - specific requirements list - "Role Details" - includes Salary Range and Location - "Benefits" - list of benefits - Then boilerplate about AEDT, EEO, E-Verify - should be removed I need to structure this properly. The rules say use

  for section headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". I should create sections for: - About the role (from "About The Role") - Responsibilities (with sub-sections as lists) - Requirements (from "Who You Are" and "Requirements" - maybe combine) - Benefits (from "Benefits") - Pay (from "Salary Range") - Location (from "Location" in Role Details) But note: "Who You Are" seems like qualifications, and "Requirements" is a separate list. I could combine them under "Requirements" or have "Qualifications" and "Requirements". The rules mention both "Requirements" and "Qualifications" as possible headings. I'll use "Requirements" for the combined list. Also, "Role Details" has Salary Range and Location. Salary Range goes to Pay section, Location could be a short

  or part of Pay? The rules say fold minor metadata into a short

  or drop it. Location is important, maybe include in a short

  at top or in Pay section? But Pay section is for pay. Could create a "Details" section? Not in the allowed headings. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Location isn't listed. I'll include location in a short

  maybe after About the role or in Pay? Better to include as a short

  somewhere. Also, the posting has "Note: Some of our benefits vary by state..." - that's part of benefits. I need to remove the boilerplate at the end: "Wonder uses an AEDT...", "At Wonder, we build the best teams...", "As part of our commitment...". Now, let's structure the HTML. First, maybe a short

  for location: "Location: Springfield, NJ". But the rules say do not put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Location is metadata, so I'll include a

  at the beginning or end. I'll start with About the role section. Then Responsibilities: each sub-section can be a

  ? But rules say use

  for section headings. The sub-sections are part of Responsibilities. I could make them

  but the rules only mention

  for section headings. However, the example headings are top-level. The sub-sections are not top-level sections. I think I should keep them as part of the Responsibilities list, maybe using

  with nested lists or just list items with bold text. But the rules say use
  • for any list of duties/requirements/benefits. The responsibilities are listed as bullet points under each sub-heading. I can create a list for each sub-heading, but that would be many lists. Alternatively, I can combine all responsibilities into one big list, but the sub-headings provide structure. I think I'll use

    for sub-sections within Responsibilities? The rules don't forbid other heading levels, but they say "use

    for section headings". It doesn't say I cannot use

    . However, to be safe, I'll keep the sub-sections as within list items or as separate

    ? The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say I cannot use other headings. But to keep it simple, I'll make the sub-sections as

    inside the Responsibilities section. That seems semantic. But the output should be a fragment. I'll do:

    About the role

    ...

    Responsibilities

    Lead Day-to-Day Operations with Excellence

    • ...

    Manage Team and Partner Performance

    • ...

    ... etc. That seems good. For Requirements: combine "Who You Are" and "Requirements". "Who You Are" is a list of qualifications. "Requirements" is a list of specific requirements. I'll put them under one

    Requirements

    with two sub-sections maybe:

    Qualifications

    and

    Requirements

    ? But the rules say use

    for section headings like Qualifications. Could make two separate

    sections: "Qualifications" and "Requirements". But the posting has "Who You Are" and "Requirements". I'll map "Who You Are" to "Qualifications" and "Requirements" to "Requirements". That matches the allowed headings. Benefits: list. Pay: salary range. Schedule: not mentioned, so omit. Location: include as a short

    maybe after About the role or at the end. Now, let's write the HTML. I need to preserve all substantive information. So I must include all bullet points exactly. Let's extract content. About the role: The paragraph under "About The Role": "As a General Manager, you’ll be the business leader of a Wonder location overseeing a shared kitchen that serves multiple brands, channels, and delivery methods. This role goes far beyond food service. You will lead a multifunctional team, manage cross brand collaboration in a single facility, and own the local P&L like a true General Manager. Success in this role requires operational dexterity: you may be navigating staffing decisions one moment and vendor relations the next. You’ll manage both employees and nonemployees (contract partners), drive business results, and represent Wonder in the local partner ecosystem. This is a unique opportunity for an experienced leader from operations, logistics, eCommerce, hospitality, or similar domains to build, manage and grow a complex operation." Responsibilities: five sub-sections with bullet points. Lead Day-to-Day Operations with Excellence: - Oversee all aspects of day-to-day operations across kitchen, service, and fulfillment channels (dine-in, pickup, delivery) - Optimize labor deployment, throughput, and service execution to meet evolving business needs - Ensure strict adherence to labor, food safety, team member safety, and compliance standards - Monitor and manage inventory accuracy, waste reduction efforts, and product shelf life adherence - Maintain high operational readiness by forecasting demand, resolving obstacles, and adjusting workflows in real-time - Monitor customer feedback and operational trends to make data-informed decisions that drive service excellence - Set and drive key operational KPIs, ensuring alignment across internal and external contributors Manage Team and Partner Performance: - Hire, onboard, coach, schedule, and develop a high-performing team of hourly employees and shift leaders - Lead a blended on-site workforce of internal employees and external partners (contracted or brand-affiliated staff) - Create a collaborative, on-brand environment where Wonder and third-party teams operate seamlessly under one roof - Address performance issues respectfully and quickly using coaching and performance tools - Ensure compliance with state and federal labor laws Drive Business Results & Own the P&L: - Take full ownership of the location’s P&L and use data to influence labor efficiency, food costs, and operational margin - Establish and track KPIs related to guest experience, order accuracy, throughput, and financial performance - Partner cross-functionally (with finance, culinary, procurement, logistics, etc.) to identify cost-saving and revenue-driving opportunities - Build action plans around local performance insights, customer feedback, and operational trends Grow the Business: - Own and drive company talent pipelines with a strong focus on succession building and readiness - Select, develop, and deploy certified trainers to support new store openings and maintain consistent onboarding of new hires - Actively mentor and coach managers-in-training, preparing them for potential transfers or leadership roles at other locations - Serve as a hands-on role model leader, modeling company values and reinforcing performance standards that promote personal and professional growth - Anticipate future business needs and strategically align staffing, scheduling, and development efforts to ensure the organization is prepared for growth - Contribute to company innovation and evolution by sharing feedback, piloting new initiatives and championing best practices for company-wide rollout Manage Partnerships & Represent the Wonder Brand: - Serve as the on-site point of contact for brand partners, vendors, and contracted operators - Nurture relationships with local stakeholders to foster trust, partnership, and operational consistency - Ensure that each brand operating in the kitchen adheres to Wonder’s service and food quality standards to deliver a flawless customer experience - Represent Wonder in local community and business interactions, helping to grow our reputation and customer base Qualifications (Who You Are): - A business operator with at least 3 years of experience leading high-volume, complex operations in sectors like logistics, field-based retail, hospitality, food, or eCommerce - Experience in fast-growing, operationally complex environments such as high-growth startups, multi-unit retail, or on-demand services - Proven leadership background and track record of progressive growth and advancement - Demonstrated success in full P&L ownership, KPI management, and driving operational results - A proactive problem solver who thrives in fast-paced, ambiguous environments - Comfortable managing hybrid workforces across employees and contracted vendors/partners - Known for cross-functional fluency—able to influence and collaborate across finance, HR, logistics, culinary, and partner organizations - Obsessed with customer service, quality, accountability, and results Requirements: - Must be at least 18 years of age and legally authorized to work in the US - Must be able to lift up to 50 pounds and stand for extended periods - Must have open availability, including nights and weekends - Food Manager Certificate as required by State, County or Local Health Departments - This list of qualifications and requirements also reflects the qualifications and