DevOps Engineer

DevOps Engineer

Have you kept a production Kubernetes cluster alive at 2am and actually enjoyed the puzzle of it? Can you look at a cloud bill and know exactly which service is quietly bleeding money? Do you build monitoring in from day one instead of scrambling to add it after the first outage?

Then, our DevOps Engineer role here at CUBE84 may interest you.

In this gig,

1. You build the pipes everyone else ships through
   You design, build, and maintain CI/CD pipelines in Jenkins across the teams services. When a pipeline breaks at a bad time, youre the one who fixes it — and then makes sure it doesnt break that way again.

2. You own the infrastructure, not just the servers
   You manage infrastructure across GCP and AWS — provisioning, scaling, access control, and cost — and you actually watch the cost side, not just the uptime side.

3. You containerize and orchestrate like its second nature
   You containerize applications with Docker and run them in production on Kubernetes, at a scale where "it works on my laptop" stopped being a useful sentence a long time ago.

4. You catch problems before they become tickets
   You set up monitoring, logging, and alerting so issues get caught before users notice them, and you automate deployment and rollback so a release never depends on someone remembering to run three manual steps in the right order.

5. Youre calm when production isnt
   You work with the engineering team on incidents — triage, root cause, and the fix that actually prevents a repeat, not just the patch that buys time until it happens again.

6. You write it down so the next person isnt stuck guessing
   You document infrastructure and runbooks so on-call knowledge lives somewhere other than your head.

Itll be awesome if you...

• Have 3-5 years in a DevOps, SRE, or infrastructure engineering role

• Have production experience with both GCP and AWS (this ones non-negotiable)

• Have hands-on Jenkins experience — building, maintaining, and debugging CI/CD pipelines, not just clicking through an existing one

• Have run Docker in production and Kubernetes orchestration at more than a toy scale

• Are comfortable with Linux administration and shell scripting

• Work in a Git-based workflow with code review on infrastructure changes

More awesome, if you have

• Infrastructure as code experience — Terraform, Pulumi, or CloudFormation

• Observability tooling experience — Prometheus, Grafana, Datadog, or similar

• Configuration management experience, such as Ansible

• Security fundamentals — IAM policy design, secrets management, network segmentation