Being a "good" developer, engineer, architect, or product manager who builds great products isn't enough anymore.
There was a time when technical experts were largely left alone. As long as their products worked, kept working, and stayed within budget, few questions were asked.
The cloud has unlocked incredible opportunities for engineers, but it has also opened the door to a new line of scrutiny. Instead of "Can we build it?" engineers and product leaders must now answer questions like:
- "Should we build it?"
- "Is this the most cost-efficient way to build it?"
- "Why did we build it this way in the first place?"
- "What other ways could we build it?"
- "What if we built it someplace else?"
- "What will happen when we add more users, customers, or data?"
This leaves many engineering leaders wondering, "Can't I just do my job?"
Welcome to the new era of engineering — this is your job.
On the surface, these questions seem like more work. But they also give engineering leaders the opportunity to own the cloud cost narrative and draw a direct line between their work and the bottom line of the business.
Being a Good Steward of Cloud Spend
Typical interactions between finance and engineering are reactions to unexpected costs, and are therefore contentious and defensive.
"My number one goal when working with my CFO is to have no surprises," says a VP of Engineering from a SaaS company whose cloud spend represents almost 20% of their P&L.
This matters because surprises and uncertainty with your finance leaders trigger an immediate need to reestablish balance — questions, meetings, and in the worst cases, cuts.
Many engineers push back at this point with, "Finance just doesn't understand." And they're probably right.
Truthfully, finance does not want to understand microservices or containers or the details of any individual technical decision. What they want is confidence that you are thinking about the financial impact of those decisions before they have to ask why costs went up. They want to know you are being a good steward of the business.
When you are, the cloud cost narrative becomes yours to own and explain — rather than a story in which you appear to play the villain.
How Engineers Can Become the Hero of the Cloud Cost Story
Think about how you measure the success of your cloud projects today. Uptime? Milestones? Completion?
Controlling the cloud cost narrative begins with talking about cloud spending in terms of business outcomes — not just for past spending, but for future planning as well.
For example, spending on VM instance-hours for development may be viewed as wasteful if the justification is something vague like "we need to develop and deploy quickly." Framed differently — "we're increasing engineering efficiency and lowering time to market by building on these VMs in separate pipelines" — that same spending reads as cost avoidance that aligns with revenue goals.
Once the outcomes that matter are understood, engineers must take action and accountability. This most often happens by removing barriers between finance and engineering through:
- Actively participating in cost allocation discussions
- Leading usage and cost data analysis and normalization
- Identifying and reconciling anomalies and areas of underutilization
- Monitoring, reporting, and continuously improving resource utilization and workload efficiency
These actions dissolve barriers because approaching cost with a shared mindset creates a common language — one that gets finance and engineering in the same room solving the same problems.
Consider a team deciding whether to spin up a new instance or size up an existing one. Traditionally, engineers ask whether the instance meets current and near-term usage needs. Bringing a cost lens to that same decision expands the considerations: What is the price difference of stepping up a half or full tier? How likely is an upgrade in the next 6, 12, or 18 months, and what would that cost?
By looking at usage and cost side-by-side, you position yourself as an ally to your finance counterpart — a driver in conversations about budget, total cost of ownership, and forecasted spend. You reduce risk by answering the what-if questions finance loves to ask. And you've positioned yourself to build in both the most technically and financially efficient way.
A word of caution: these practices matter even before you've settled on the perfect metric for measuring their impact. Metrics will evolve as you learn. But by approaching your work with a cost mindset from the start, you'll be positioned to tell the engineering impact story as your understanding matures.
Efficiency Is Now Part of the Job
There is no question that owning the cloud cost narrative requires effort. But it is effort that is no longer optional. Companies are adopting Cloud FinOps practices to invest more strategically in the cloud in ways that drive measurable business value. As a result, cloud cost efficiency is not a finance problem or an engineering problem — it's a business operations problem.
If engineering and product teams don't want to feel like victims of this shift, they need to embrace the opportunity to become champions of their cloud cost narrative and its role in building a great business.