Infrastructure as Code Engineer - Nutanix, Terraform & Ansible
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do not include boilerplate like Interview Mode, Duration, etc? Those are metadata; we can fold minor metadata into a short
or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include location, duration, interview mode maybe as a short paragraph under About the role? But they said "Prefer a few substantive sections over many thin ones." So we can have sections: About the role (position overview), Responsibilities, Requirements (maybe combine Required and Preferred?), Skills? But we have many qualifications; we can put them under Requirements as a list. Benefits, Pay, Schedule: not present, so omit those sections. Also we should not include sections with filler like "commensurate with experience". Not present.
We need to preserve all substantive information. So we need to include details like: Job Location: 100% Remote, Duration: 24 months, Interview Mode: 1st round remote via Teams, 2nd round onsite in New York, NY, CANDIDATES MUST BE ABLE TO GO TO 2ND ROUND INTERVIEW ONSITE IN NEW YORK, NY AND ONBOARD FOR 2-3 DAYS ONSITE IN NYC. This is metadata; we can fold into a short
maybe under About the role or a separate "Details" section? But they said only include section when posting has real, specific content for it. Could we make a section "Details"? Not in the list of allowed headings; they gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should stick to those. So we can put the metadata in About the role paragraph.
Thus About the role: include position overview plus job location, duration, interview mode, onsite requirement.
Responsibilities: list all responsibilities bullet points.
Requirements: include Required Qualifications bullet points.
Skills: maybe we could separate but we can combine Required Qualifications as Requirements. Or we could have Requirements and Skills separate but we don't have explicit skills list separate; we could treat Required Qualifications as Requirements and maybe Preferred Qualifications as Skills? But they said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we could have both Requirements and Qualifications sections. But we need to avoid thin sections. Perhaps combine Required and Preferred into Requirements? Or have Requirements (Required) and Skills (Preferred). However the instruction: "Prefer a few substantive sections over many thin ones." So better to have fewer sections: About the role, Responsibilities, Requirements (including both required and preferred). Could also have Skills but maybe not needed.
We must not repeat job title as heading. So no for job title.
We must output only HTML fragment, no /, no markdown fences.
Let's craft:
About the role
Position Overview: ... plus location, duration, interview mode, onsite requirement.
Responsibilities
- ...
...
Requirements
- ...
...
We need to preserve all substantive information from responsibilities and qualifications.
Let's extract responsibilities bullet points from the posting:
From "Key Responsibilities" section:
- Infrastructure as Code & Automation
- Design, develop, maintain, and enhance Terraform modules for automated infrastructure provisioning and lifecycle management.
- Build reusable Ansible playbooks, roles, and configuration automation frameworks.
- Develop automation solutions that reduce manual infrastructure administration and eliminate configuration drift.
- Implement Infrastructure as Code and Configuration as Code practices across critical infrastructure environments.
- Develop automation using Python, Linux shell scripting, and related technologies.
- Maintain infrastructure and configuration code through Git-based version control and established DevOps practices.
- Develop reusable automation standards that enable consistent deployment across environments.
- Nutanix, VMware & Platform Engineering
- Automate the provisioning, configuration, and ongoing management of Nutanix AHV and VMware environments.
- Support virtualized data center infrastructure across enterprise and Operational Technology environments.
- Engineer and automate solutions supporting Oracle Linux, Red Hat Linux, Windows, and virtualized infrastructure.
- Create and maintain standardized Oracle Linux and Windows golden images using HashiCorp Packer.
- Establish repeatable server and infrastructure baselines that improve consistency, security, and recoverability.
- Troubleshoot complex infrastructure, virtualization, operating system, and automation issues.
- Azure DevOps & CI/CD
- Design, develop, and maintain CI/CD pipelines within Microsoft Azure DevOps.
- Integrate infrastructure provisioning, configuration management, validation, and deployment processes into automated pipelines.
- Apply Git, DevOps, CI/CD, and version-control practices to infrastructure engineering.
- Implement automated testing and validation to improve deployment quality and reliability.
- Maintain traceability and auditability for infrastructure changes through source control and automated delivery processes.
- Secrets Management & Security
- Implement HashiCorp Vault for secure secrets management, credential handling, and certificate management.
- Partner with cybersecurity and infrastructure teams to implement secure-by-design automation and infrastructure solutions.
- Integrate security requirements into infrastructure code, server baselines, deployment pipelines, and operational processes.
- Support cybersecurity resilience and infrastructure-hardening initiatives.
- Help ensure infrastructure configurations remain standardized, controlled, auditable, and recoverable.
- Site Reliability Engineering & Observability
- Apply Site Reliability Engineering (SRE) principles to improve system availability, reliability, performance, and operational efficiency.
- Develop and support observability solutions utilizing Grafana, Prometheus, Loki, Alertmanager, and related platforms.
- Build dashboards, monitoring, logging, metrics, and alerting capabilities that improve visibility into infrastructure health.
- Participate in troubleshooting, incident analysis, and root cause analysis.
- Identify recurring operational issues and develop automation to reduce or eliminate them.
- Partner with infrastructure and operations teams on continuous reliability improvements.
- Disaster Recovery & Resilience
- Develop automated infrastructure validation, recovery, and disaster recovery workflows.
- Support rapid and repeatable restoration of critical environments.
- Automate recovery testing to improve disaster recovery readiness and business continuity.
- Help establish infrastructure practices that improve system recoverability and cybersecurity resilience.
- Support testing and documentation of recovery procedures and platform dependencies.
- Documentation & Cross-Functional Collaboration
- Develop detailed technical documentation, architecture information, operational procedures, and runbooks.
- Create knowledge-transfer materials supporting infrastructure and operations teams.
- Collaborate with infrastructure, operations, cybersecurity, database, and application teams.
- Participate in architecture and technical-design discussions.
- Document automation standards, deployment procedures, recovery processes, and troubleshooting guidance.
- Promote repeatable infrastructure-management practices across engineering and operational teams.
Now Required Qualifications bullet points:
- Strong hands-on experience as an Infrastructure as Code Engineer, SRE Engineer, DevOps Engineer, Infrastructure Automation Engineer, or comparable infrastructure engineering professional.
- Advanced hands-on experience with Terraform for infrastructure provisioning and automation.
- Strong experience developing Ansible playbooks and configuration-management automation.
- Experience with HashiCorp Packer for automated image creation and standardized server builds.
- Strong experience with HashiCorp Vault for secrets management and secure credential handling.
- Hands-on experience with Microsoft Azure DevOps, including automated CI/CD pipelines.
- Strong understanding of Git, DevOps, CI/CD, and version-control practices.
- Hands-on experience with Nutanix infrastructure and virtualization technologies.
- Experience supporting enterprise data center virtualization environments.
- Strong Linux administration experience, including Red Hat Linux and Oracle Linux.
- Strong Linux shell scripting capabilities.
- Experience developing infrastructure and operational automation using Python.
- Experience with observability and monitoring technologies, including Grafana and Prometheus.
- Understanding of modern observability practices involving metrics, monitoring, logging, and alerting.
- Experience developing operational procedures, technical documentation, and runbooks.
- Experience applying SRE principles to infrastructure reliability and operational automation.
- Strong troubleshooting and root cause analysis capabilities.
- Ability to collaborate effectively across infrastructure, operations, cybersecurity, database, and application teams.
Preferred Qualifications bullet points:
- Experience automating Nutanix AHV and VMware provisioning and configuration.
- Experience with Loki and Alertmanager.
- Experience supporting Windows infrastructure in addition to Linux environments.
- Experience creating and maintaining standardized Linux and Windows golden images.
- Experience automating disaster recovery, infrastructure restoration, and recovery validation.
- Experience supporting business continuity and cybersecurity-resilience initiatives.
- Experience developing reusable Terraform modules and enterprise Ansible frameworks.
- Experience integrating Vault secrets and certificate management into automated CI/CD workflows.
- Experience supporting highly controlled, security-sensitive, or Operational Technology environments.
- Experience implementing infrastructure standards designed to minimize configuration drift.
- Strong understanding of infrastructure security, auditability, recovery, and operational resilience.
Also "What We're Looking For" paragraph: we could incorporate into About the role or maybe a separate section but we can keep in About the role.
Now About the role paragraph: combine Position Overview plus job location, duration, interview mode, onsite requirement, and what we're looking for.
Let's craft:
Our Fortune 500 client located in New York, NY is seeking an experienced Senior Infrastructure as Code Engineer - Nutanix, Terraform & Ansible to design, develop, and maintain automation solutions supporting critical Operational Technology (OT) infrastructure and enterprise applications. This is a hands-on infrastructure automation and Site Reliability Engineering role focused on transforming traditional infrastructure operations into a repeatable, secure, version-controlled, and highly automated delivery model. The engineer will develop Infrastructure as Code (IaC) and Configuration as Code (CaC) solutions using Terraform, Ansible, HashiCorp Packer, Vault, Git, and Azure DevOps across Nutanix AHV, VMware, Linux, and Windows environments. The ideal candidate brings strong infrastructure engineering fundamentals combined with deep automation expertise. This individual will build reusable infrastructure modules, standardized server images, CI/CD pipelines, automated recovery processes, and observability solutions that improve platform reliability, security, recoverability, and operational efficiency.
Job Location: 100% Remote. Duration: 24 months. Interview Process: 1st round remote via Teams, 2nd round onsite in New York, NY. Candidates must be able to attend the 2nd round onsite interview and onboard for 2‑3 days onsite in NYC.
What We're Looking For: The ideal candidate is a hands‑on infrastructure automation engineer who thinks like an SRE, comfortable writing Terraform modules and Ansible automation, building Packer images, developing Azure DevOps pipelines, scripting with Python or Linux shell, and troubleshooting Nutanix, VMware, and Linux infrastructure, turning manual procedures into reusable, version‑controlled automation, establishing repeatable infrastructure baselines, improving observability, and building automated recovery capabilities.
That seems good.
Now Responsibilities: we need to list each bullet as - . Could group under headings? But we only allowed
for section headings, not subheadings. So we can just have a flat list of all responsibilities. That will be long but okay.
Similarly Requirements: list all required and preferred qualifications.
We must ensure we don't miss any.
Let's compile responsibilities list exactly as above.
I'll produce with each responsibility as - . Ensure we preserve the exact phrasing.
Let's list them:
1. Design, develop, maintain, and enhance Terraform modules for automated infrastructure provisioning and lifecycle management.
2. Build reusable Ansible playbooks, roles, and configuration automation frameworks.
3. Develop automation solutions that reduce manual infrastructure administration and eliminate configuration drift.
4. Implement Infrastructure as Code and Configuration
for prose. Do not include boilerplate like Interview Mode, Duration, etc? Those are metadata; we can fold minor metadata into a short
or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include location, duration, interview mode maybe as a short paragraph under About the role? But they said "Prefer a few substantive sections over many thin ones." So we can have sections: About the role (position overview), Responsibilities, Requirements (maybe combine Required and Preferred?), Skills? But we have many qualifications; we can put them under Requirements as a list. Benefits, Pay, Schedule: not present, so omit those sections. Also we should not include sections with filler like "commensurate with experience". Not present. We need to preserve all substantive information. So we need to include details like: Job Location: 100% Remote, Duration: 24 months, Interview Mode: 1st round remote via Teams, 2nd round onsite in New York, NY, CANDIDATES MUST BE ABLE TO GO TO 2ND ROUND INTERVIEW ONSITE IN NEW YORK, NY AND ONBOARD FOR 2-3 DAYS ONSITE IN NYC. This is metadata; we can fold into a short
maybe under About the role or a separate "Details" section? But they said only include section when posting has real, specific content for it. Could we make a section "Details"? Not in the list of allowed headings; they gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should stick to those. So we can put the metadata in About the role paragraph. Thus About the role: include position overview plus job location, duration, interview mode, onsite requirement. Responsibilities: list all responsibilities bullet points. Requirements: include Required Qualifications bullet points. Skills: maybe we could separate but we can combine Required Qualifications as Requirements. Or we could have Requirements and Skills separate but we don't have explicit skills list separate; we could treat Required Qualifications as Requirements and maybe Preferred Qualifications as Skills? But they said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we could have both Requirements and Qualifications sections. But we need to avoid thin sections. Perhaps combine Required and Preferred into Requirements? Or have Requirements (Required) and Skills (Preferred). However the instruction: "Prefer a few substantive sections over many thin ones." So better to have fewer sections: About the role, Responsibilities, Requirements (including both required and preferred). Could also have Skills but maybe not needed.
We must not repeat job title as heading. So no for job title.
We must output only HTML fragment, no /, no markdown fences.
Let's craft:
About the role
About the role
Position Overview: ... plus location, duration, interview mode, onsite requirement.
Responsibilities
- ... ...
Requirements
- ... ...
Our Fortune 500 client located in New York, NY is seeking an experienced Senior Infrastructure as Code Engineer - Nutanix, Terraform & Ansible to design, develop, and maintain automation solutions supporting critical Operational Technology (OT) infrastructure and enterprise applications. This is a hands-on infrastructure automation and Site Reliability Engineering role focused on transforming traditional infrastructure operations into a repeatable, secure, version-controlled, and highly automated delivery model. The engineer will develop Infrastructure as Code (IaC) and Configuration as Code (CaC) solutions using Terraform, Ansible, HashiCorp Packer, Vault, Git, and Azure DevOps across Nutanix AHV, VMware, Linux, and Windows environments. The ideal candidate brings strong infrastructure engineering fundamentals combined with deep automation expertise. This individual will build reusable infrastructure modules, standardized server images, CI/CD pipelines, automated recovery processes, and observability solutions that improve platform reliability, security, recoverability, and operational efficiency.
Job Location: 100% Remote. Duration: 24 months. Interview Process: 1st round remote via Teams, 2nd round onsite in New York, NY. Candidates must be able to attend the 2nd round onsite interview and onboard for 2‑3 days onsite in NYC.
What We're Looking For: The ideal candidate is a hands‑on infrastructure automation engineer who thinks like an SRE, comfortable writing Terraform modules and Ansible automation, building Packer images, developing Azure DevOps pipelines, scripting with Python or Linux shell, and troubleshooting Nutanix, VMware, and Linux infrastructure, turning manual procedures into reusable, version‑controlled automation, establishing repeatable infrastructure baselines, improving observability, and building automated recovery capabilities.
That seems good. Now Responsibilities: we need to list each bullet as