Devops Engineer

We are looking for a hands-on DevOps Engineer to help build and run reliable cloud infrastructure and CI/CD for our product teams. You will automate the boring stuff, ship repeatable environments, and keep services observable and secure. Expect real ownership, code in production, and the occasional on-call. What you do Build and maintain CI/CD pipelines (e.g., Azure DevOps) with proper build, test, security scans, and deploy stages. Write infrastructure-as-code (Terraform preferred; CloudFormation/Bicep acceptable) for cloud resources (AWS/Azure/GCP). Containerize apps (Docker) and manage Kubernetes basics: namespaces, deployments, services, ingress, secrets, and Helm releases. Implement monitoring, logging, and alerting (Prometheus/Grafana/Alertmanager, OpenTelemetry, ELK or cloud-native tools like CloudWatch/Azure Monitor/Stackdriver). Keep secrets and configs in the right places (Vault/AWS Secrets Manager/Azure Key Vault) and use least-privilege IAM. Contribute to release automation (blue/green, canary, rollbacks) and environment management across dev/SIT/UAT/prod. Harden images and infrastructure (CIS benchmarks where practical), run container and IaC scans (Trivy/Snyk/Checkov). Write runbooks and README-grade docs that others can actually follow; participate in incident response and post-mortems. Keep an eye on cost and right-size infra; tag resources so we can attribute spend. Ensure secure practices are followed. Must-have skills 2–3 years in DevOps/Platform/SRE or adjacent role with production exposure. Solid with Linux, Git, and one major cloud (AWS or Azure; GCP is a plus). CI/CD: able to author pipelines as code including cache, test parallelism, and artifact management (Artifactory/ECR/ACR/GCR). Containers & orchestration: Docker fundamentals, Kubernetes basics (kubectl, pods, deployments, services, logs, events). IaC: Terraform fundamentals (providers, modules, workspaces, remote state). Scripting: Bash plus one general-purpose language (Python/Go preferred). Observability basics: metrics vs logs vs traces, alerting that's actionable (low noise, high signal). Networking fundamentals: VPC/VNet, subnets, routing, security groups/NSGs, DNS, TLS. Clear written and verbal communication; bias for automation and ownership. Nice to have Azure DevOps Knowledge. Experience with Helm chart authoring. Exposure to message brokers (Kafka/RabbitMQ) and cache layers (Redis). Cost/FinOps fundamentals and tagging/chargeback practices. Skills: devops,cd,aws,cloud,ci,infrastructure,azure,code