Remote Infrastructure Engineer Jobs
Remote Infrastructure Engineer jobs are open across the US at companies hiring remotely, from entry-level roles at remote-first startups to senior roles on large distributed teams, with employers like CVS Health, Speechify, and IT Labs hiring right now. Scan the live roles below and apply to whichever ones fit.
Find JobsOverview
Showing 5 of 1,000+ Remote Infrastructure Engineer jobs
INTRODUCTION
This role involves the development and implementation of automation templates and migration tools to facilitate the provisioning of virtual machines (VMs) across various operating systems. The position requires collaboration with security teams and infrastructure teams to ensure seamless integration and migration processes.
ROLE AND RESPONSIBILITIES
Primary Deliverables
- Aria Automation templates that provision VMs and self-register with AWS SSM and SentinelOne across Windows, Linux, and macOS
- GitLab CI pipelines to develop, test, validate, and deploy provisioning templates and migration script code
- Security team collaboration — define and validate exclusions, token handling, and a documented exclusions process and technical implementation
- VMware-to-Proxmox migration toolkit — robust, repeatable scripts and pipelines to migrate ~1,500–2,000 on-premises VMs with SSM and SentinelOne registration to a Proxmox-based environment
- Proxmox platform readiness — collaborate on capacity planning input, environment validation, and migration tools and scripts
Key Responsibilities
Provisioning & Templates
- Extend existing production Aria Automation environment with new virtual machine templates for SSM and SentinelOne self-registration
- Build reusable, parameterized templates across Aria Automation, Terraform, and Ansible
- Support for all three OS types: Windows, Linux, and macOS (Intel-based)
- Integrate with existing CI-driven provisioning and deprovisioning workflows already in place
- Treat the existing production environment with care — validate all changes in non-production before any production promotion. Attention to detail and clear team communication of possible clear assessment of production impact is imperative.
AWS SSM Integration
- Automate SSM Agent installation and registration as part of every provisioning workflow
- Configure hybrid activation codes for all on-premises (non-EC2) targets across all OS types
- Validate SSM registration before marking provisioning complete
SentinelOne Integration
- Automate SentinelOne agent installation and silent deployment for Windows, Linux, and macOS
- Develop hands-off integration with SentinelOne so that any defined exclusions are in place at SentinelOne installation time
- Confirm agent check-in as a provisioning completion gate
Security Team Collaboration
- Work directly with the internal Security group to define and validate required exclusion sets
- Work directly with internal security group to define system integration for up-front exclusions activation process
- Collaborate with Security to develop and document a formal exclusions process — covering what exclusions are permissible, how they are requested, reviewed, and approved
GitLab & CI/CD Pipeline Development
- Maintain all code in GitLab with regular, meaningful check-ins, pull requests, and regular reviews with the team
- Follow generally accepted software development practices: branching strategies, merge requests, commit hygiene, and code review
- Build and maintain GitLab CI pipelines for linting, validation, testing, and deployment of provisioning and migration code
- Implement pipeline stages for Dev, Staging, and Production promotion with appropriate approval gates
- Use Artifactory to store and retrieve binary dependencies
- Organize repositories clearly so the internal team can understand, maintain, and extend the work after the engagement ends
VMware-to-Proxmox Migration
- Work with the infrastructure team to inventory all ~1,500–2,000 VMs — workload types, OS, network topology, storage layout, and VMware-specific dependencies (VMware Tools features, VMXNET3, paravirtual SCSI, VMware-specific drivers, etc.)
- Self-review all VMs and migration candidates for VMware-specific dependencies — proactively identify anything that may not translate cleanly to Proxmox and raise findings with the team leader before proceeding
- Coordinate with the infrastructure team on Proxmox capacity planning — advise on node count, storage sizing for ~300TB of VM data, and network configuration
- Design and develop a migration script toolkit (Bash, Python, PowerShell, and/or Ansible) to automate export from VMware and import/conversion to Proxmox-compatible formats using tools such as virt-v2v and qemu-img
- Automate post-migration configuration: network interface remapping, storage attachment, and VM hardware profile alignment
- Integrate SSM Agent and SentinelOne re-registration into the post-migration workflow so migrated VMs are immediately managed and protected on Proxmox
- Implement pre- and post-migration validation checks — confirming VM boot, network connectivity, SSM registration, and SentinelOne check-in before marking a migration complete
- Prefer live migration where feasible; where downtime is unavoidable, coordinate directly with end-users to agree on outage windows before proceeding
- Support a phased migration approach: non-production and lower-risk workloads first, then production with change management gates
- Consult freely and proactively with the team leader throughout — ask questions early, flag concerns immediately, and do not proceed with uncertain migrations without alignment
- Deliver a migration runbook covering prerequisites, execution steps, rollback procedures, and known edge cases
Proxmox Platform Readiness
- Advise the infrastructure team on capacity requirements based on current VMware inventory and ~500TB data volume
- Assist with validation of Proxmox-based self-service provisioning system. Develop and run test scripts and Terraform and cloud-init templates for testing
- Prototype VM provisioning using Terraform (Proxmox provider) and Ansible
- Validate Proxmox networking, storage, and resource configuration against workload requirements
Documentation & Handoff
- Deliver runbooks for all provisioning templates, CI pipelines, and migration workflows
- Document integration architecture, secret/credential management with existing internal controls
- Deliver the Security-approved exclusions process as a standalone document
- Deliver the migration script toolkit with inline documentation and a standalone operations guide
- Conduct a knowledge transfer session with the internal infrastructure team before engagement close
INTRODUCTION
This role involves the development and implementation of automation templates and migration tools to facilitate the provisioning of virtual machines (VMs) across various operating systems. The position requires collaboration with security teams and infrastructure teams to ensure seamless integration and migration processes.
ROLE AND RESPONSIBILITIES
Primary Deliverables
- Aria Automation templates that provision VMs and self-register with AWS SSM and SentinelOne across Windows, Linux, and macOS
- GitLab CI pipelines to develop, test, validate, and deploy provisioning templates and migration script code
- Security team collaboration — define and validate exclusions, token handling, and a documented exclusions process and technical implementation
- VMware-to-Proxmox migration toolkit — robust, repeatable scripts and pipelines to migrate ~1,500–2,000 on-premises VMs with SSM and SentinelOne registration to a Proxmox-based environment
- Proxmox platform readiness — collaborate on capacity planning input, environment validation, and migration tools and scripts
Key Responsibilities
Provisioning & Templates
- Extend existing production Aria Automation environment with new virtual machine templates for SSM and SentinelOne self-registration
- Build reusable, parameterized templates across Aria Automation, Terraform, and Ansible
- Support for all three OS types: Windows, Linux, and macOS (Intel-based)
- Integrate with existing CI-driven provisioning and deprovisioning workflows already in place
- Treat the existing production environment with care — validate all changes in non-production before any production promotion. Attention to detail and clear team communication of possible clear assessment of production impact is imperative.
AWS SSM Integration
- Automate SSM Agent installation and registration as part of every provisioning workflow
- Configure hybrid activation codes for all on-premises (non-EC2) targets across all OS types
- Validate SSM registration before marking provisioning complete
SentinelOne Integration
- Automate SentinelOne agent installation and silent deployment for Windows, Linux, and macOS
- Develop hands-off integration with SentinelOne so that any defined exclusions are in place at SentinelOne installation time
- Confirm agent check-in as a provisioning completion gate
Security Team Collaboration
- Work directly with the internal Security group to define and validate required exclusion sets
- Work directly with internal security group to define system integration for up-front exclusions activation process
- Collaborate with Security to develop and document a formal exclusions process — covering what exclusions are permissible, how they are requested, reviewed, and approved
GitLab & CI/CD Pipeline Development
- Maintain all code in GitLab with regular, meaningful check-ins, pull requests, and regular reviews with the team
- Follow generally accepted software development practices: branching strategies, merge requests, commit hygiene, and code review
- Build and maintain GitLab CI pipelines for linting, validation, testing, and deployment of provisioning and migration code
- Implement pipeline stages for Dev, Staging, and Production promotion with appropriate approval gates
- Use Artifactory to store and retrieve binary dependencies
- Organize repositories clearly so the internal team can understand, maintain, and extend the work after the engagement ends
VMware-to-Proxmox Migration
- Work with the infrastructure team to inventory all ~1,500–2,000 VMs — workload types, OS, network topology, storage layout, and VMware-specific dependencies (VMware Tools features, VMXNET3, paravirtual SCSI, VMware-specific drivers, etc.)
- Self-review all VMs and migration candidates for VMware-specific dependencies — proactively identify anything that may not translate cleanly to Proxmox and raise findings with the team leader before proceeding
- Coordinate with the infrastructure team on Proxmox capacity planning — advise on node count, storage sizing for ~300TB of VM data, and network configuration
- Design and develop a migration script toolkit (Bash, Python, PowerShell, and/or Ansible) to automate export from VMware and import/conversion to Proxmox-compatible formats using tools such as virt-v2v and qemu-img
- Automate post-migration configuration: network interface remapping, storage attachment, and VM hardware profile alignment
- Integrate SSM Agent and SentinelOne re-registration into the post-migration workflow so migrated VMs are immediately managed and protected on Proxmox
- Implement pre- and post-migration validation checks — confirming VM boot, network connectivity, SSM registration, and SentinelOne check-in before marking a migration complete
- Prefer live migration where feasible; where downtime is unavoidable, coordinate directly with end-users to agree on outage windows before proceeding
- Support a phased migration approach: non-production and lower-risk workloads first, then production with change management gates
- Consult freely and proactively with the team leader throughout — ask questions early, flag concerns immediately, and do not proceed with uncertain migrations without alignment
- Deliver a migration runbook covering prerequisites, execution steps, rollback procedures, and known edge cases
Proxmox Platform Readiness
- Advise the infrastructure team on capacity requirements based on current VMware inventory and ~500TB data volume
- Assist with validation of Proxmox-based self-service provisioning system. Develop and run test scripts and Terraform and cloud-init templates for testing
- Prototype VM provisioning using Terraform (Proxmox provider) and Ansible
- Validate Proxmox networking, storage, and resource configuration against workload requirements
Documentation & Handoff
- Deliver runbooks for all provisioning templates, CI pipelines, and migration workflows
- Document integration architecture, secret/credential management with existing internal controls
- Deliver the Security-approved exclusions process as a standalone document
- Deliver the migration script toolkit with inline documentation and a standalone operations guide
- Conduct a knowledge transfer session with the internal infrastructure team before engagement close
See All 1,000+ Remote Infrastructure Engineer Jobs
Find roles that match your experience and apply in just a few clicks.
Find JobsRemote Infrastructure Engineer Job Market
Who's Hiring
- CVS Health121
- Speechify74
- IT Labs56I
- Humana55
- TechBiz Global16T
Top Industries Hiring
- Technology & Software308
- Healthcare & Medical Services212
- Insurance90
- Consulting & Professional Services55
- Banking & Financial Services17
What Employers Look For
The qualifications that appear most often in remote infrastructure engineer jobs.
- Three or more years of experience managing cloud infrastructure on AWS, Azure, or GCP
- Proficiency with infrastructure-as-code tools such as Terraform or Ansible
- Strong knowledge of networking fundamentals including TCP/IP, DNS, VPNs, and load balancing
- Experience with containerization and orchestration using Docker and Kubernetes
- Familiarity with CI/CD pipelines and tools such as Jenkins, GitLab CI, or GitHub Actions
- Bachelor's degree in computer science, information technology, or a related technical field
Tips for Your Remote Infrastructure Engineer Job Search
Tailor your resume to the stack
Infrastructure engineer postings vary wildly between teams running bare-metal servers and those fully in Kubernetes on AWS. Pull the exact tools from each job description and mirror that language in your resume's skills and project bullets, not a generic list.
Apply early to roles that fit
Migrate Mate lists infrastructure engineer openings from across the United States in one place, so you can find roles that match and apply directly to each listing.
Quantify your reliability and scale wins
Hiring managers for infrastructure roles want to see uptime improvements, latency reductions, or the scale of environments you managed. Replace vague claims like 'maintained servers' with concrete outcomes like reduced deployment failures or increased cluster capacity.
Filter openings by cloud platform first
Most infrastructure teams are deeply invested in one cloud ecosystem. Targeting roles that match your primary platform, whether AWS, Azure, or GCP, puts you ahead of generalist applicants and avoids the ramp-up gap that kills offers.
Prepare for a hands-on technical screen
Infrastructure interviews almost always include a live troubleshooting exercise or a take-home task involving a broken environment. Practice diagnosing misconfigured Terraform plans, failed deployments, or networking issues out loud so you can narrate your reasoning under pressure.
Negotiate beyond base using on-call context
Infrastructure roles often carry on-call responsibilities that many candidates forget to factor in when evaluating offers. Ask about on-call frequency, incident severity expectations, and whether on-call hours count toward comp, then use that information to frame your counteroffer.
Remote Infrastructure Engineer Jobs: Frequently Asked Questions
How do I get a remote infrastructure engineer job?
Target companies that already run distributed teams, since they hire remotely by default and know how to onboard someone they never meet in person. Remote infrastructure engineer employers screen hard for self-direction and clear written communication on top of the core skills, so show evidence you can own work without someone over your shoulder. Apply to the openings above that match your experience.
Which companies hire remote infrastructure engineers?
Companies hiring remote infrastructure engineers include CVS Health, Speechify, and IT Labs, based on current remote listings on Migrate Mate as of June 2026. Remote-first firms and large companies running distributed teams post the most remote infrastructure engineer roles.
Can you get a remote infrastructure engineer job with no experience?
Yes, but it is harder than an on-site role, because remote work expects you to operate independently from the start. Entry-level remote infrastructure engineer openings do exist, especially at remote-first companies, and a portfolio of real work helps more than a long resume. Applying broadly to the roles that fit improves your odds.
Do you need a degree for remote infrastructure engineer jobs?
Not always. Many employers hire remote infrastructure engineers on demonstrated skills and prior work rather than a specific degree, though some larger companies still prefer one. Showing relevant results matters more than a credential for most remote infrastructure engineer roles.
Which industries hire the most remote infrastructure engineers?
The sectors hiring the most remote infrastructure engineers are Technology & Software, Healthcare & Medical Services, and Insurance, based on current remote listings on Migrate Mate as of June 2026. These sectors run distributed teams and hire infrastructure engineers remotely most consistently.
See All 1,000+ Remote Infrastructure Engineer Jobs
Find roles that match your experience and apply in just a few clicks.
Find Jobs