Hey everyone!
I'm a FinOps Engineer working in Big Tech, with 5 years of experience in the field.
My job sits somewhere between cloud infrastructure, data, automation, and engineering teams. In other words, I spend my time thinking about cloud costs-so hopefully, fewer people have to panic when the bill arrives. 😅
I'm particularly interested in four things:
Cloud cost optimization: getting more value out of the infrastructure we already have.
FinOps automation: because if a human has to repeat the same task every month, there's probably an opportunity to automate it.
Data and cost allocation: making cloud spending visible, understandable, and attributable to the teams and services behind it.
Working with engineering teams: turning cost awareness into better technical decisions.
I work in a multi-cloud environment, which keeps things interesting. Different platforms, different billing models, different quirks and plenty of opportunities to learn that the phrase "it's just a small change" can have a surprisingly interesting financial interpretation.
What do I believe about FinOps?
I don't think FinOps is about cutting costs at all costs.
It's about understanding what we're paying for, why we're paying for it, and whether we're getting the value we expected.
Sometimes the answer is optimization. Sometimes it's better visibility. Sometimes it's helping a team understand the trade-offs behind an architectural decision.
And sometimes, the best optimization is realizing that the expensive thing is actually worth it.
Why am I here?
I want to learn from people who are solving similar problems in different environments.
And remember: the goal isn't to make the cloud cheap.
It's to make the cloud worth what it costs. 🚀
Top comments (0)