Senior Engineer – AWS (FinOps)
AHEAD · Gurugram
—
Jul 26, 2026
Gurugram
Jul 27, 2026
What this job asks for AI summary
A senior cloud engineering role focused on cost management, governance, and automation across AWS, Azure, and GCP. Day-to-day work involves building cost dashboards, enforcing tagging standards, rightsizing cloud resources, managing reservations and savings plans, and developing automated workflows using infrastructure-as-code and CI/CD tooling. The role suits an experienced cloud or DevOps engineer with a background in FinOps or cloud cost optimization who is comfortable engaging directly with both engineering and finance stakeholders.
Senior level · 5+ years · Full-time
Quick apply — this platform usually takes a CV and a few fields.
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (7)
The posting's benefits section references India regulations and India employment benefits, indicating this role is based in India, not the United States — the US-based flag is set to false accordingly. No city or CBSA is specified.
The role blends cloud cost engineering (FinOps), infrastructure automation (IaC, CI/CD), and DevOps/SRE practices. It was mapped to Software Developers (15-1252) because the primary deliverables are writing automation code, IaC, and CI/CD pipelines; Network and Computer Systems Administrators (15-1244) is the runner-up given the significant infrastructure operations and cost governance component.
The 5+ years minimum is stated as 'minimum 5+ years in a customer-facing technical role'; a separate requirement of '3+ years designing, securing, and deploying large-scale cloud applications' is a sub-requirement within that window and was not treated as a separate the overall years minimum.
The 'Nice-to-Have Tools' section (Apptio Cloudability, CloudHealth, Kubecost, custom FinOps dashboards) is explicitly labeled as optional and is marked preferred. Note that Apptio Cloudability and CloudHealth also appear in the Core Technology Stack narrative section, which is not a hard-gate section, so they remain preferred.
Datadog and Grafana appear in the Qualifications section under 'monitoring and observability tools including Amazon CloudWatch, Datadog, Grafana, or similar platforms' — they are listed as alternatives to CloudWatch, which is already captured as a required skill. Datadog is emitted as a separate preferred skill (with Grafana as an alternative) since CloudWatch is the AWS-native tool explicitly called out first.
SAST/DAST tools and Pre-commit Hooks appear in the Qualifications section but name no specific product; they were omitted per the rule against emitting non-specific tool categories.
No compensation figures are provided in the posting.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.