We are looking for a DevOps engineer to take ownership of our infrastructure.
You would be the person responsible for it. Not one of twelve people on a platform team, and not someone working through a queue of tickets. You would work directly with the CTO, and the calls you make would actually get shipped.
What you would be doing
You would own our AWS setup, which means provisioning, scaling, keeping costs sane, and keeping it reliable. You would run our Kubernetes clusters and make them better than you found them. You would look after our CI/CD pipelines so the rest of the engineering team can ship without holding their breath.
A big part of the job is making sure we find out about problems before our users do, so monitoring, alerting, and logging would be yours to build and improve. Anything still being done by hand, you would move into Terraform and leave it there.
Security is part of the role too. IAM, secrets, network boundaries, and rotating certificates and keys before they expire on us.
You would be on call, and we would like your help making on call something people do not dread.
What we are looking for
- 2 to 4 years working in DevOps, SRE, cloud, or infrastructure
- Solid hands on AWS. EC2, S3, VPC, IAM, RDS, CloudWatch, CloudFront, ECS or EKS
- Kubernetes in production. We would rather hear about a pod you debugged at 2am than a tutorial you finished
- You have owned CI/CD pipelines. Jenkins, GitHub Actions, GitLab CI, whatever you have used
- Comfortable on Linux and writing shell scripts
- Docker and containers
- Terraform, or another infrastructure as code tool
- Git, and a clear picture of how code gets from a branch to production
Nice to have, not required
- Python or Node.js for automation
- Prometheus, Grafana, ELK, or Datadog
- Experience bringing AWS costs down at scale
- Databases and caching. RDS, Redis, backups and restores you have actually tested
- Video streaming or CDN infrastructure
- An AWS certification
What actually matters to us
If you have had to do something twice by hand, you automate it the third time. You write things down so the next person does not have to work it out again. You stay calm when production is down, and you say so when you are the reason it went down. And when you do not know something, you tell us instead of guessing.
