Qentelli - AWS DevOps Engineer

Qentelli

4 - 10 Years

Hyderabad

AWS DevOps Cloud Infrastructure Terraform Kubernetes CI/CD Pipeline YAML IAC Terraform

Posted on: 30/06/2026

Job Description

Job Description :

Experience :

- 4 years of professional experience in DevOps, cloud infrastructure, or platform engineering with a meaningful portion of that time writing Terraform and managing Kubernetes in production, not solely maintaining existing pipelines.

- Demonstrable experience provisioning and operating a cloud environment from scratch: you have written Terraform that someone else could run in a new AWS account and get a working environment not just modified existing configs.

- Production Kubernetes experience : you have debugged CrashLoopBackOff pods at 2am, understood why a Deployment was not scheduling, and tuned resource requests/limits based on actual usage data.

- Experience designing CI/CD pipelines end-to-end : build through production promotion, including security gates (SAST, container scanning) and approval workflows not just maintaining YAML that someone else wrote.

- Experience with secrets management in production : Vault, AWS Secrets Manager, or an equivalent at the level of configuring auth methods and lease policies, not just calling the API.

- Familiarity with service mesh concepts : you understand why mTLS matters, what a VirtualService does, and how to read Istio telemetry even if you have not operated Istio in production yourself.

Education :

- Bachelor's degree in Computer Science, Software Engineering, or a related technical discipline OR equivalent practical experience.

- Relevant certifications (CKA, AWS Solutions Architect, AWS DevOps Engineer, HashiCorp Terraform Associate, GCP Professional DevOps Engineer) are a positive signal and demonstrate structured knowledge but demonstrable production experience outweighs certifications.

Personal attributes we look for :

- Infrastructure-as-code fundamentalism : manual production changes make you uncomfortable not because of policy, but because you genuinely understand why they are dangerous in a stateful, multi-service platform.

- Security by default : you include IAM policies, secret rotation, and network policies in your first PR not in a follow-up ticket labelled 'hardening'.

- Documentation as a deliverable : a runbook, an architecture diagram, or an ADR is as real a deliverable to you as a Terraform module; you know that the platform is only as operable as its documentation.

- Curiosity about AI workloads : you do not need to understand machine learning, but you need to care about what it means to schedule GPU pods, manage model artefact storage, and keep a 2M-node graph database healthy at production scale.

- Collaborative ownership : this platform has 6 engineering teams; effective platform engineering here means building self-service tooling that makes every team faster not becoming a gatekeeper.