Job Description
DevOps Engineer
\n
\n
Location: Remote (US) | Type: Contract | Experience: 4 to 7 years | Pay: $65-$75/hr
\n
\n
About the Role
\n
We're hiring a DevOps Engineer to design, run, and troubleshoot large microservices estates on Kubernetes in production for enterprise clients moving to and scaling on AWS. You'll build cloud-native CI/CD for containers, define infrastructure as code, and be the person developers turn to when a deployment, a cluster, or a pipeline needs to behave.
\n
\n
This is an 8-month contract with extensions, embedded on the professional services delivery team of an AWS-focused cloud services and modernization consultancy. The work is client-facing, so you'll be representing the practice in front of engineering teams who expect you to know your stuff.
\n
\n
If you've kept real workloads healthy on Kubernetes, not just stood up a cluster for a demo, this role will feel familiar in the best way.
\n
\n
What You'll Do
\n
- \n
- Design, deploy, and troubleshoot microservices estates running on Kubernetes (EKS) in production
- Deploy and integrate service mesh tooling such as Istio, Linkerd, or Consul, and manage Helm charts and Custom Resource Definitions
- Architect and maintain CI/CD pipelines for containers using Jenkins, GitLab, CodePipeline, CodeDeploy, or similar
- Define AWS infrastructure in Terraform, CloudFormation, or CDK so environments are repeatable from dev through production
- Guide client developers on AWS architecture, git branching strategy, and pipeline best practices
- Use tagging and usage data to support cost analysis and keep infrastructure efficient
- Help plan and execute migrations from on-premises environments to AWS, including microservices-based applications
- Join daily delivery standups and push back on implementation approaches when there's a better path
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Qualifications
\n
Core Experience
\n
- \n
- 4 to 7 years of DevOps or SRE experience in AWS environments or supporting software development teams
- 3+ years running microservices on Kubernetes in production
- 4+ years building AWS cloud infrastructure and 4+ years developing CI/CD pipelines
- Hands-on container development and orchestration with Kubernetes, EKS, Helm, and CRDs
- Strong working knowledge of AWS security practices
\n
\n
\n
\n
\n
\n
Tooling and Languages
\n
- \n
- Proficient in Infrastructure as Code (Terraform or CloudFormation) and configuration management (Ansible, Chef, or Puppet)
- Solid Linux and Docker fundamentals
- Comfortable scripting in Bash plus at least one language such as Python, Go, or Java
- Experience delivering in Agile teams
\n
\n
\n
\n
\n
Nice to Have
\n
- \n
- Certified Kubernetes Administrator (strongly preferred), or AWS Solutions Architect or DevOps Engineer Professional
- GitOps in production with ArgoCD and app-of-apps patterns, plus Prometheus and Grafana
- Code analysis and testing tools wired into CI/CD, like SonarQube or Selenium
- Advanced AWS networking and routing knowledge
- Open-source contributions
\n
\n
\n
\n
\n
\n
\n
Why Join Us
\n
You'll work alongside cloud engineers and architects who deliver AWS work for enterprise clients every day, where the expectation is fit-for-purpose solutions rather than "good enough."
\n
\n
Engagements are varied, the problems are real production problems, and the team values people who treat a blocker as a puzzle to solve.
\n
\n
With an 8-month runway and room to extend, this is a chance to go deep on meaningful Kubernetes work instead of hopping between short-term tickets.