IT / OT Infrastructure Manager
Re:Build Manufacturing · New Kensington, PA · 1 mo ago
HybridFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Re:Build" (company description) then "Who we are looking for", "The Role", "What you get to do!", "What you bring to the Team", "Additional Knowledge & Strengths Required", "Nice-to-Have", "Location", "The BIG payoff". We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We must not repeat job title as heading. We must not include Job ID etc. We must remove boilerplate (EEO, accommodations, etc). Also remove duplicated lines.
We need to decide which sections to include:
- About the role: Could be the description of role (The Role). Could also include "About Re:Build" as company description but not required. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content.
We have content about responsibilities: "What you get to do!" includes bullet points of duties. That maps to Responsibilities.
We have qualifications: Education & Experience, Deep Core Technical Expertise, Additional Knowledge & Strengths Required, Nice-to-Have. Could map to Requirements, Qualifications, Skills. We need to decide.
We have benefits: "The BIG payoff" includes ownership sharing, financial rewards, etc. That's benefits. Also maybe location/hybrid schedule info: "Location: Candidates must be local... hybrid – 3 days onsite / 2 days remote." That's schedule (or location). Could be Schedule section.
We have no explicit Pay info. So we should not create Pay section.
We have no explicit Benefits beyond ownership; but "The BIG payoff" is about ownership and financial rewards, that's benefits. So we can include Benefits.
We need to preserve all substantive information, not invent or summarize away detail. Must not create sections with filler like "not specified". So we include only sections with real content.
Thus we can have:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content.
We have content about responsibilities: "What you get to do!" includes bullet points of duties. That maps to Responsibilities.
We have qualifications: Education & Experience, Deep Core Technical Expertise, Additional Knowledge & Strengths Required, Nice-to-Have. Could map to Requirements, Qualifications, Skills. We need to decide.
We have benefits: "The BIG payoff" includes ownership sharing, financial rewards, etc. That's benefits. Also maybe location/hybrid schedule info: "Location: Candidates must be local... hybrid – 3 days onsite / 2 days remote." That's schedule (or location). Could be Schedule section.
We have no explicit Pay info. So we should not create Pay section.
We have no explicit Benefits beyond ownership; but "The BIG payoff" is about ownership and financial rewards, that's benefits. So we can include Benefits.
We need to preserve all substantive information, not invent or summarize away detail. Must not create sections with filler like "not specified". So we include only sections with real content.
Thus we can have:
About the role
maybe include company mission? But "About the role" could be a brief description of the role: The IT Infrastructure Manager leads... We have "Who we are looking for" and "The Role". Could combine.
Better: Use About the role for a short paragraph summarizing the role (from "Who we are looking for" and "The Role").
Responsibilities: from "What you get to do!" bullet list.
Requirements: Education & Experience (Bachelor's, 7+ years, 5+ years leading, certifications plus). Could also include Deep Core Technical Expertise as Requirements.
Qualifications: maybe Additional Knowledge & Strengths Required (cybersecurity, CAD, ITIL, AI tools, documentation, team development, learning). Could be Qualifications.
Skills: maybe Nice-to-Have (Lean Manufacturing, manufacturing OT networking). Or we could treat Skills as technical skills list (Servers & Virtualization etc). Actually Deep Core Technical Expertise is a list of technical skills. That could be Skills.
Benefits: The BIG payoff (ownership, financial rewards, share in success). Also maybe mention hybrid schedule? That's schedule.
Schedule: Location/hybrid info.
We must not duplicate content. Need to ensure we preserve all substantive info.
Let's extract content:
Company description: "About Re:BuildAt Re:Build, our mission is to ensure the next generation of important products are made, at scale, in America. We are laying the foundation for a better future for our customers, employees, and communities by revitalizing America's manufacturing base and creating meaningful jobs across the country, including in historically deindustrialized regions.We operate an advanced, end-to-end manufacturing platform that partners with industrial companies and innovators to take products from first concept to full-scale production in critical verticals including aerospace and defense, electrification, medical, energy and environment, and robotics and automation.The way we operate is as important as the work we do. It's guided by The Re:Build Way, 16 principles that shape how we collaborate with each other, partner with our customers and vendors, and contribute to the communities where we operate. (link to The Re:Build Way principles)". This is company overview; could be included in About the role? Possibly not needed but could be part of About the role. The instruction: "About the role" heading for section headings. It didn't say we must include company description; we can include it if we want. It's substantive. We'll include a brief paragraph under About the role summarizing the role and maybe company mission.
But we must not repeat job title as heading. That's fine.
Now "Who we are looking for": "We’re seeking an IT Infrastructure Manager to lead and evolve the technology foundation that enables a positive, reliable, and productive end-user experience for all Re:Builders. This role blends deep infrastructure expertise with strong people leadership, emotional intelligence, and a continuous-improvement approach.The ideal candidate is resilient, empathetic, and outcome-driven—someone who can balance operational excellence with long-term architectural thinking while building trust across IT and the business."
That's a good summary for About the role.
"The Role": "The IT Infrastructure Manager is responsible for leading the infrastructure team, overseeing day-to-day operations, and owning infrastructure design and architecture across Re:Build. This role ensures systems are secure, available, scalable, and performant, while continuously improving the way infrastructure services are delivered.You’ll partner closely with business leaders, IT peers, and vendors to solve today’s infrastructure challenges and design solutions that support future growth."
That could also be part of About the role or Responsibilities. But we already have responsibilities list.
Now "What you get to do!" includes bullet points under headings: Leadership & Team Management, Infrastructure Operations & Reliability, Architecture & Engineering, Continuous Improvement & Metrics, Planning, Governance & Vendors. Each with sub-bullets.
We need to output - for any list of duties/requirements/benefits. So we can flatten these into a single list? Or we could keep subheadings? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. It doesn't forbid headings inside list? Probably better to keep each duty as
- and maybe include sub-bullets as nested
. But we must preserve all substantive information. We could keep the headings as plain text inside - and then nested list for subpoints.
Simplify: For each major duty heading, we can have
- Leadership & Team Management: ... then nested
for subpoints.
But the instruction didn't forbid using inside - . It's okay.
Now "What you bring to the Team": includes Education & Experience, Deep Core Technical Expertise. That's requirements/qualifications.
"Additional Knowledge & Strengths Required": list.
"Nice-to-Have": list.
"Location: Candidates must be local to one of our Re:Build locations, or willing to relocate (hybrid – 3 days onsite / 2 days remote)." That's schedule/location.
"The BIG payoff": ownership share, financial rewards.
We must not include EEO etc.
Now decide sections:
- About the role: combine "Who we are looking for" + "The Role" maybe short paragraph.
- Responsibilities: the "What you get to do!" bullet list.
- Requirements: Education & Experience (Bachelor's, 7+ years, 5+ years leading, certifications plus). Could also include Deep Core Technical Expertise as Requirements? But maybe better as Skills.
- Qualifications: Additional Knowledge & Strengths Required.
- Skills: Deep Core Technical Expertise (list of technical skills). Could also include Nice-to-Have as Skills? But Nice-to-Have is separate.
- Benefits: The BIG payoff.
- Schedule: Location/hybrid.
We must not create sections with filler. All have content.
Now we need to ensure we don't repeat content across sections. Let's extract each piece.
About the role paragraph:
From "Who we are looking for": "We’re seeking an IT Infrastructure Manager to lead and evolve the technology foundation that enables a positive, reliable, and productive end-user experience for all Re:Builders. This role blends deep infrastructure expertise with strong people leadership, emotional intelligence, and a continuous-improvement approach.The ideal candidate is resilient, empathetic, and outcome-driven—someone who can balance operational excellence with long-term architectural thinking while building trust across IT and the business."
From "The Role": "The IT Infrastructure Manager is responsible for leading the infrastructure team, overseeing day-to-day operations, and owning infrastructure design and architecture across Re:Build. This role ensures systems are secure, available, scalable, and performant, while continuously improving the way infrastructure services are delivered.You’ll partner closely with business leaders, IT peers, and vendors to solve today’s infrastructure challenges and design solutions that support future growth."
We can combine into a paragraph.
Now Responsibilities: list of duties.
We need to capture all bullet points under each heading.
Let's extract:
Leadership & Team Management
- Lead, coach, and develop the Infrastructure team, fostering a positive, accountable, and service-oriented culture
- Manage staffing, scheduling, priorities, performance reviews, and professional development plans
- Ensure teams operate cohesively with minimal friction; mentor and support others across IT as needed
Infrastructure Operations & Reliability
- Oversee all infrastructure operations, processes, and service delivery
- Ensure service levels meet or exceed agreed targets; manage escalations and breached SLAs
- Own and lead critical incident management processes and post-incident improvements
- Support the team with incident resolution, service requests, and project execution when needed
Architecture & Engineering
- Design, review, and approve infrastructure architectures using a collaborative, business-aligned approach
- Lead design, build, test, and support activities for infrastructure solutions across the enterprise
- Ensure infrastructure standards, patterns, and documentation are current and effective
Continuous Improvement & Metrics
- Define, validate, and communicate important infrastructure metrics and performance indicators
- Drive continuous improvement across people, processes, and systems using data-driven methods
- Maintain SOPs, work instructions, and knowledge base content; communicate changes effectively
Planning, Governance & Vendors
- Contribute to IT planning, budgeting, forecasting, and vendor management
- Ensure infrastructure aligns with security, compliance, and regulatory requirements
- Monitor end-user satisfaction and feedback, translating insights into actionable improvements
Now Requirements: Education & Experience
- Bachelor’s degree in Information Technology or a related field, or equivalent practical experience
- 7+ years of experience designing, building, supporting, and troubleshooting enterprise infrastructure
- 5+ years of experience leading and managing infrastructure teams
- Current IT industry certifications are a plus
Now Qualifications: Additional Knowledge & Strengths Required
- Cybersecurity practices and compliance frameworks (CMMC, GCC High, AWS GovCloud, FedRAMP)
- Familiarity with CAD systems
- ITIL processes and service management concepts
- Experience employing AI tools to streamline and improve IT operations
- Strong documentation skills (architecture, policies, runbooks, procedures)
- Demonstrable ability to develop teams, hold accountability, and create an outcome-driven culture
- Proven ability to learn new technologies quickly and apply them effectively
Now Skills: Deep Core Technical Expertise list
- Servers & Virtualization: Server hardware, Microsoft Server, VMware, Hyper-V
- Cloud Platforms: Microsoft Azure, AWS, Google Cloud
- Core Services: Active Directory, DNS, DHCP, file/print, certificates, identity services
- Storage, Backup & Recovery
- Complex Environments: Multi-tenant, multi-cloud, multi-domain, multi-forest
- Endpoint & Device Management: PCs, Macs, peripherals, printers, Intune
- Microsoft 365 & End-User Technologies: Exchange, SharePoint, Teams, OneDrive, Office, Copilot, Windows OS, Defender, MFA, Authenticator
- Networking: Firewalls, switches,
- for any list of duties/requirements/benefits, and
for prose. It doesn't forbid headings inside list? Probably better to keep each duty as
- and maybe include sub-bullets as nested
- . But we must preserve all substantive information. We could keep the headings as plain text inside
- and then nested list for subpoints. Simplify: For each major duty heading, we can have
- Leadership & Team Management: ... then nested
- for subpoints.
But the instruction didn't forbid using inside
- . It's okay. Now "What you bring to the Team": includes Education & Experience, Deep Core Technical Expertise. That's requirements/qualifications. "Additional Knowledge & Strengths Required": list. "Nice-to-Have": list. "Location: Candidates must be local to one of our Re:Build locations, or willing to relocate (hybrid – 3 days onsite / 2 days remote)." That's schedule/location. "The BIG payoff": ownership share, financial rewards. We must not include EEO etc. Now decide sections: - About the role: combine "Who we are looking for" + "The Role" maybe short paragraph. - Responsibilities: the "What you get to do!" bullet list. - Requirements: Education & Experience (Bachelor's, 7+ years, 5+ years leading, certifications plus). Could also include Deep Core Technical Expertise as Requirements? But maybe better as Skills. - Qualifications: Additional Knowledge & Strengths Required. - Skills: Deep Core Technical Expertise (list of technical skills). Could also include Nice-to-Have as Skills? But Nice-to-Have is separate. - Benefits: The BIG payoff. - Schedule: Location/hybrid. We must not create sections with filler. All have content. Now we need to ensure we don't repeat content across sections. Let's extract each piece. About the role paragraph: From "Who we are looking for": "We’re seeking an IT Infrastructure Manager to lead and evolve the technology foundation that enables a positive, reliable, and productive end-user experience for all Re:Builders. This role blends deep infrastructure expertise with strong people leadership, emotional intelligence, and a continuous-improvement approach.The ideal candidate is resilient, empathetic, and outcome-driven—someone who can balance operational excellence with long-term architectural thinking while building trust across IT and the business." From "The Role": "The IT Infrastructure Manager is responsible for leading the infrastructure team, overseeing day-to-day operations, and owning infrastructure design and architecture across Re:Build. This role ensures systems are secure, available, scalable, and performant, while continuously improving the way infrastructure services are delivered.You’ll partner closely with business leaders, IT peers, and vendors to solve today’s infrastructure challenges and design solutions that support future growth." We can combine into a paragraph. Now Responsibilities: list of duties. We need to capture all bullet points under each heading. Let's extract: Leadership & Team Management - Lead, coach, and develop the Infrastructure team, fostering a positive, accountable, and service-oriented culture - Manage staffing, scheduling, priorities, performance reviews, and professional development plans - Ensure teams operate cohesively with minimal friction; mentor and support others across IT as needed Infrastructure Operations & Reliability - Oversee all infrastructure operations, processes, and service delivery - Ensure service levels meet or exceed agreed targets; manage escalations and breached SLAs - Own and lead critical incident management processes and post-incident improvements - Support the team with incident resolution, service requests, and project execution when needed Architecture & Engineering - Design, review, and approve infrastructure architectures using a collaborative, business-aligned approach - Lead design, build, test, and support activities for infrastructure solutions across the enterprise - Ensure infrastructure standards, patterns, and documentation are current and effective Continuous Improvement & Metrics - Define, validate, and communicate important infrastructure metrics and performance indicators - Drive continuous improvement across people, processes, and systems using data-driven methods - Maintain SOPs, work instructions, and knowledge base content; communicate changes effectively Planning, Governance & Vendors - Contribute to IT planning, budgeting, forecasting, and vendor management - Ensure infrastructure aligns with security, compliance, and regulatory requirements - Monitor end-user satisfaction and feedback, translating insights into actionable improvements Now Requirements: Education & Experience - Bachelor’s degree in Information Technology or a related field, or equivalent practical experience - 7+ years of experience designing, building, supporting, and troubleshooting enterprise infrastructure - 5+ years of experience leading and managing infrastructure teams - Current IT industry certifications are a plus Now Qualifications: Additional Knowledge & Strengths Required - Cybersecurity practices and compliance frameworks (CMMC, GCC High, AWS GovCloud, FedRAMP) - Familiarity with CAD systems - ITIL processes and service management concepts - Experience employing AI tools to streamline and improve IT operations - Strong documentation skills (architecture, policies, runbooks, procedures) - Demonstrable ability to develop teams, hold accountability, and create an outcome-driven culture - Proven ability to learn new technologies quickly and apply them effectively Now Skills: Deep Core Technical Expertise list - Servers & Virtualization: Server hardware, Microsoft Server, VMware, Hyper-V - Cloud Platforms: Microsoft Azure, AWS, Google Cloud - Core Services: Active Directory, DNS, DHCP, file/print, certificates, identity services - Storage, Backup & Recovery - Complex Environments: Multi-tenant, multi-cloud, multi-domain, multi-forest - Endpoint & Device Management: PCs, Macs, peripherals, printers, Intune - Microsoft 365 & End-User Technologies: Exchange, SharePoint, Teams, OneDrive, Office, Copilot, Windows OS, Defender, MFA, Authenticator - Networking: Firewalls, switches,