Contract - Cloud Infrastructure Engineer

Contract – Cloud Infrastructure Engineer

Rate: Open

Location: Chicago, IL

Hybrid: 3 days onsite, 2 days remote

Duration: 6+ months

• We are unable to provide sponsorship for this role*

Qualifications

• 3-5+ years of experience in the following:

• Infrastructure-as-Code using Terraform, AWS Cloud

Formation/Ansible; provisioning and managing cloud resources across AWS and Azure.

• Cloud-native container orchestration: Kubernetes (EKS preferred)/Rancher-k8s, including cluster operations, workload deployment, and project/namespace governance.

• CI/CD pipeline development using tools such as Git

Hub Actions, AWS Code

Pipeline, Git

Lab CI, or Azure Dev

Ops Pipelines.

• 2–3+ years of experience in the following:

• Git

Ops delivery patterns using ArgoCD or equivalent; managing declarative application state from git repositories.

• Secrets management and PKI: Hashi

Corp Vault configuration and operations / AWS KMS & Secrets Manager.

• 1–3+ years of experience in the following:

• Observability and monitoring: Prometheus, Grafana, Elasticsearch, AWS Cloud

Watch/Cloud

Trail or equivalent enterprise logging and alerting tooling.

• Working knowledge of enterprise networking: ingress controllers (Traefik or equivalent), load balancers, security groups, and certificate-based authentication.

• Familiarity with Git

Hub Copilot or AI-assisted developer tooling integration within a CI/CD or developer environment context.

• Strong UNIX/Linux fundamentals; comfortable operating in terminal-first infrastructure environments.

• Experience working from a backlog in a planned work management tool (Jira or equivalent); ability to operate autonomously against a defined delivery roadmap.

Responsibilities

• Maintain and extend Infrastructure-as-Code (IaC) patterns using Terraform for both AWS and Azure environments within the Enterprise Lab Zone.

• Operate and evolve the Enterprise Lab management plane: EKS cluster configuration, Git

Lab CI/CD runners, ArgoCD deployments, Vault PKI, Traefik ingress, and AWS Code

Pipeline.

• Resolve outstanding Azure/Entra billing and governance issues; bring Azure under the same unified governance model as AWS.

• Maintain resource tagging compliance, cost visibility, and sandbox lifecycle controls (90%/100% cost thresholds) across both cloud providers.

• Build and populate the Architecture Pattern Catalog: approved IaC patterns enabling users to provision sandbox environments without manual OTSI Engineering intervention.

• Implement self-service cloud catalog to provision compute resources to sandbox environment(s).

• Instrument and validate the Deployment Time SLA — the time from session start to a provisioned environment — targeting a threshold that makes 1-hour and 1-day lease durations frictionless for end users.

• Contribute developer environment patterns to the catalog to expand the Enterprise Lab user base beyond infrastructure-only experiments.