General Manager, Food Distribution Center

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules carefully: 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 4. Do NOT put Job ID / requisition numbers as headings 5. Preserve ALL substantive information 6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) 7. Include a section ONLY when the posting has real, specific content for it 8. Never emit a heading followed by filler/placeholder text 9. Never create Pay/Schedule/Benefits sections unless the posting actually states them 10. Prefer a few substantive sections over many thin ones 11. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the content: The posting has: - Company context (The Common Market description) - Role Description (overview) - Candidate Profile (ideal candidate description) - Snapshot of the Ideal Candidate (bullet points) - Who This Role Is Not for (bullet points) - Position Description with multiple subsections: - Site Leadership & Operational Ownership - Warehouse Operations - Transportation & Fleet Oversight - Food Safety & Quality (SQF Program Owner) - People Leadership & Team Development - Financial & Performance Management - Cross-Functional Leadership - Success in This Role Looks Like (bullet points) - Requirements/Qualifications (bullet points) - Location & Travel - Compensation & Benefits (with salary and benefits list) I need to organize this into logical sections. The rules mention specific heading names: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should map the content to these sections: - "About the role" could cover the company context and role description - "Responsibilities" could cover the Position Description subsections - "Requirements" or "Qualifications" for the qualifications list - "Benefits" for the benefits list - "Pay" for the salary - "Schedule" for location/travel info But I need to be careful: only include sections that have real content. The posting has specific content for all of these. Let me structure: 1. About the role - combine company context and role description 2. Responsibilities - the Position Description subsections 3. Qualifications - the Requirements/Qualifications list 4. Pay - salary 5. Benefits - benefits list 6. Schedule - location & travel I'll use

  for each section heading. For responsibilities, I'll have sub-sections but the rule says use

  for section headings. The Position Description has multiple subsections. I could make each a separate

  or group under Responsibilities with

  but the rule only mentions

  . I think I should use

  for each major responsibility area as they are distinct. Actually, the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It gives examples but doesn't forbid other headings. However, it says "Prefer a few substantive sections over many thin ones." So maybe I should group the Position Description subsections under a Responsibilities heading with

  • for each area, but that would lose detail. Better to have each as a subsection with

    ? But the example headings are specific. Let me re-read: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests these are the standard section headings to use. But the Position Description has 7 subsections. I could make "Responsibilities" an

    and then use

    for subsections? But the rule doesn't mention

    . It says "use

    for section headings". Might be okay to use

    for each major responsibility area as they are sections. But the instruction: "Prefer a few substantive sections over many thin ones." So maybe group them under Responsibilities with a list of areas, each with sub-bullets. Let me think: The Position Description has 7 areas, each with multiple bullet points. That's substantial. I could create an

    Responsibilities and then for each area, use a or

    but the rule says only

    for headings. Hmm. Actually, the rule says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say you cannot use other headings, but it gives examples. I think it's safe to use

    for each major section of the job posting. The Position Description subsections are essentially responsibilities. I'll make each a separate

    with the area name, but that might be too many. However, they are distinct and substantive. Alternatively, I could have one "Responsibilities"

    and then use

    with nested lists. But the rule says "use
    • for any list of duties/requirements/benefits". So I can have a list of responsibilities, each being a major area with sub-items. Let me structure:

      About the role

      Company context and role overview...

      Responsibilities

      • Site Leadership & Operational Ownership
        • Own overall performance...
        ...
      ...
      But that's nested lists. Might be okay. But the rule says "use
      • for any list of duties/requirements/benefits". It doesn't forbid nested lists. I'll do that for Responsibilities: a top-level list of the 7 areas, each with a nested list of duties. For Qualifications, a simple list. For Benefits, a list. For Pay, a paragraph with salary. For Schedule, a paragraph with location/travel. Also, there's "Snapshot of the Ideal Candidate" and "Who This Role Is Not for" - these could be part of About the role or separate. I'll include them in About the role or maybe a "Candidate Profile" section. But the example headings don't include Candidate Profile. I could fold into About the role. Similarly, "Success in This Role Looks Like" could be part of Responsibilities or a separate section. I'll include in Responsibilities or About the role. Let me draft. First, About the role: include company context, role description, candidate profile, snapshot, who this role is not for, success metrics. But that's a lot. Might be better to split: About the role (company and role overview), Candidate Profile (ideal candidate, snapshot, who not for), Success Metrics (success in this role). But the rule says prefer few substantive sections. I'll combine into About the role with sub-sections using and lists. Actually, the rule says "use

        for section headings" and "use

        • for any list". So I can have

          About the role

          then

          for prose, and

          for lists like snapshot and who not for. Let me write the HTML. I'll start with About the role:

          About the role

          The Common Market is a nonprofit social enterprise working to build a more resilient and equitable food system. Through a network of regional chapters, we connect family farmers to the institutions that need their food most, including schools, hospitals, universities, and community organizations. As our national network continues to grow, our ability to deliver on this mission depends on strong, reliable, and values-aligned operations. From warehouse teams and drivers to customer support and sales, our operational performance is critical to ensuring consistent, high-quality service. To support the continued growth and performance of our Philadelphia market, The Common Market is seeking a General Manager to lead site operations, develop frontline teams, and ensure excellence across warehouse, trucking, and food safety systems. This role will play a critical part in ensuring we consistently deliver on our commitments to customers, farmers, and communities.

          The General Manager is responsible for leading and owning the day-to-day and long-term performance of The Common Market's Philadelphia distribution facility, with oversight of warehouse operations, trucking, food safety, and frontline team leadership. This role sits at the intersection of operations, people, and performance. The General Manager ensures that systems are executed with consistency and discipline, while also building the structure, accountability, and team capability needed to support growth. Working in close partnership with the Executive Director, Sales, Customer Support, and National Operations, this role owns execution through others while ensuring alignment across teams. The General Manager is responsible for delivering operational results while continuously improving systems, processes, and team performance. This is a highly hands-on leadership role for someone who is energized by building strong teams, improving operations, and driving consistent execution in a fast-paced distribution environment. The General Manager holds primary accountability for site-level performance, including operational execution, team effectiveness, and cost management. This role is expected to operate with a high degree of autonomy in day-to-day decision-making, ensuring the facility and fleet run effectively without requiring constant executive oversight.

          Ideal Candidate Profile

          This role is best suited for a hands-on operational leader who thrives in a lean, fast-paced environment. The General Manager will directly oversee and work across multiple areas of the business—including procurement, warehouse operations, trucking, food safety, and people leadership—without large layers of specialized support. Successful candidates will be comfortable shifting between strategic leadership and hands-on problem solving while maintaining strong operational standards and accountability. The ideal candidate is an experienced operations leader who combines strong execution with the ability to build structure, develop people, and drive performance across a complex, multi-function operation. They are comfortable leading frontline teams, managing competing priorities, and ensuring that daily operations run smoothly while also identifying and implementing improvements. They are equally comfortable on the warehouse floor, reviewing performance metrics, directing staff, coordinating with cross-functional partners, scheduling repairs, and making real-time decisions that impact service, cost, and safety.

          • Operational Leader & Owner: Leads full-site operations with accountability for performance, safety, and execution
          • Frontline Team Builder: Develops supervisors and hourly staff, building a culture of accountability, safety, and strong performance
          • Food Safety Leader: Maintains strong command of SQF, HACCP, FSMA programs
          • Logistics & Fleet Operator: Oversees routing, delivery performance, maintenance, and fleet coordination
          • Business-Minded Operator: Understands cost, service levels, and operational tradeoffs
          • Problem Solver & Decision Maker: Navigates shifting priorities with strong follow-through
          • Professional Foundation: 7-12+ years relevant experience; 3-5+ years team leadership

          Who This Role Is Not For

          • Candidates who prefer strategy over execution
          • Candidates who avoid direct people management
          • Candidates who lack food or operational experience
          • Candidates who prefer predictable environments
          • Candidates seeking remote roles

          Success in This Role Looks Like