Overview
This is a project-based contract engagement supporting the OTSI Engineering team. The role ensures continuity of Enterprise Lab delivery during a planned team capacity transition. The Enterprise Lab is OTSI's sandbox and strategic experimentation platform, and this engagement focuses on infrastructure build-out, self-service provisioning, and cloud governance across AWS and Azure.
Scope of Work
Enterprise Lab Infrastructure (AWS + Azure) Maintain and extend Infrastructure-as-Code (IaC) patterns using Terraform across both cloud environments. Operate and evolve the Enterprise Lab management plane, including EKS cluster configuration, GitLab CI/CD runners, ArgoCD deployments, Vault PKI, Traefik ingress, and AWS CodePipeline. Resolve outstanding Azure/Entra billing and governance issues, bringing 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 providers.
Self-Service Provisioning Pipeline Build and populate an Architecture Pattern Catalog of approved IaC patterns that allow users to provision sandbox environments without manual OTSI Engineering intervention. Implement a self-service cloud catalog for compute provisioning and instrument a Deployment Time SLA — targeting provisioning speeds that make 1-hour and 1-day lease durations frictionless. Contribute developer environment patterns to broaden the Enterprise Lab user base beyond infrastructure-only experiments.
Git Persistence Model Operationalize the git persistence model: IaC patterns stored in approved experiment repositories, with a documented and repeatable redeploy workflow validated end-to-end. Ensure all sandbox environments are fully reproducible from repository state with no persistent compute assumed across lease cycles. Support integration with GitHub Actions and the broader GitOps delivery pipeline. Document workflows, catalog usage patterns, and environment architecture in the work management platform and experiment repositories.
Required Skills & Experience
- 3–5 years — Infrastructure-as-Code with Terraform, AWS CloudFormation, and/or Ansible; provisioning and managing resources across AWS and Azure
- 3–5 years — Cloud-native container orchestration with Kubernetes (EKS preferred), including cluster operations, workload deployment, and namespace governance
- 3–5 years — CI/CD pipeline development using GitHub Actions, AWS CodePipeline, GitLab CI, or Azure DevOps Pipelines
- 2–3 years — GitOps delivery patterns with ArgoCD or equivalent; managing declarative application state from git repositories
- 2–3 years — Secrets management and PKI using HashiCorp Vault, AWS KMS, or Secrets Manager
- 1–3 years — Observability and monitoring with Prometheus, Grafana, Elasticsearch, AWS CloudWatch/CloudTrail, or equivalent
- Working knowledge of enterprise networking: ingress controllers (Traefik or equivalent), load balancers, security groups, and certificate-based authentication
- Familiarity with GitHub Copilot or AI-assisted developer tooling in a CI/CD or developer environment context
- Strong Unix/Linux fundamentals; comfortable in terminal-first infrastructure environments
- Experience working from a backlog in Jira or equivalent; able to operate autonomously against a defined delivery roadmap