DevOps Engineer

These are the explicit baseline requirements captured in the internal JD.
Proficiency in DevOps practices and tooling
Strong understanding of Continuous Integration and Continuous Deployment (CI/CD) practices
Hands on experience with containerization technologies such as Docker and Kubernetes
Familiarity with cloud platforms such as AWS, Azure, or Google Cloud (with Azure commonly preferred)
Experience with CI/CD tools (e.g., Azure DevOps, GitHub Actions, Jenkins)
Knowledge of Infrastructure as Code (IaC) using tools like Terraform
Familiarity with scripting languages such as Python, Bash, or Ruby
Ability to collaborate with stakeholders, translate requirements into technical pipelines, and contribute to code reviews and quality improvements

Good to Have (Commonly Requested, Not Universal)

These skills enhance deployability but are not mandatory for every DevOps demand.
Experience with Kubernetes Helm charts and YAML scripting for environment configuration
Exposure to database platforms such as PostgreSQL in support of application deployments
Comfort working closely with application teams (UI/UX, backend, QA) in Agile delivery models
Note: The JD does not explicitly separate a Good to Have list the above items are derived from the Professional & Technical Skills section and framed as commonly valued enrichers.

Depending on Client Needs (Demand Specific / Program Driven Overlays)

Use these selectively based on the client s cloud strategy, DevOps maturity, and delivery model.
Cloud specific depth (Azure first vs AWS first vs multi cloud) depending on client environment
Stronger focus on GitOps, secrets management, and environment governance in regulated or scale programs
Emphasis on platform reliability, monitoring, and operational excellence for AMS / production heavy roles
Expanded responsibility for incident response and continuous improvement in mature DevOps organizations
(These are positioned as overlays because they are not explicitly enumerated in the JD text but are commonly toggled per client engagement.)