Senior Infrastructure Engineer
- .
Required Knowledge, Skills and Abilities bullet list.
Education bullet list.
Experience bullet list (under Experience heading maybe part of Requirements? But we have separate Experience heading? The list of headings includes Requirements, Qualifications, Skills. We could put Education and Experience under Requirements. Or we could have separate sections but not required. The instruction: Prefer a few substantive sections over many thin ones. So we can combine Education and Experience into Requirements.
Preferred Qualifications bullet list.
Work Environment paragraph: includes remote states, Dallas-Fort Worth preference, hours vary, standard US business hours, occasional after-hours support, travel less than 10% domestic. That's Schedule.
Compensation paragraph: Base Salary range, notes. That's Pay.
We should not include Benefits.
Skills: maybe we can extract skills from Required Knowledge etc. But we already have Required Knowledge etc. Could create Skills section summarizing key skills: e.g., Azure IaaS/PaaS, Entra ID, Intune, Windows/Linux, DNS/DHCP/TCP/IP, VPN, SSO/SAML, Terraform, Ansible, PowerShell, Python, etc. But that might duplicate. However we need to include all substantive info; we can put them in Requirements and Preferred Qualifications. Skills section could be optional but we can include if we have specific skills list. The posting includes many skills; we could create Skills section summarizing both required and preferred. But to avoid duplication, maybe we just not include Skills section and rely on Requirements and Qualifications. However the instruction says we can use those headings; not mandatory to use all. So we can omit Skills if we think it's thin. But we have plenty of skill details in Required Knowledge etc. Could put them under Requirements. That seems fine.
Thus sections: About the role (h3), Responsibilities (h3), Requirements (h3) (includes Required Knowledge, Skills and Abilities, Education, Experience), Qualifications (h3) (Preferred Qualifications), Pay (h3), Schedule (h3).
We need to ensure we don't include filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no markdown fences.
Let's craft.
About the role
We are seeking a Senior Infrastructure Platform Engineer to help design, operate, and evolve our global enterprise infrastructure environment. This role is intended for highly capable engineers with broad technical depth across infrastructure domains including systems, networking, cloud, identity, endpoint management, and core Internet technologies. This is a hands-on engineering role with operational responsibility. The successful candidate will be expected to execute production changes, troubleshoot complex technical issues, participate in operational support, and contribute to long-term infrastructure strategy and standardization efforts. We are intentionally seeking engineers with broad foundational knowledge rather than narrow specialization. The ideal candidate understands not only how to operate enterprise technologies, but also how the underlying systems and protocols function together. This role requires strong critical thinking, structured troubleshooting ability, sound technical judgment, and the ability to learn new technologies quickly.
Responsibilities
- Infrastructure Engineering & Operations - Design, implement, maintain, and support enterprise infrastructure platforms across cloud and enterprise environments
- Execute production infrastructure changes in accordance with operational and change management standards
- Support day-to-day operational health, maintenance, and troubleshooting of infrastructure systems
- Participate in incident response, root cause analysis, and operational recovery efforts
- Maintain ownership of infrastructure reliability, scalability, security, and operational excellence
- Cross-Platform Infrastructure Support - Support and troubleshoot: Windows Server environments, Linux systems, Cloud infrastructure, Enterprise networking, Identity and authentication platforms, Endpoint management solutions, Infrastructure management tooling
- Work across infrastructure disciplines without reliance on narrowly defined technology boundaries
- Collaborate with peers, business, project, and application teams to support enterprise initiatives
- Core Infrastructure & Identity Services - Support enterprise infrastructure technologies including: DNS, DHCP, TCP/IP, Routing and connectivity, VPN technologies, TLS/SSL, SSO/SAML authentication
- Maintain and troubleshoot endpoint management platforms including: Microsoft Intune, Windows Autopilot, Patch My PC
- Troubleshooting & Problem Resolution - Diagnose and resolve complex infrastructure and systems issues across multiple technology layers - Apply structured troubleshooting methodologies and logical problem-solving techniques - Utilize logs, metrics, packet captures, and system analysis to isolate root causes and remediate as necessary - Respond effectively during outages, escalations, and high-pressure operational situations - Recognize knowledge gaps quickly and seek assistance appropriately when necessary
- Automation & Continuous Improvement - Contribute to infrastructure automation and infrastructure-as-code initiatives - Learn and adopt automation technologies and modern operational practices as needed - Support or develop automation solutions using tools such as: Terraform, Ansible, PowerShell, Python - Create and maintain high-quality operational documentation, standards, and procedures - Identify opportunities to improve reliability, operational efficiency, and scalability
Requirements
Required Knowledge, Skills and Abilities:
- 7+ years of progressive experience in infrastructure engineering, systems engineering, or enterprise IT operations
- Strong hands-on experience supporting and designing: Azure IaaS and PaaS resources, Entra ID, Intune, Windows, and Linux environments
- Strong understanding of foundational infrastructure and Internet technologies including: DNS, DHCP, TCP/IP, Routing, VPNs, Authentication protocols and SSO/SAML concepts
- Experience supporting cloud infrastructure, preferably Microsoft Azure
- Experience managing or supporting endpoint management technologies including Intune and Autopilot
- Demonstrated ability to execute and support production infrastructure changes
- Strong troubleshooting, analytical, and critical thinking skills
- Ability to quickly learn new technologies and adapt within a fast-moving environment
- Strong communication and documentation skills
- Proven ability to operate effectively across multiple infrastructure disciplines
Education:
- Bachelor’s degree required
- Master’s degree preferred
Experience:
- This role is highly hands-on and requires both strategic thinking and operational execution
- 8+ years of progressive enterprise network engineering experience
- Proven experience supporting stable, scalable, and secure global network operations
- Experience reducing operational risk and driving standardization across multiple office locations
- Demonstrated leadership managing and developing offshore network engineering teams
- Strong ability to partner effectively with infrastructure, security, and business leadership teams
- Experience responding to and resolving critical incidents and operational challenges in a timely and effective manner
Qualifications
Preferred Qualifications:
- Experience with: Terraform, Ansible, Python, PowerShell, OCI, Enterprise networking technologies, Identity and access management platforms and Infrastructure monitoring and observability tools
- Experience in global enterprise environments
- Experience supporting hybrid cloud infrastructure architectures
Pay
Base Salary: $120,000.00 - $150,000.00 - Compensation is subject to change based on experience and location hired. - Base salary only includes the base annual wage; base salary does not include other forms of compensation, such as commissions or bonuses. - Base salary also does not include other forms of compensation or benefits offered in connection with this advertised job, such as: employer-provided insurance, paid or unpaid time off work, the availability of or contributions towards retirement or savings funds, such as 401(k) plans, severance pay or overtime pay.
Schedule
This job operates in a professional office environment - Please note that all applicants must reside in and perform all work remotely from one of the following states for the entire duration of the internship: Florida, Michigan, Montana, New Jersey, New York, North Carolina, Pennsylvania, Texas, Utah, or Virginia. - Candidates located in the Dallas-Fort Worth area are preferred. - This position’s hours vary depending on business activity - Candidate must be available during standard U.S. business hours - Occasional after-hours support may be required during major incidents or escalations - This position does not require frequent travel, less than 10%. Travel would be domestic
Check for any duplicated lines: we have repeated travel line twice? In Work Environment we had two lines: "This position does not require frequent travel, less than 10%. Travel would be domestic" appears twice in original (once in Work Environment, once in Travel Requirements). We included only once. Good. We removed boilerplate like EEO etc. We preserved all substantive info. Check if any content missing: The "Work Environment" also had "This job operates in a professional office environment". We included that at start of Schedule paragraph. Good. We included "Please note that all applicants must reside in and perform all work remotely from one of the following states..." Good. We included "Candidates located in the Dallas-Fort Worth area are preferred." Good. We included "This position’s hours vary depending on business activity" etc. We included "Occasional after-hours support may be required during major incidents or escalations". Good. We included "This position does not require frequent travel, less than 10%. Travel would be domestic". Good. Compensation section includes all details. We didn't include Benefits section. We didn't include Skills section (optional). That's fine. We need to ensure we didn't miss any bullet points from Essential Functions: we captured them but need to verify each bullet