This one is the “keep the plane in the sky while we upgrade the engines” job. If you’re the kind of engineer who likes owning EKS end-to-end, standardizing how teams ship across clusters, and being the calm adult in the room when prod acts up, this is your lane.
About Dutchie
Dutchie powers dispensary operations and consumer access across 40+ cannabis markets in the U.S. and Canada. It’s high-volume, regulated, and infrastructure-heavy in the ways that actually matter.
Schedule
- Remote
- Senior ownership + cross-team influence
- You’ll be a “platform multiplier,” not a ticket-taker
What You’ll Do
⦁ Own and evolve EKS across multiple clusters (reliability, security, scalability)
⦁ Standardize multi-cluster deployment patterns and best practices
⦁ Serve as cloud infrastructure SME, guiding teams on decisions and tradeoffs
⦁ Mentor engineers on Kubernetes, AWS, and cloud-native patterns
⦁ Build infra that balances performance, cost, and security
⦁ Partner with dev teams to improve deployment + operations workflows
⦁ Maintain infrastructure-as-code (Pulumi/Terraform) for reproducibility
⦁ Implement cloud security best practices (network policies, IAM, compliance)
What You Need
⦁ Deep Kubernetes experience, specifically production EKS at scale
⦁ Strong AWS fundamentals: EKS, IAM, VPCs, security groups, networking
⦁ Solid Linux troubleshooting + performance tuning
⦁ Docker + orchestration patterns
⦁ IaC with Pulumi or Terraform
⦁ Python or Go for automation/tooling (production-quality)
⦁ Security-first mindset
⦁ 5+ years cloud infrastructure/platform experience (degree or equivalent)
Bonus Points
⦁ Service mesh (Linkerd/Istio)
⦁ GitOps (ArgoCD/Flux)
⦁ Cloudflare (Workers especially)
⦁ Observability (Datadog/Prometheus/Grafana)
⦁ Cost optimization wins
⦁ Open source in cloud-native land
Benefits
⦁ Target salary range: $149,000–$200,000
⦁ Medical, dental, vision
⦁ Stock options
⦁ Tech allowance
⦁ Flexible vacation and sick days
Backbone note: the sneaky “interview winner” here is a story where you reduced toil and standardized deployments (think Helm/Kustomize patterns, GitOps rollout rules, multi-cluster strategy), plus a security/cost win you can quantify. If your resume reads like “I used Kubernetes,” you’re toast. If it reads like “I led a multi-cluster standardization that cut deploy failures 40% and shaved $X/month,” you’re dangerous.
Happy Hunting,
~Two Chicks…