Devops Engineer AWS Cloud and Data Center Infrastructure

DevOps Engineer AWS Cloud and Data Center Infrastructure

Role

Summary

We are hiring a DevOps Engineer to build and run the delivery pipelines, infrastructure automation and platforms that span our AWS accounts and on-premises data centers. You will make deployments fast, repeatable and safe in both environments, and keep the hybrid connection between them reliable and secure.

The role works closely with Development, Infrastructure, Network and Security teams. It suits an engineer who is equally comfortable writing Terraform for AWS and troubleshooting a Linux VM or Kubernetes node in our own data center.

Role: Consultant/Contractual

Experience 

5+ years in DevOps, SRE or systems engineering; 3+ years hands-on AWS in production 

On-call participation in rotation for platform and pipeline incidents

Key responsibilities

CI/CD and release engineering

• Build and maintain CI/CD pipelines that deploy to both AWS and on-prem targets from a single workflow.
• Implement deployment strategies such as blue/green, canary and rolling releases, with automated rollback.
• Manage artifact repositories, container registries and versioning standards.

Infrastructure as code

• Provision and manage AWS infrastructure with Terraform (or CloudFormation/CDK), using reusable modules and remote state.
• Automate on-prem servers, VMs and network configuration with Ansible and Terraform providers for vSphere or Nutanix.
• Enforce code review, testing and drift detection for all infrastructure changes.

Platforms and containers

• Operate Kubernetes on Amazon EKS and on-prem (e.g., Rancher, OpenShift or upstream), plus ECS where used.
• Standardize Helm charts, GitOps workflows and cluster add-ons across both environments.

Hybrid connectivity and cloud operations

• Maintain the AWS landing zone: multi-account structure, VPCs, Transit Gateway, and Direct Connect or site-to-site VPN to the data center.
• Manage hybrid DNS (Route 53 Resolver), identity federation and secrets across environments.
• Track and optimize AWS spend with tagging, rightsizing and Savings Plans.

Reliability, observability and security

• Build monitoring, logging and alerting that give one view across AWS and on-prem.
• Define SLOs, run incident response and lead blameless post-incident reviews.
• Embed security in pipelines (DevSecOps): code, dependency, container and IaC scanning, least-privilege IAM, and secrets management.
• Support backup, disaster recovery and DR testing for cloud and on-prem workloads.

Enablement

• Provide developers with self-service templates, documentation and golden paths.
• Document runbooks and mentor engineers on DevOps practices.

Required qualifications

Candidates must have built and operated production systems in AWS and on-prem, not one or the other. Candidates should be familiar with AWS core services, AWS architecture, Infrastructure as code, Configuration management, CI/CD, Containers, Linux, Scripting, Version control, On-prem infrastructure. Candidates should also be familiar with CI/CD, GitOps and delivery, Infrastructure as code, Configuration management, Containers and orchestration, Configuration management, Containers and orchestration, Artifacts and registries, Serverless and managed services, Observability, Networking, Security and DevSecOps, On-prem virtualization,Data and storage, Backup and DR, Hybrid and migration, Cost management, Operating systems, ITSM and collaboration. 

Preferred qualifications and certifications

Certifications are a plus. Nice to have one or more of the following certifications: AWS Certified DevOps Engineer, Certified Kubernetes Administrator (CKA), HashiCorp Certified: Terraform Associate, Red Hat Certified Engineer (RHCE) or RHCSA

What success looks like in the first year

Timeframe Outcome

30 days -Inventory of pipelines, environments and IaC coverage; quick wins identified

90 days -Standard pipeline template live for AWS and on-prem deployments; IaC drift reported

6 months -Unified observability across both environments; SLOs set for key services

12 months -Measurable gains in DORA metrics: deployment frequency, lead time, change failure rate and time to restore