> Markdown version of [/jobs/ext/4720422-senior-infrastructure-engineer](https://www.wearedevelopers.com/jobs/ext/4720422-senior-infrastructure-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Infrastructure Engineer - **Company:** Eagle Industries - **Location:** Minneapolis, MN, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Proxmox, Amazon Web Services, Amazon Elastic Compute Cloud, Amazon S3, Systems Engineering, Confluence, Backup Devices, Intelligent Platform Management Interface, Bash Shell, Ubuntu (Operating System), Configuration Management, Data Recovery, Dynamic Host Configuration Protocol, Linux, Domain Name System (DNS), Elasticsearch, Identity and Access Management, Virtual Private Networks (VPN), Python (Programming Language), Linux System Administration, Linux Servers, Linux Support, Logical Volume Manager, Windows Servers, Routing, Nginx, OpenID, Package Management Systems, Windows PowerShell, Red Hat Enterprise Linux, Logstash, Ansible, Runbook, Security Assertion Markup Language (SAML), Shell Script, Single Sign-On, Virtual Machines, SSL Certificate Management, Data Logging, Scripting, Transport Layer Security, File Transfer Protocol (FTP), Gerrit, Grafana, Software Troubleshooting, Firewalls (Computer Science), Amazon Virtual Private Cloud (VPC), Kubernetes, ZFS File System, Hardware Asset Management, Kibana, Firewall Services Module, Terraform, Network Server, Docker, Jenkins - **Published:** November 14, 2026 - **Apply:** https://www.careerboard.com/us/en/find-jobs-in-United-States/-4DF4EA05520B181C9A/ ## About the Role * 7+ years in infrastructure or systems engineering, with recent ownership of a hybrid on-premises and cloud environment * Expert-level Linux administration (Ubuntu and RHEL/Rocky): systemd, Shell scripting, package management and repositories, storage on hypervisor hosts (ZFS or LVM-thin) including capacity monitoring and disk failure recovery, networking, performance troubleshooting, and users, sudo, and SSH at scale * Proven experience supporting engineers on many Linux systems, including build machines, test systems, and developer escalations * Hands-on depth with virtualization on Linux (Proxmox preferred) and AWS (EC2, VPC, IAM, S3) * Backup and recovery, including restores you have run yourself and recovery after a VM or host failure * Configuration management with Ansible and Scripting in Bash, PowerShell, or Python * Container experience with Docker or Podman and systemd * A habit of writing things down: diagrams, standards, and runbooks someone else can follow * Degree or equivalent relevant experience * Windows Server administration * Working knowledge of firewalls, routing, VPN, and DNS/DHCP * Reverse proxies and certificate management (nginx, Traefik) * Rootless Podman with systemd Quadlets * Axcient and Proxmox Backup Server * Proxmox clustering, including quorum and Corosync failure scenarios * Infrastructure as code with Terraform * Kubernetes and Helm * ELK (Elasticsearch, Logstash, Kibana) and Grafana * Running Jenkins and Gerrit instances * Entra ID single sign-on and federation (SAML and OIDC) * Supporting manufacturing or engineering workloads ## Description * Servers, hypervisor hosts, storage, and UPS at our locations, including racking, cabling, out-of-band management (IPMI/iLO/iDRAC), and NAS storage * Hardware lifecycle, capacity planning, and patching, including failed-disk replacement and data recovery * The compute foundation for the new Solon factory and headquarters AWS and virtual compute * AWS accounts, regions, EC2, storage, and ECR, including account lifecycle and AWS health and abuse notices * Virtual machines and clusters on-premises and in AWS, for every team that runs on them: Proxmox installs, VM standards, P2V and rehosting of physical servers, and AWS image imports * Backup and recovery for the infrastructure IT owns, tested rather than assumed: Axcient, Proxmox Backup Server, drive imaging, and AWS image restores, including backups of the DHCP, DNS, and Firewall configurations * Linux and Windows server hardening for the hosts IT owns Containers, Linux, and services * The container platform: rootless Podman with systemd Quadlets, Portainer, the private registry, and the standards for how services are deployed * Ansible-based deployment with least-privilege access, so application teams can deploy without IT involvement * Reverse proxies and certificates: nginx and Traefik, SSL issuance and renewal, and the standard for publishing applications through the proxy * Linux server installs, user, sudo, and SSH key provisioning, and a defined process for developer requests for root access, build machines, and test VMs * Hands-on Linux support for our engineers at the operating system level: build machines, test systems, packages, networking, storage, and performance * The instances behind internal services such as Jenkins, Gerrit, PyPI, and FTP/EDI. IT stands up and runs the instances. The teams own their projects and pipelines. Automation and observability * Infrastructure as code and scripts in Bash, PowerShell, and Python that make provisioning and routine operations repeatable * Logging, monitoring, and dashboards for the platform, with ELK and Grafana * Single sign-on for the platforms IT hosts, working with the IT administrators who own identity Standards and the team around you * Written infrastructure standards in Confluence, treated as a deliverable of the role, not a byproduct * A clear line with application owners: you run the platform, they run what is on it * Cross-trained backup with our compute engineer in Belgrade, and they for you * A working dependency with the network side: you build and host the DNS, NTP, proxy, and DHCP Servers and back up their configurations; the network side configures and operates the services on them and owns connectivity between our sites and AWS * Enough network depth to troubleshoot firewalls, routing, VPN, DNS, and DHCP and keep the core network running during an outage * Change plans with validation and rollback steps for production changes * Architecture reviewed by our CISO before it ships