IT / OT Infrastructure Manager
Re:Build Manufacturing · Rochester, NY · 1 mo ago
HybridInformation TechnologyFull-time
We need to output HTML fragment with sections only if real content. We need to extract sections: About the role? Actually the posting includes "About Re:Build" description, then "Who we are looking for", then "The Role", then bullet lists under "What you get to do!" with subheadings: Leadership & Team Management, Infrastructure Operations & Reliability, Architecture & Engineering, Continuous Improvement & Metrics, Planning, Governance & Vendors. Then "What you bring to the Team" with subheadings Education & Experience, Deep Core Technical Expertise, Additional Knowledge & Strengths Required, Nice-to-Have, Location. Then "The BIG payoff" with some prose about ownership etc. Then EEO boilerplate etc to be removed.
We must use for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we can use other headings? The instruction: "use
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we can use other headings? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use h3 for sections. Likely we should map our sections to those headings where appropriate. But we can also use other headings? It says use h3 for section headings (e.g., ...). Probably they expect we use h3 for each section heading we include. We should not repeat the job title as a heading. So we will produce sections like:
About Re:Build
maybe? But they gave example "About the role". However we can still use About Re:Build as a section. It's okay.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. There's no explicit pay or schedule besides location hybrid (3 days onsite/2 days remote). That's schedule info? It says 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 info (hybrid). Should we create a Schedule section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state hybrid schedule, so we can include a Schedule section. Benefits? There's mention of ownership share, financial rewards, etc. That could be considered benefits. The "The BIG payoff" section mentions ownership, financial rewards, etc. That's benefits. So we can include Benefits section.
We need to avoid filler like "commensurate with experience". Not present.
We need to output only HTML fragment.
Let's structure:
About Re:Build
... description ...
Who we are looking for
... short paragraph ...
The Role
... short paragraph ...
Then we could combine the "What you get to do!" subheadings into a Responsibilities section? The instruction says use h3 for section headings like Responsibilities. So we could make a Responsibilities section and put the bullet lists under it. But we also have subheadings like Leadership & Team Management etc. We could either keep them as subheadings inside Responsibilities using maybe ? But they only said use h3 for section headings; not forbid other headings. Safer to keep the subheadings as or ? But they said use - for any list of duties/requirements/benefits, and
for prose. They didn't forbid using other headings for subsections. We could keep the subheadings as
or just . However to be safe, we could treat each subheading as its own section? That would create many sections but they said prefer a few substantive sections over many thin ones. So better to group under Responsibilities.
Thus:
Responsibilities
Then under that we can have subheadings maybe as or . But we need to output only HTML fragment; using is okay.
We'll produce:
Responsibilities
Leadership & Team Management
- ...
... etc.
Similarly for Requirements/Qualifications/Skills: we have Education & Experience, Deep Core Technical Expertise, Additional Knowledge & Strengths Required, Nice-to-Have, Location. Could group under Requirements or Qualifications. Let's make a Qualifications
and include subheadings.
Benefits: from "The BIG payoff": ownership share, financial rewards, etc. Also maybe mention "share ownership in the company". We'll put that.
Schedule: hybrid 3 days onsite/2 days remote.
We must not include EEO etc.
Let's extract content precisely.
First, "About Re:Build" paragraph:
"At 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)"
We need to preserve all substantive information; we can keep the link mention but maybe drop the "(link to ...)" as it's not substantive? It's a reference; but it's part of the description. Might keep as is.
Second, "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."
Third, "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."
Now responsibilities bullet lists:
Under "What you get to do!" we have sections:
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 qualifications:
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
Deep Core Technical Expertise (list many):
- 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, routers, access points, cabling; Fortinet platforms
- Data Center Operations: Racks, cabling, power, cooling, fire suppression
- Monitoring & Alerting: Including preference for automated remediation
- Patch & Asset Lifecycle Management
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
Nice-to-Have
- Working knowledge of Lean Manufacturing principles
- Experience in manufacturing environments and OT networking
Location: Candidates must be local to one of our Re:Build locations, or willing to relocate (hybrid – 3 days onsite / 2 days remote).
Now Benefits / The BIG payoff:
"We are a company who is going to make a difference in the industries and the communities in which we choose to operate.
Every employee of Re:Build will share ownership in the company and will share in the financial rewards of the success we achieve together, at all levels of the company!
We want to work with people that reflect the communities in which we operate"
We should preserve that.
Now we need to output HTML.
We'll have sections:
About Re:Build
...
Who we are looking for
...
The Role
...
Responsibilities
Leadership & Team Management
...
Infrastructure Operations & Reliability
...
Architecture & Engineering
...
Continuous Improvement & Metrics
...
Planning, Governance & Vendors
...
Qualifications
Education & Experience
...
Deep Core Technical Expertise
...
Additional Knowledge & Strengths Required
...
Nice
About Re:Build
maybe? But they gave example "About the role". However we can still use About Re:Build as a section. It's okay. We need to use- for any list of duties/requirements/benefits, and
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions. We must not create Pay/Schedule/Benefits sections unless posting actually states them. There's no explicit pay or schedule besides location hybrid (3 days onsite/2 days remote). That's schedule info? It says 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 info (hybrid). Should we create a Schedule section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state hybrid schedule, so we can include a Schedule section. Benefits? There's mention of ownership share, financial rewards, etc. That could be considered benefits. The "The BIG payoff" section mentions ownership, financial rewards, etc. That's benefits. So we can include Benefits section. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment. Let's structure:
About Re:Build
... description ...
Who we are looking for
... short paragraph ...
The Role
... short paragraph ...
Then we could combine the "What you get to do!" subheadings into a Responsibilities section? The instruction says use h3 for section headings like Responsibilities. So we could make a Responsibilities section and put the bullet lists under it. But we also have subheadings like Leadership & Team Management etc. We could either keep them as subheadings inside Responsibilities using maybe? But they only said use h3 for section headings; not forbid other headings. Safer to keep the subheadings as
or ? But they said use
- for any list of duties/requirements/benefits, and
for prose. They didn't forbid using other headings for subsections. We could keep the subheadings as
or just . However to be safe, we could treat each subheading as its own
section? That would create many sections but they said prefer a few substantive sections over many thin ones. So better to group under Responsibilities. Thus:
Responsibilities
Then under that we can have subheadings maybe asor . But we need to output only HTML fragment; using
is okay. We'll produce:
Responsibilities
Leadership & Team Management
- ...
Qualifications
and include subheadings. Benefits: from "The BIG payoff": ownership share, financial rewards, etc. Also maybe mention "share ownership in the company". We'll put that. Schedule: hybrid 3 days onsite/2 days remote. We must not include EEO etc. Let's extract content precisely. First, "About Re:Build" paragraph: "At 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)" We need to preserve all substantive information; we can keep the link mention but maybe drop the "(link to ...)" as it's not substantive? It's a reference; but it's part of the description. Might keep as is. Second, "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." Third, "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." Now responsibilities bullet lists: Under "What you get to do!" we have sections: 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 qualifications: 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 Deep Core Technical Expertise (list many): - 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, routers, access points, cabling; Fortinet platforms - Data Center Operations: Racks, cabling, power, cooling, fire suppression - Monitoring & Alerting: Including preference for automated remediation - Patch & Asset Lifecycle Management 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 Nice-to-Have - Working knowledge of Lean Manufacturing principles - Experience in manufacturing environments and OT networking Location: Candidates must be local to one of our Re:Build locations, or willing to relocate (hybrid – 3 days onsite / 2 days remote). Now Benefits / The BIG payoff: "We are a company who is going to make a difference in the industries and the communities in which we choose to operate. Every employee of Re:Build will share ownership in the company and will share in the financial rewards of the success we achieve together, at all levels of the company! We want to work with people that reflect the communities in which we operate" We should preserve that. Now we need to output HTML. We'll have sections:About Re:Build
...
Who we are looking for
...
The Role
...
Responsibilities
Leadership & Team Management
- ...
Infrastructure Operations & Reliability
- ...
Architecture & Engineering
- ...
Continuous Improvement & Metrics
- ...
Planning, Governance & Vendors
- ...
Qualifications
Education & Experience
- ...
Deep Core Technical Expertise
- ...
Additional Knowledge & Strengths Required
- ...
Nice
- for any list of duties/requirements/benefits, and