Skip to content
MacawsHub

Mid-level DevOps Engineer

Own the infrastructure that keeps our clients' production systems running — Terraform-managed AWS, CI/CD, observability, and the on-call we sleep through.

Level: Mid Team: DevOps Location: Remote — EU & MENA Type: Full-time

About the role

You’ll own the infrastructure for a couple of client engagements at a time — typically AWS, sometimes multi-account, occasionally hybrid with on-prem or VPS. The engineering teams ship through pipelines you build, and the on-call rotation is shared with you.

We’re not looking for a “click-ops” engineer — every change is in Terraform, reviewed, and idempotent. If you’ve ever fixed an outage and then automated the post-mortem fix, this is the team.

How we hire

One intro call → a paid short Terraform + AWS scenario take-home (real-shaped, not trick questions) → a 60-minute working session walking through your submission → an offer. About two weeks end to end.

What you'll do

  • Design and maintain AWS infrastructure across multiple client environments — VPC, ECS/EKS, RDS, S3, CloudFront, IAM.
  • Manage all infrastructure as code in Terraform — modules, state, drift detection, review workflow.
  • Build and own CI/CD pipelines (GitHub Actions, GitLab CI) for the engineering teams to ship through.
  • Set up observability — metrics, logs, traces, alerts — so we know what's wrong before the client does.
  • Participate in on-call rotation for client production environments (one week every six, post-onboarding).

What we're looking for

  • 3–5 years of professional DevOps / SRE / platform-engineering experience in production.
  • **Terraform is a must** — you can write modules, manage state safely, and reason about plan/apply edge cases.
  • **AWS is a must** — you've built and run real workloads on AWS, not just toy examples.
  • Strong Linux fundamentals — networking, systemd, troubleshooting from the shell.
  • Comfortable scripting in at least one of Bash, Python, or Go.
  • Real experience with Docker and at least one container orchestrator (ECS or EKS preferred).

Nice to have

  • Kubernetes-in-production experience (EKS, Helm, ArgoCD).
  • Security hardening — IAM least-privilege, secrets management, threat-modeling AWS architectures.
  • Cost-optimization work on real AWS bills.
  • Multi-region or multi-account AWS organization design.

How we work

  • Outcomes over output

    We don't bill for activity. We commit to outcomes you can put on a slide.

  • Senior by default

    Every engagement starts with senior engineers. No bait-and-switch.

  • Honest in writing

    If a feature won't move the metric, we'll tell you — in writing — before the sprint starts.

  • Built to be inherited

    Code, docs, runbooks, infra-as-code. We design every engagement to be handed off.

Let's build something your customers brag about.

Tell us where you are and where you want to go — we'll come back within one business day with an honest opinion and a path forward.