Software Engineer, FinOps Engineering (East Coast)

The opportunity 

To achieve our ambitious goals, we’re looking for a Software Engineer to join our FinOps team as part of the wider Engineering Platform team. The person in this role will work directly with the biggest Grammarly vendors, identify and visualize cost drivers, discover cost optimization options, and forecast and analyze our cloud spending. They will drive our financial accountability culture and enable our Product, Engineering, IT, Finance, and Executive teams to scale Grammarly while making data-driven spending decisions.

Grammarly’s engineers and researchers have the freedom to innovate and uncover breakthroughs—and, in turn, influence our product roadmap. The complexity of our technical challenges is growing rapidly as we scale our interfaces, algorithms, and infrastructure. You can hear more from our team on our technical blog.

Your impact

As a FinOps Engineer, you will be at the forefront of building and optimizing a framework that empowers our engineering teams to manage cloud costs effectively and provides stakeholders with the information to make value-driven decisions. You will create an abstraction over complex, flexible, and user-friendly infrastructure, balancing cost-efficiency with performance and security while making numerous critical decisions.

Your work will be instrumental in establishing a center of excellence for cost awareness, establishing and evangelizing best practices, and developing tools to scale these practices across all engineering teams.

In this role, you will:

• Be an ambassador for FinOps – building and continually improving cost tooling and processes.
• Fostering FinOps program and cost awareness: evolve tooling and processes to run the FinOps program, fostering cost awareness across Grammarly.
• Create and drive cost saving backlog: Collaborate with developers to create a backlog of cost-saving initiatives and implement them effectively.
• Implement cost monitoring and awareness tools: Deploy cost monitoring tools and practices organization-wide to increase awareness of cloud spending.
• Provide guidance to engineering teams to have a cost-effective application/service by identifying anomalies and best practices.
• Collaborate closely with executives to present financial reports, provide clear summaries, and address questions, ensuring insightful decision-making in a high-visibility role.
• Implement cost forecasting improvements to reduce manual intervention for cost optimization workflows.
• Implementing policy as code for cost optimization guardrails for prevention and auto-remediation.

Qualifications

• Is experienced in building out FinOps tooling for cost anomaly detection, prevention and auto-remediation.
• Has a minimum of 7 years of experience operating across live production SaaS environments with high load.
• Experience in FinOps Framework: familiarity with FinOps principles and frameworks.
• Hands-on experience with cloud-native infrastructure solutions and container orchestration platforms.
• Background in software development or engineering roles with a focus on infrastructure and cost optimization.
• Is knowledgeable on all things FinOps and how to scale those solutions across the engineering organization.
• Is experienced in performance tuning and auto-scaling applications and infrastructure.
• Is knowledgeable of AWS —or has deep expertise in Azure or GCP and is willing to learn AWS quickly.
• Can deliver maintainable and high-quality code in Go or other languages.
• Strong communication and presentation skills with an ability to articulate technical matters to a broad audience and executive leadership.
• Embodies our EAGER values—is ethical, adaptable, gritty, empathetic, and remarkable.
• Is inspired by our MOVE principles, which are the blueprint for how things get done at Grammarly: move fast and learn faster, obsess about creating customer value, value impact over activity, and embrace healthy disagreement rooted in trust.
• Is able to meet in person for their team’s scheduled collaboration weeks, traveling if necessary to the hub where their team is based.