About This Role

BQE Software is hiring a Cloud FinOps Engineer to own cloud cost visibility, anomaly detection, optimization and tooling spend across our AWS estate and the SaaS tools that run our Cloud Engineering function. You will take over a working FinOps practice (not build one from zero), Daily, weekly and monthly AWS cost reports, Reserved Instance and Savings Plan analysis, an automated FinOps analyst pipeline, and cost tracking for observability platforms.

The role sits in Cloud Engineering and reports to the Head of Cloud Engineering. You will partner daily with SRE, Database Engineering, Finance and Engineering leadership, and you will be the single accountable owner for the question "why did our cloud bill move, and what do we do about it".

Key Responsibilities

1. AWS cost visibility and reporting

- Own the weekly FinOps report and the monthly wrap-up to leadership with dollar impact, Savings Plan and RI status, anomalies, and recommended actions with named owners. Maintain month-end forecasts using the settled methodology.
- Design and build the next generation of the system - automated Cost and Usage Report ingestion, daily automated reconciliation to the bill, and self-serve dashboards.

2. Anomaly detection and cost movement analysis

- Investigate every anomaly service, setup systems to detect and alert for anomalies. Drive each confirmed anomaly to a root cause and an owner and follow it to closure with a Jira ticket where remediation is needed.

3. Commitment and rate optimization

- Own Savings Plan and Reserved Instance strategy across all accounts. Monitor utilization daily, with particular attention to weekend over-commitment and unused commitment dollars, and adjust commitment levels with payback period,



expected monthly savings and confidence stated for every change.
- Run right-sizing, instance family modernization, storage tiering, idle resource cleanup and Spot evaluation across EC2, RDS, Aurora, EBS, OpenSearch, Kinesis and DMS.
- Partner with Database Engineering on SQL Server licensing economics: license-included versus BYOL, Standard versus Enterprise placement, passive node billing and weekend downgrade schedules.

4. AI and platform spend governance

- Establish guardrails for AI workloads: AWS Budgets with alerts, service quotas, IAM boundaries and mandatory cost allocation tags. Report AI spend by model, account and workload as a first-class line in the weekly report.
- Track AI tooling usage and spend alongside cloud spend.

6. Observability and SaaS tooling cost

- Build and own the first unified tooling cost view across all SaaS tooling. Own renewal negotiations and right-sizing of tool commitments with vendor account teams, with Finance and Procurement.

7. Stakeholder partnership and FinOps culture

- Present monthly to Engineering leadership and Finance. Translate cloud spend into unit economics that the business understands, such as cost per tenant, per region and per customer database.
- Run a monthly FinOps review with SRE, Database Engineering and Application Engineering owners to agree actions and confirm closure of prior ones.




- Define and enforce tagging standards, account structure and cost allocation rules so show back by team, product and environment is reliable.

Required qualifications and experience

- 2+ years relevant experience: cloud cost management, FinOps, cloud financial analysis or cloud infrastructure engineering with a demonstrable cost focus

Including 1+ year hands-on AWS billing / FinOps experience.

- Deep working knowledge of AWS Cost Explorer, the Cost and Usage Report, AWS Budgets, Cost Anomaly Detection, Savings Plans, Reserved Instances.
- Proven experience managing commitment portfolios: purchasing, tracking utilization and coverage, renewing before expiry, and quantifying the payback of every change.
- Ability to write and maintain analysis code. Python with pandas or openpyxl and boto3. You should be comfortable reading Lambda handlers, YAML rule files and SQL.
- Statistical literacy for anomaly work: baselines, standard deviation and Z-scores, seasonality, weekday versus weekend patterns, and how to separate one-time charges from run-rate.
- Experience producing executive-level reporting: turning a month of billing data into a headline, three drivers and a set of owned actions, in Excel, Word or a dashboard.
- Working knowledge of Windows Server and SQL Server licensing on AWS, or a transparent ability to learn it quickly
- Familiarity with observability platform commercial models, especially New Relic consumption pricing (CCU and data ingest), and with SaaS licensing and renewal negotiation.
- Strong stakeholder skills: you can hold engineers accountable for spend, work with Finance on accruals and forecasts, and push back on a vendor with data

📌 Cloud FinOps Engineer (Srinagar)
🏢 BQE Software
📍 Srinagar