FinOps Engineer

This role is for one of the Weekday's clients

Salary range: Rs - Rs (ie INR 10-15 LPA)

Experience: 3+ yrs

Location: Pune

Job Type: full-time

We are seeking a highly motivated FinOps Engineer with a strong DevOps and Cloud Engineering background to drive cloud cost optimization and financial accountability across a large-scale technology environment. This role is ideal for professionals who are passionate about identifying inefficiencies, eliminating cloud waste, and building a culture of cost-conscious engineering.

As a FinOps Engineer, you will work closely with Engineering, SRE, Product, and Finance teams to improve cloud resource utilization, optimize infrastructure spending, and implement cost governance strategies. You will play a critical role in ensuring that cloud investments align with business objectives while maintaining performance, scalability, and operational excellence across multi-cloud environments.

Requirements

\n
• Continuously monitor and optimize cloud infrastructure costs across AWS, Azure, and GCP environments.
\n
• Identify idle, underutilized, or oversized resources and implement cost-saving recommendations.
\n
• Conduct regular cloud cost audits covering compute, storage, networking, databases, observability platforms, and third-party services.
\n
• Develop and maintain cloud cost visibility dashboards, reports, and forecasting models.
\n
• Lead cost optimization initiatives including rightsizing, autoscaling improvements, storage lifecycle management, and utilization reviews.
\n
• Implement and manage Reserved Instances, Savings Plans, Spot Instances, and other cloud pricing optimization strategies.
\n
• Build chargeback and showback models to improve spending transparency across teams.
\n
• Integrate cost governance controls into Infrastructure as Code (Terraform, CloudFormation), CI/CD pipelines, and deployment workflows.
\n
• Optimize Kubernetes environments through resource tuning, node optimization, autoscaling strategies, and cost management tools.
\n
• Establish automated monitoring, anomaly detection, and alerting mechanisms for budget overruns and unexpected cloud spend.
\n
• Collaborate with Finance teams on budgeting, forecasting, cloud spend analysis, and unit economics reporting.
\n
• Drive cloud cost awareness through documentation, workshops, best practices, and engineering enablement initiatives.
\n
• Partner with technical teams to balance performance, reliability, scalability, and cost efficiency.
\n
• Provide actionable insights and recommendations to leadership through periodic cost review meetings.
\n

\n
• 3+ years of experience in FinOps, DevOps, Cloud Engineering, Site Reliability Engineering (SRE), or related roles.
\n
• Strong expertise in cloud cost optimization and financial governance within AWS environments.
\n
• Hands-on experience with cloud billing analysis, cost reporting, and native cloud cost management tools.
\n
• Solid understanding of Infrastructure as Code technologies such as Terraform, CloudFormation, or similar platforms.
\n
• Experience working with Kubernetes, Docker, and containerized workloads in cloud environments.
\n
• Proficiency in scripting and automation using Python, Bash, or Go.
\n
• Knowledge of cloud pricing models including On-Demand, Reserved Instances, Savings Plans, and Spot Instances.
\n
• Experience integrating cost controls into CI/CD pipelines and deployment processes.
\n
• Strong analytical and problem-solving skills with a data-driven mindset.
\n
• Ability to communicate technical and financial insights effectively to both engineering and business stakeholders.
\n
• Familiarity with FinOps platforms such as Apptio, CloudHealth, Cloudability, Spot.io, Kubecost, or similar tools is an advantage.
\n
• Experience working in multi-cloud environments and understanding cloud financial management best practices.
\n
• FinOps certification and cloud platform certifications are desirable.
\n
• Self-driven, proactive, and highly detail-oriented with a strong focus on continuous improvement and operational efficiency.
\n