Skip to main content

DevOps Engineer

Posted today

evlo aiMinneapolis (MN)

SENIORITY

Senior

Apply (opens in a new tab)

About the role

About The Role: The role sits at the intersection of infrastructure engineering and production reliability - building, automating, and operating the platform that runs customer-facing services at scale. You will work with software engineering teams to ship faster without breaking things: owning CI/CD pipelines, Kubernetes infrastructure, observability tooling, and the incident response practices that keep uptime in the four-nines range.
Key Responsibilities:
  • Design, build, and maintain cloud infrastructure on AWS using Terraform and Terragrunt, with infrastructure-as-code covering networking, compute, and data stores
  • Operate and scale Kubernetes clusters (EKS) handling production workloads, including cluster upgrades, autoscaling policies, and multi-AZ resilience
  • Build and maintain CI/CD pipelines in GitHub Actions and ArgoCD supporting safe, frequent deployments with canary and blue-green strategies
  • Instrument services with Prometheus, Grafana, and Open
  • Telemetry; own SLO definitions, alerting thresholds, and dashboards used across the org
  • Lead incident response for production outages - triage, mitigation, root cause analysis, and blameless postmortems with actionable follow-ups
  • Harden infrastructure security: IAM least-privilege policies, secrets management with Vault, network segmentation, and compliance-driven audit readiness
  • Drive capacity planning and cost optimization across cloud spend, identifying savings without sacrificing reliability or performance
What We Are Looking For:
  • 3-6 years of experience in DevOps, SRE, or infrastructure engineering roles supporting production systems
  • Strong hands-on experience with AWS (EKS, EC2, RDS, IAM, VPC) and infrastructure-as-code with Terraform
  • Deep working knowledge of Kubernetes: deployment strategies, Helm, operators, and troubleshooting workloads in production
  • Proficiency with observability stacks (Prometheus, Grafana, Datadog, or similar) and designing actionable alerting, not noise
  • Solid scripting skills in Python, Bash, or Go for automation and tooling
  • Experience running on-call rotations and leading incident response at a team level
Bonus: GCP or multi-cloud experience, service mesh (Istio/Linkerd), GitOps tooling (ArgoCD/Flux), and Kubernetes certifications (CKA/CKS)

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this