DevOps Engineer
About this role
What You'll Do
Own the platform: Design, build, and operate the cloud infrastructure that runs our autonomous testing agents, from commit to production
Make shipping effortless: Build and harden CI/CD pipelines so engineers deploy daily with confidence, not anxiety
Infrastructure as code: Define everything in Terraform/Pulumi, reproducible, reviewable, and disposable
Scale the agents: Run containerised, orchestrated workloads on Kubernetes that spin up and tear down thousands of simulated user sessions on demand
Own reliability: Design observability, alerting, and incident response so we catch failures before customers do
Tame cost and performance: Keep the cloud bill sane while the workload grows 10x
What We're Looking For
Relentless drive: You execute fast, adapt faster
Startup scar tissue: You've kept production alive with no safety net
Cloud fluency: AWS/GCP, containers, Kubernetes, networking, IAM, you've built it, not just configured it
Automation reflex: If you've done it twice by hand, you've already scripted the third time
Reliability obsession: You care more about uptime and recovery than dashboards that look pretty
Security-aware by default: Secrets, least privilege, and supply-chain hygiene are habits, not afterthoughts
Ideal Background
There's no perfect pedigree. We hire for mindset, not credentials. That said, you might have:
Built and scaled infra for a high-velocity product from 0 to 1
Owned CI/CD and platform tooling for a fast-shipping engineering team
Run production workloads on Kubernetes under real load
Thrived in chaos with high ownership
Why This Matters
Software is accelerating. The infrastructure under it has to keep up. As AI ships more code faster, the platform that tests, deploys, and trusts that code becomes the bottleneck, or the unlock.
Five years from now, every high-velocity team will run on infrastructure like the one you'll build here. Join now, and help make that future real, before someone else does.
Company at a glance
As AI commoditises code generation, the bottleneck moves from writing software to trusting it. Verification is the layer that determines whether AI-generated code ships to production or stalls in review.
Code-level tests rot every time the implementation changes.
Product-level verification does not care how the code was written, only whether the product still does what users came to do.
Duku continuously simulates your users so you can trust every release, before it ships.
Tired of cold applications?
Sign up with Clera and we'll reach out the moment a role actually fits you — no more spraying applications into the void.
Know someone who'd be great for this?