Key Responsibilities

Own the AWS infrastructure end to end

You are responsible for the health of our AWS environment. Not just aware of it, responsible for it.
Design, build, and maintain core infrastructure: EC2, ECS/EKS, RDS, DynamoDB, S3, ALB, VPC, IAM, CloudWatch and the rest of the stack.
Know where every single production workload lives, what it depends on, and what breaks if it goes down. No black boxes you haven’t opened.
Proactively identify and fix things that are fragile before they break in production, not after.

Build CI/CD that engineers actually trust

Deploying software should be fast, safe, and boring. That is your goal.
Own the CI/CD pipeline for our Java/Spring Boot microservices end to end. From code commit to production, with proper gates at every stage.
Build rollback mechanisms that actually work. A deployment that can’t be undone in under 5 minutes is a liability.
Work with engineering teams to improve build times, reduce flakiness, and make deployments something developers do confidently, not nervously.

Take reliability seriously, not as a metric, as a mindset

When something breaks, be the person who stays until it is understood, not just resolved. There is a difference.
Write postmortems that find the real cause. “Human error” is never the root cause. Something in the system made human error possible, find that.
Build runbooks, on-call rotations, and escalation paths that mean nobody has to improvise during an incident.
Track and improve the metrics that matter: MTTR, deploy frequency, change failure rate. Make them go in the right direction every month.

Infrastructure as Code. No exceptions !

Every resource in AWS should be declared in code. If it was clicked into existence in the console and isn’t in terraform (or equivalent), it is tech debt and it is yours to clean up.
Version control, review, and test infra changes the same way you’d treat application code. No cowboy changes in prod.

Keep developers fast

Your upstream customer is the engineering team. Make their lives easier: faster builds, cleaner environments, self-service tooling where possible.
Reduce the number of things a developer has to ask you to do. Every manual handoff is a bottleneck.

Qualifications, Skills, And Experience

3+ years working in a DevOps, SRE, or infrastructure engineering role, ideally at a product company running real production workloads on AWS.
Deep AWS hands-on experience. Not just “familiar with”, you should be able to design a resilient, secure, cost-efficient architecture on AWS from scratch and explain every tradeoff.
You write infrastructure as code. Terraform preferred. If it’s not in version control, it doesn’t exist.
Strong CI/CD experience, building and maintaining pipelines for Java or similar backend services. You should be able to look at a pipeline and immediately spot what would go wrong at 10x the deploy frequency.
You understand networking: VPCs, subnets, security groups, load balancers, DNS. When someone says “it’s a network issue” you can verify that or prove it isn’t.
Experience with observability tooling: CloudWatch, ELK/OpenSearch, or similar. You know the difference between a dashboard and actual observability.
PostgreSQL and DynamoDB operational experience. Their backups, replication, slow query investigation, connection pooling. Database failures are not someone else’s problem.
You have been on-call. You know what that means and you take it seriously.

Skills: cd,ci,devops,infrastructure,aws

The Versatile Club

New Jobs