Hadrian
Infrastructure Engineer
About this role
Hadrian seeks an experienced Infrastructure Engineer to design and lead the technical architecture of cloud, edge, and factory-floor systems supporting autonomous manufacturing across multiple sites. You'll define infrastructure standards, build reusable platforms, and mentor engineers while balancing strategic decisions with hands-on implementation.
What you'll do
- Design and implement AWS cloud infrastructure using Terraform/OpenTofu with multi-cluster Kubernetes architecture
- Build CI/CD pipelines and GitOps workflows using GitHub Actions and ArgoCD
- Develop reusable infrastructure patterns including Terraform modules, Helm charts, and configuration schemas
- Architect networking solutions connecting cloud, edge devices, and factory-floor systems
- Implement monitoring and observability using Prometheus, Grafana, and Datadog
- Establish engineering standards, conduct architecture reviews, and mentor team members on infrastructure best practices
What they're looking for
- Infrastructure as Code (Terraform/OpenTofu)
- Kubernetes cluster management (EKS, K0s, K3s)
- AWS cloud architecture
- CI/CD and GitOps tools (GitHub Actions, ArgoCD)
- Networking and edge computing
- Security and compliance fundamentals
- Monitoring and observability platforms
- Technical documentation and communication
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Hadrian
Hadrian builds aerospace and defense manufacturing systems, offering enterprise software platforms, advanced tooling design, and highly automated production capabilities for the sector. The company is hiring full stack engineers, manufacturing and tooling specialists, infrastructure and identity management experts, and workforce systems architects to support its rapid scaling.
View all jobs at HadrianLikely interview questions
- Walk us through a multi-cluster Kubernetes architecture you've designed. What trade-offs did you make between cloud and edge, and how did you handle failover across sites?
- Describe a time you built reusable infrastructure patterns (Terraform modules, Helm charts) that significantly reduced toil for other engineers. How did you ensure adoption?