Sr. Operations Manager (Onsite - Shakopee, MN)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also must not create sections with filler like "commensurate with experience". Must only include sections where posting has real specific content. We need to parse the posting. Let's extract sections: - Position Overview: description of role. Could be "About the role". We'll put that content under

About the role

with

. - Essential Functions: list of duties/responsibilities. We'll put under

Responsibilities

with

• . - Competencies (Knowledge and Skills needed): list of skills. Could be

  Skills

  with
  . - Desired Qualifications: includes education, experience, etc. Could be split into Requirements (education, experience) and Qualifications maybe. But we need to decide: The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - Required Education: Bachelor's degree... or equivalent work experience. - Experience: 8+ years progressive operations leadership experience, preferrably within fast-paced distribution or warehouse environment; 5+ years hands-on inventory management expertise; experience in reverse logistics; proficiency with Microsoft Dynamics 365 WMS; ideal candidates extensive background in domestic and global supply chain; familiarity with ISO standards/FDA regulations; familiarity with Lean manufacturing; 2-3 years experience in regulated environment. - Travel: Approximately up to 25% Domestic/International; at times may be more depending on projects. - Other Information: Direct reports, Indirect reports, Location, Working Environment, Physical Demands, Position Type and Expected Hours of Work. - About Us: description of company. - What We Offer: benefits list. - Pay Transparency Notice: salary range $117,000 - $127,000/yr, discretionary bonus. - Also mention "Competitive benefits package, including annual bonuses, health insurance, a 401(k) plan, paid time off and paid holidays." - Also mention "We encourage you to apply..." etc (application instructions) - we must remove application instructions. - Also mention "We are committed to an inclusive recruitment process..." etc (EEO) - remove. - Also mention "Pay Transparency Notice:" we keep salary range. - Also mention "Disability Accommodation" - remove (EEO/legal). - Also mention "GN brings people closer..." etc (About Us) - we can keep as maybe not a required heading but could be part of About the role? Actually About Us is company overview, not role. The instruction says we should not include boilerplate like About Us? It says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not explicitly prohibited, but it's not a required heading. However we could include it under About the role? Might be better to keep as a separate section? The allowed headings list does not include About Us. So we should not create a heading for About Us unless we map it to one of the allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should incorporate About Us content maybe into About the role? But About the role is about the position, not company. However we could treat About Us as extra info not fitting headings; maybe we should omit it because it's not required heading and we should prefer few substantive sections. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit About Us if not needed. But we must preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot omit substantive info like company description. However maybe we can incorporate it into About the role as a brief note? But that would be adding info not originally there? It's not inventing; it's reusing. It's okay to include company overview under About the role? Might be stretching but permissible as it's still substantive. However the instruction says "About the role" heading for section headings (e.g. About the role, Responsibilities...). So we can put company overview under About the role? Might be odd but acceptable. Alternatively we could create a separate section not in list? The instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive list? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should stick to those. Thus we need to map all substantive info into those sections. Let's decide: - About the role: Position Overview + maybe About Us? We'll include Position Overview paragraph. - Responsibilities: Essential Functions list. - Requirements: Education and Experience (maybe also Travel? Travel could be under Schedule? Actually Travel is not schedule but maybe under Requirements? Could be under Requirements as "Travel". But we have a separate Schedule heading for work hours. Travel could be under Requirements or maybe under Schedule? Not exactly. Since we have Schedule for hours, we could put Travel under Requirements as a bullet. - Qualifications: Desired Qualifications beyond education/experience? Actually Desired Qualifications includes education, experience, etc. But we already used education/experience under Requirements. Could shift some to Qualifications: like proficiency with D365 WMS, ISO standards, Lean, regulated environment, global supply chain, etc. We'll decide. - Skills: Competencies list (knowledge and skills needed). - Benefits: What We Offer list (benefits). Also mention competitive benefits package etc. - Pay: Pay Transparency Notice salary range and discretionary bonus. - Schedule: Position Type and Expected Hours of Work (Mon-Fri first shift, some additional hours week and Saturdays). Also maybe location? Location could be under Schedule? Not really. Location could be under Requirements? But we have no heading for location. Could we put location under About the role? Might be okay. Or we could drop location? But we must preserve ALL substantive information. So we need to include location somewhere. Perhaps we can include location under About the role as a note. Or we could create a separate heading not in list? But instruction says use those headings; maybe we can still add other headings if needed? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not strict. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create any heading as long as it's meaningful. But they gave examples. Safer to stick to those examples but we could also add others like Location if needed. However they said "Prefer a few substantive sections over many thin ones." Adding Location as its own section would be thin. Better to incorporate location into About the role or Requirements. Thus we will put location in About the role paragraph. Physical Demands: Could be under Requirements? Or maybe under Schedule? Not exactly. Could be under Requirements as "Physical Demands". We'll add a bullet under Requirements. Working Environment: Could be under Requirements as well. Direct/Indirect reports: Could be under Requirements. Thus Requirements will contain many bullets: Education, Experience, Travel, Location, Direct reports, Indirect reports, Working Environment, Physical Demands, Position Type and Expected Hours of Work? Actually schedule is separate. We'll keep schedule separate. Thus: - About the role: Position Overview paragraph + maybe About Us? We'll include Position Overview only; we can add location note there. - Responsibilities: Essential Functions bullet list. - Requirements: Education, Experience, Travel, Location, Direct reports, Indirect reports, Working Environment, Physical Demands. - Qualifications: Desired Qualifications beyond education/experience: proficiency with D365 WMS, ISO standards/FDA, Lean, regulated environment, global supply chain, etc. Also maybe "Preferred" items. - Skills: Competencies list. - Benefits: What We Offer list + mention of competitive benefits package (health insurance, 401k, PTO, holidays, annual bonuses). - Pay: Salary range + discretionary bonus. - Schedule: Position Type and Expected Hours of Work (Mon-Fri first shift, some additional hours week and Saturdays). Now we need to ensure we don't include filler like "commensurate with experience". Not present. We must remove boilerplate: EEO, disability accommodation, application instructions, etc. Also remove duplicated lines: we see some duplication like "We encourage you to apply..." etc. Remove. Also remove "Pay Transparency Notice:" but we keep the salary range. Also remove "Compensation for roles at GN depend on a wide array of factors..." maybe that's boilerplate; we can keep brief? It's somewhat generic but still substantive? Might be considered boilerplate. Safer to remove generic sentences that are not specific to this role. The specific substantive is the salary range. We'll keep that. Also remove "GN participates in E-Verify..." etc. Also remove "We make life sound better..." etc (About Us) maybe we keep brief? But we already used About Us maybe not needed. We'll omit About Us to avoid extra section. Now craft HTML. We'll need to wrap each section in

  heading then content. For lists:

  • items. For prose:

    . We must not include or . Let's draft. About the role:

    The Sr. Operations Manager assists the director of the division with creating a culture of success and accountability, managing various production activities and supporting delivery of business results by driving performance against objectives or implementing overall functional strategy. This role may involve directly leading a divisional operations team, directly leading a team of supervisors/managers that manage direct labor over a large part of the division/workstream process, or indirectly supporting other ops areas with planning, directing and monitoring of work to meet established expectations, schedules, cost/wastage targets and quality standards. The position will be onsite at the Shakopee, MN facility starting October 2025 (relocating from Bloomington, MN).

    That captures position overview and location. Responsibilities: list essential functions. We need to extract each bullet from Essential Functions. Let's list them: - Responsible for strategic direction, execution, coordination, and success of their direct areas. - Provide effective, safe, and efficient working conditions, space, resources, and a positive environment that will maximize the effectiveness of employees in accomplishing the objectives of the department. - Responsible to provide senior-level support to areas of indirect responsibility. - Support Direct line leaders’ plans and expectations, by providing decision making, coaching when necessary, technical support, and labor support. - Manages the activities of first‐level managers and/or supervisors. - Mentor and develop Supervisors and Production leads to build bench strength and future managers. - Responsible for cost, compliance, product quality, efficiency, product turn-around time and employee engagement for all direct responsibility areas. - Develop continuous improvement culture and processes to achieve business strategy and goals relative to profitability, cost control, and increased efficiency. - Work with Director of division on developing strategic vision and execution for the entire divisional operations team. - Communicate with Director of division regarding employee issues, process issues, and other items that impact our success or offer opportunities. - Create a staffing plan for all areas, update as forecasts change, work with supervisors/managers to review and track open positions in their areas, be part of the