Sr. Manager - Facilities & Automation Management
About the role
with. Responsibilities: The "What You'll Do" section includes bullet points: Strategic Leadership & Team Development, Systemic Process Improvement & Reporting, Automation & Equipment Management, Financial Management & Project Planning, Compliance & Availability. We need to list duties as
- . Should we break each bullet into separate li? Probably each bullet as a li. The bullet text includes multiple sentences; we can keep as is.
Requirements: "What You'll Need Required:" includes required degree, alternative experience, certifications, etc. That's requirements. We'll list as
- .
Qualifications: Might be overlapping with requirements; but we can treat "What You'll Need" as Requirements. Qualifications maybe certifications? But we can combine. However we need to avoid thin sections. We'll have Requirements section with list.
Skills: Could be extracted from required: engineering-minded familiarity with electrical/mechanical, PLCs, conveyor systems, robotics, PIT PMs, ticketing systems like Limble, data analysis, budgeting, vendor negotiation, communication, problem solving, etc. Could list as Skills.
Benefits: Not mentioned in posting. No benefits details. So we should NOT include Benefits section.
Pay: Not mentioned. So omit.
Schedule: Not mentioned (maybe 50% travel flexibility required). That's schedule? Travel flexibility is not schedule. No explicit schedule. So omit.
We also need to include maybe "About ShipMonk" but that's company description; not required heading. We could include as part of About the role? Probably not needed. The instruction: use headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only include those headings if content exists. We'll include About the role, Responsibilities, Requirements, Skills. Possibly Qualifications if we have distinct content beyond Requirements. The posting includes certifications etc. Could treat as Qualifications. But we already have Requirements covering degree, experience, certifications. Qualifications could be things like "Proven experience in managing maintenance teams across multiple locations..." etc. That's also requirements. Might be overlapping. To avoid thin sections, we can combine Requirements and Qualifications into one Requirements section. But we need to follow instruction: use headings for those categories if content exists. It's okay to have only some headings. We'll include About the role, Responsibilities, Requirements, Skills.
Now we need to preserve all substantive information, not invent or summarize away detail. Must not omit any substantive info. So we need to include all points from the posting.
Let's extract all substantive info:
Overview paragraph (first paragraph after "Overview").
What You'll Do bullet points:
- Strategic Leadership & Team Development:
Manage maintenance operations across multiple buildings, each supported by in-house maintenance technicians.
Lead, monitor the performance, and coach the maintenance team, developing their troubleshooting skills to move beyond basic part replacement.
Act as the first line of defense for complex issues, teaching technicians to use data and diagnostic tools to identify root causes.
Ensure each building is adequately staffed and properly equipped to meet operational needs, with a focus on future-proofing skills for robotics and automation.
- Systemic Process Improvement & Reporting:
Develop and implement systemic maintenance reporting and escalation protocols.
Ensure clear visibility into equipment status, severity levels, and resolution timelines to prevent unexpected downtime.
Oversee maintenance ticketing systems to track and resolve issues efficiently.
Lead by example in keeping open lines of communication with operations stakeholders regarding open issues.
Implement Standard Work procedures for maintenance technicians to ensure consistency and accountability across all sites.
- Automation & Equipment Management:
Ensure the smooth, ongoing operation of all facilities in the region, prioritizing safety and efficiency.
Partner with LP & Safety department on policy development and ensuring adherence to OSHA and safety regulations.
Perform and monitor preventive maintenance on Powered Industrial Trucks (PITs), advanced conveyor systems, and future automation equipment/robotics.
Implement a predictive maintenance strategy, leveraging data analysis to identify and escalate potential issues before they affect operations.
Take ownership over ensuring the facilities and equipment are supporting shared operational goals.
- Financial Management & Project Planning:
Manage the financial side of maintenance operations, ensuring accountability for spending and tracking expenditures against the region’s maintenance budget.
Manage vendor relationships, standard of work, and negotiate contracts for cost efficiency and quality.
Develop and manage the annual budget for the region's maintenance operations.
- Compliance & Availability:
Ensure the timely and accurate completion of facility inspections and maintenance reports.
Be available after hours to address emergencies and provide support to the facilities.
Communicate vertically with senior leadership and other departments to ensure alignment on goals and objectives.
What You'll Need Required:
- A Bachelor's degree in Engineering (Mechanical, Electrical, Civil, or Industrial), Facilities Management, Construction Management, or a related technical/business field.
- Alternatively, demonstrable equivalent experience (10+ years of progressive leadership experience in facilities/maintenance in complex industrial environments) may be considered, but a degree is strongly preferred to ensure a solid foundation in engineering and management principles.
- Certifications: Relevant professional certifications are highly valued, such as a Certified Facility Manager (CFM) or Facility Management Professional (FMP) certification from the International Facility Management Association (IFMA).
- Proven experience in managing maintenance teams across multiple locations with an emphasis on coaching and skill development.
- Strong, engineering-minded familiarity with both electrical and mechanical sides of automation, particularly with complex conveyor systems, PLCs, and a vision for integrating future robotics.
- Knowledge of and experience working with PIT PMs, conveyor system PMs, and ticketing systems like Limble.
- Demonstrated experience in developing and implementing systemic reporting mechanisms and structured escalation protocols.
- Strong financial management skills, including the ability to manage budgets, negotiate vendor contracts, control costs, and track maintenance spending.
- Excellent communication skills, with a strong focus on vertical communication to senior leadership.
- Partner effectively and in timely manner with cross-functional teams, including ops, IT, inventory, transportation, etc.
- The ability to anticipate maintenance issues using data analysis and address them proactively through systemic fixes, not just quick patches.
- A "Builder" mentality and a "Change the Score" leader. A desire to build mechanisms from scratch and elevate the skill level of the entire department.
- 50% travel flexibility required, with availability to visit regional facilities as needed.
- Strong problem-solving skills and the ability to make critical decisions under pressure in a fast-paced environment.
About ShipMonk paragraph (company description) - could be omitted as not required heading but maybe we can include as part of About the role? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
- Strategic Leadership & Team Development: Manage maintenance operations across multiple buildings, each supported by in-house maintenance technicians. Lead, monitor the performance, and coach the maintenance team, developing their troubleshooting skills to move beyond basic part replacement. Act as the first line of defense for complex issues, teaching technicians to use data and diagnostic tools to identify root causes. Ensure each building is adequately staffed and properly equipped to meet operational needs, with a focus on future-proofing skills for robotics and automation.
- Systemic Process Improvement & Reporting: Develop and implement systemic maintenance reporting and escalation protocols. Ensure clear visibility into equipment status, severity levels, and resolution timelines to prevent unexpected downtime. Over
or drop it." It doesn't forbid including company description; but we should only include sections for the headings list. Could we include a
about ShipMonk under About the role? Probably not needed. The overview already includes role description. The company description may be considered extra but not required to preserve? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to preserve all substantive information from the posting. That includes the About ShipMonk paragraph, Core Values, etc. However those are not under the headings list; but we could still include them as generic
without heading? 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 says use those for those specific headings. It doesn't say we cannot have other headings or paragraphs. However to be safe, we could include them as
without heading, but we need to preserve all substantive info. The overview already includes some of the role description; the About ShipMonk and Core Values are substantive. We should include them maybe as a
after the sections, without a heading, or we could add a heading like "About ShipMonk" but that's not in the allowed list; but maybe it's okay? The 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 exclusive list. But 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 could add a heading for About ShipMonk if there is content. However they gave examples of headings; they didn't forbid others. But to be safe, we could just include the content as
without a heading. The instruction didn't say we cannot have other headings; but they said use
for section headings (e.g. ...). It implies we should use h3 for headings, but we could still use h3 for other headings if we want. However they might check for only those headings. Safer to stick to the allowed headings and put extra info as
under maybe "About the role" or as a separate
without heading. But "About the role" already used for role overview; we could extend that
to include also company description? Might be mixing. Better: Keep About the role as role overview only. Then after sections, add a
containing the About ShipMonk paragraph and Core Values etc. That preserves all info without extra headings. We must not include boilerplate like EEO etc. The posting includes "ShipMonk is an equal opportunity employer..." which is boilerplate; we should remove that. Also remove duplicated lines, cookie/navigation/legal etc. There's none. Now craft HTML. We'll produce:
About the role
As the Sr. Facilities & Automation Maintenance Manager, you will be a strategic leader responsible for overseeing complex maintenance operations across multiple ShipMonk operated fulfillment centers. The primary mission is to ensure all buildings and automation systems remain fully operational and efficient. This includes leading a team of dedicated Maintenance Technicians, shifting the culture towards proactive mechanisms supporting our next phase of growth, data-driven maintenance, and ensuring a safe, functional working environment for all team members. You will be a proactive, engineering-minded leader with a keen eye for anticipating maintenance needs, driving automation strategy, and quickly addressing operational concerns with systemic solutions and mechanisms.
Responsibilities