Senior Cloud / DevOps Engineer — Infrastructure Location: Remote (Global) Team: Infrastructure / Platform Engineering Client: TBD Summary You'll own and evolve our client's production cloud infrastructure on AWS — keeping it secure, observable, and scalable as the company and its client portfolio grows. This isn't a build-from-scratch role; it's about being the person who knows the system deeply, improves it deliberately, and keeps things from catching fire. You'll work across a mature but actively evolving stack, with real ownership and no bureaucratic layers between you and the infrastructure. Requirements (Must-Haves) Excellent English communication skills — you'll interact directly with internal engineering teams and, at times, with external client stakeholders to align on infrastructure needs. 5+ years of hands-on cloud infrastructure experience in production AWS environments. Deep AWS expertise — EC2, VPC, IAM, networking, and the broader AWS ecosystem. You know the console, the CLI, and when to use each. Kubernetes in production — you've managed real workloads on EKS or ECS, handled node scaling, and debugged cluster-level issues. Helm and Karpenter experience is expected. Terraform as your default IaC tool — you write modules, manage state, and don't let drift happen. Terragrunt experience is a strong plus. GitOps mindset — you've used ArgoCD or a similar tool and understand why declarative, version-controlled deployments matter. Autonomous and senior-minded — you can assess a system, identify what needs fixing, and prioritize without someone handing you a roadmap. Requirements (Nice-to-Haves) Terragrunt — managing multi-environment or multi-account Terraform at scale. Observability stack — hands-on with Datadog, Prometheus/AlertManager, or CloudWatch beyond just dashboards. You've built alerts that actually fire when they should. Security tooling — familiarity with Security Hub, GuardDuty, CloudTrail, or Inspector. Bonus if you've worked toward SOC 2 or AWS Foundational Security Best Practices. CI/CD pipelines — Jenkins or GitHub Actions for infrastructure or application delivery. ECR for container registry management. Serverless — Lambda and EventBridge for event-driven patterns or automation tasks. Databases — experience operating Aurora MySQL (RDS) and ElastiCache Memcached in production. Bonus Points Experience with Akamai properties or CDN configuration at the edge (AMD / Adaptive Media Delivery is a meaningful plus). IAM / IRSA design at scale — you've thought carefully about least-privilege in a Kubernetes-on-AWS context. AWS Secrets Manager and SSM Parameter Store experience in a real secrets management workflow. Experience supporting multiple client environments or a multi-tenant infrastructure model. AWS certifications (Solutions Architect, DevOps Engineer Professional) — not required, but signals depth.
Senior Cloud / DevOps Engineer — Infrastructure
Senior Cloud / DevOps Engineer — InfrastructureLocation: Remote (Global)
Location:Team: Infrastructure / Platform Engineering
Team:Client: TBD
Client: TBDSummary
SummaryYou'll own and evolve our client's production cloud infrastructure on AWS — keeping it secure, observable, and scalable as the company and its client portfolio grows. This isn't a build-from-scratch role; it's about being the person who knows the system deeply, improves it deliberately, and keeps things from catching fire. You'll work across a mature but actively evolving stack, with real ownership and no bureaucratic layers between you and the infrastructure.
Requirements (Must-Haves)
Requirements (Must-Haves)- Excellent English communication skills — you'll interact directly with internal engineering teams and, at times, with external client stakeholders to align on infrastructure needs.
Excellent English communication skills- 5+ years of hands-on cloud infrastructure experience in production AWS environments.
5+ years- Deep AWS expertise — EC2, VPC, IAM, networking, and the broader AWS ecosystem. You know the console, the CLI, and when to use each.
Deep AWS expertise- Kubernetes in production — you've managed real workloads on EKS or ECS, handled node scaling, and debugged cluster-level issues. Helm and Karpenter experience is expected.
Kubernetes in production- Terraform as your default IaC tool — you write modules, manage state, and don't let drift happen. Terragrunt experience is a strong plus.
Terraform as your default IaC tool- GitOps mindset — you've used ArgoCD or a similar tool and understand why declarative, version-controlled deployments matter.
GitOps mindset- Autonomous and senior-minded — you can assess a system, identify what needs fixing, and prioritize without someone handing you a roadmap.
Autonomous and senior-mindedRequirements (Nice-to-Haves)
Requirements (Nice-to-Haves)- Terragrunt — managing multi-environment or multi-account Terraform at scale.
Terragrunt- Observability stack — hands-on with Datadog, Prometheus/AlertManager, or CloudWatch beyond just dashboards. You've built alerts that actually fire when they should.
Observability stack- Security tooling — familiarity with Security Hub, GuardDuty, CloudTrail, or Inspector. Bonus if you've worked toward SOC 2 or AWS Foundational Security Best Practices.
Security tooling- CI/CD pipelines — Jenkins or GitHub Actions for infrastructure or application delivery. ECR for container registry management.
CI/CD pipelines- Serverless — Lambda and EventBridge for event-driven patterns or automation tasks.
Serverless- Databases — experience operating Aurora MySQL (RDS) and ElastiCache Memcached in production.
DatabasesBonus Points
Bonus Points- Experience with Akamai properties or CDN configuration at the edge (AMD / Adaptive Media Delivery is a meaningful plus).
- IAM / IRSA design at scale — you've thought carefully about least-privilege in a Kubernetes-on-AWS context.
- AWS Secrets Manager and SSM Parameter Store experience in a real secrets management workflow.
- Experience supporting multiple client environments or a multi-tenant infrastructure model.
- AWS certifications (Solutions Architect, DevOps Engineer Professional) — not required, but signals depth.