Assistant General Manager

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Content: - Intro: "On-site - Pittston, Pennsylvania The roleRunning a ShipMonk fulfillment center means managing thousands of daily decisions, from inbound receiving to outbound accuracy, while keeping a team of 40+ people moving in the same direction. As AGM, you're the operator who makes that happen every shift.You'll own the P&L, drive KPIs, and build the layer of supervisory leadership that means the floor doesn't stop when you step away. This is a high-accountability role with real visibility into how the business performs." That's about the role. Then "What you'll own:" with bullet list: - Daily operations. Inbound, outbound, inventory accuracy, equipment maintenance, and sanitation standards. You set the expectations and hold the team to them. - P&L and KPIs. You track the numbers that matter, labor cost, throughput, error rates, and you understand what levers to pull when they're off. - People and culture. You hire supervisors, develop frontline leads, and build a team that doesn't need you to solve every problem. You run performance conversations directly and consistently. - Cross-functional coordination. You work with customer service, sales, and other facility leaders to make sure warehouse activity doesn't create problems downstream. Then "What you bring:" bullet list: - 6 to 8 years in fulfillment, distribution, or supply chain operations, including leading teams of 40 or more - Experience managing a facility budget and hitting operational KPIs - Comfort with WMS and enterprise tools (Excel, project management software, process documentation) - A track record of building supervisory layers, not just managing individual contributors - Strong enough communication to present to executives and work a warehouse floor in the same day - Lean Six Sigma certification is a plus. A degree helps, but equivalent operational experience is fine. Then "What makes ShipMonk different:" paragraph about 80% role definition etc. Then "Perks:" list: - Full medical, dental, and vision coverage. - Unlimited PTO. - 401(k). - Referral bonus program. Then "About ShipMonk:" paragraphs describing company. Then "Why ShipMonk?" list of differentiators. Then "Our Core Values" list. Then EEO statement (remove). We need to decide sections. We have content for: - About the role (intro paragraph) - Responsibilities (What you'll own) - Requirements (What you bring) maybe combine with Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map: About the role: intro paragraph. Responsibilities: bullet list of what you'll own. Requirements: maybe the "What you bring" list (experience, etc.) Qualifications: maybe the "Lean Six Sigma certification is a plus. A degree helps, but equivalent operational experience is fine." Could be part of Requirements but we can separate. Skills: maybe "Comfort with WMS and enterprise tools (Excel, project management software, process documentation)" and "Strong enough communication to present to executives and work a warehouse floor in the same day" could be Skills. But we need to avoid thin sections. Prefer few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But headings are prescribed; we can omit sections if no real specific content. So we need to decide which sections have real content. We have content for About the role, Responsibilities, Requirements (experience), Skills (tools, communication), Benefits (perks), maybe Pay and Schedule not present (no mention). So we omit Pay and Schedule. Qualifications maybe we can include as part of Requirements or separate if we have distinct content: "Lean Six Sigma certification is a plus. A degree helps, but equivalent operational experience is fine." That's qualification-like. Could be placed under Qualifications. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. We must not include empty sections. 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. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "About ShipMonk:" etc? That's substantive about company; we could include maybe under About the role? But we already have About the role intro. The "About ShipMonk:" and "Why ShipMonk?" and "Our Core Values" are also substantive but maybe not required for the job posting? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that info somewhere. Where? Could be under a section like "About the company" but not in prescribed headings. We could add a section like "About ShipMonk" but not in list of allowed headings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. But we must preserve all substantive info; we could incorporate company info into About the role or maybe under Responsibilities? Not ideal. Maybe we can create a section "About the company" but that's not in the list; risk of being considered not following instruction. However instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. But they also say "Prefer a few substantive sections over many thin ones." So we could add a section "About ShipMonk" if we have substantive content. But we must ensure we don't create thin sections. We have substantive content about ShipMonk: description, differentiators, core values. That's a lot. Could be its own section. Thus we could have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, About ShipMonk. But 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, just gives examples. So we can add About ShipMonk. We must not repeat job title as heading. Already not. We must not put Job ID etc. Now we need to extract all substantive info and format. Let's gather: About the role paragraph: "Running a ShipMonk fulfillment center means managing thousands of daily decisions, from inbound receiving to outbound accuracy, while keeping a team of 40+ people moving in the same direction. As AGM, you're the operator who makes that happen every shift. You'll own the P&L, drive KPIs, and build the layer of supervisory leadership that means the floor doesn't stop when you step away. This is a high-accountability role with real visibility into how the business performs." Note there is also "On-site - Pittston, Pennsylvania" location. Should we include location? It's substantive. Could be part of About the role paragraph or separate short p. We'll include as a short paragraph maybe. Responsibilities bullet list: each bullet includes a sentence. We need to preserve all detail: For each bullet we have: - Daily operations. Inbound, outbound, inventory accuracy, equipment maintenance, and sanitation standards. You set the expectations and hold the team to them. - P&L and KPIs. You track the numbers that matter, labor cost, throughput, error rates, and you understand what levers to pull when they're off. - People and culture. You hire supervisors, develop frontline leads, and build a team that doesn't need you to solve every problem. You run performance conversations directly and consistently. - Cross-functional coordination. You work with customer service, sales, and other facility leaders to make sure warehouse activity doesn't create problems downstream. Requirements (What you bring): - 6 to 8 years in fulfillment, distribution, or supply chain operations, including leading teams of 40 or more - Experience managing a facility budget and hitting operational KPIs - Comfort with WMS and enterprise tools (Excel, project management software, process documentation) - A track record of building supervisory layers, not just managing individual contributors - Strong enough communication to present to executives and work a warehouse floor in the same day - Lean Six Sigma certification is a plus. A degree helps, but equivalent operational experience is fine. We could split: Requirements: first two bullets (experience, budget). Qualifications: Lean Six Sigma certification plus degree note. Skills: comfort with WMS/tools, communication. But we also have "Comfort with WMS and enterprise tools (Excel, project management software, process documentation)" which is a skill. And "Strong enough communication to present to executives and work a warehouse floor in the same day" also skill. Thus: Requirements: 6-8 years experience, leading teams 40+, experience managing facility budget and hitting operational KPIs. Qualifications: Lean Six Sigma certification is a plus. A degree helps, but equivalent operational experience is fine. Skills: Comfort with WMS and enterprise tools (Excel, project management software, process documentation); Strong enough communication to present to executives and work a warehouse floor in the same day; A track record of building supervisory layers, not just managing individual contributors (maybe also skill). Actually building supervisory layers is more of a qualification/experience. Could be under Requirements or Qualifications. Let's put under Requirements as it's experience. But we need to avoid duplication. Let's decide: Requirements: - 6 to 8 years in fulfillment, distribution, or supply chain operations, including leading teams of 40 or more - Experience managing a facility budget and hitting operational KPIs - A track record of building supervisory layers, not just managing individual contributors Qualifications: - Lean Six Sigma certification is a plus - A degree helps, but equivalent operational experience is fine Skills: - Comfort with WMS and enterprise tools (Excel, project management software, process documentation) - Strong enough communication to present to executives and work a warehouse floor in the same day Benefits (Perks): - Full medical, dental, and vision coverage - Unlimited PTO - 401(k) - Referral bonus program About ShipMonk: include description, differentiators, core values. We need to preserve all substantive info from those sections. Let's extract: About ShipMonk paragraph: "ShipMonk isn't just a 3PL; we're a growth partner for merchants. We provide cutting-edge technology and a network of owned and operated fulfillment centers that empower high-growth ecommerce and DTC brands to stress less and grow more. With over 2,500 employees across five countries, we're on a mission to revolutionize fulfillment by providing everything from the fastest click-to-delivery and real-time inventory to custom solutions, all with a merchant-first mindset." Why ShipMonk? list of five differentiators: - Global Fulfillment Network: Our 12+ owned and operated fulfillment centers span the US, Canada, the U.K., and Mainland Europe. We never outsource, ensuring quality and consistency. - Proprietary Technology: We've eliminated the need for tribal knowledge with our AI-powered platform. It provides a real-time, unified view of inventory and orders, giving our merchants the control and visibility they need to succeed. - Unrivaled Support: We provide