In a recent episode of the FinOps on Azure podcast hosted by Michael Stephenson, we got a rare behind-the-scenes look at one of the most influential voices shaping the FinOps conversation globally: Victor Garcia.
Victor isn’t just pushing out a weekly newsletter. He’s quietly building an ecosystem a grassroots movement of practitioners, engineers, architects, and even a few finance folks bound by a simple but powerful mission: make FinOps knowledge more accessible, actionable, and community-driven.
Victor started his career in software engineering, working across languages like Python, Java, and TypeScript, eventually growing into DevOps and cloud-native technologies like Kubernetes, Terraform, and CI/CD systems. This hands-on experience across the cloud lifecycle gave him a real-world view of where FinOps could have the most impact—not just in theory, but in engineering workflows.
This background gives FinOps Weekly a different flavor. The content doesn’t feel abstract. It’s rooted in the real decisions practitioners face: tagging strategies that work, GitHub tools that solve real problems, cost visibility within CI/CD pipelines, and optimizing Kubernetes workloads for cost without disrupting delivery.
What started as a simple curation project has grown into a go-to resource for engineers, cloud architects, and increasingly, even finance teams. FinOps Weekly now includes:
It’s not built around a tool, a company, or a certification. It’s built around content that actually helps people get better at managing cloud costs. That’s why it’s gained so much trust and why the community keeps growing.
FinOps Weekly has never been about building a personal brand or monetizing an audience. The focus has been consistent: make FinOps knowledge easy to access, consume, and apply no matter your background.
This approach has attracted contributors from all over the world, from technical engineers to FinOps specialists to vendor-neutral experts. The newsletter and Slack community (now 500+ strong) have become safe spaces for honest discussion especially on hot topics like AI-related cost consumption, tagging disputes, or cross-cloud optimization challenges.
There’s also a strong Azure presence in the content reflecting the fact that some of the most detailed FinOps work being done today is happening inside Microsoft environments, particularly among architects managing complex hybrid scenarios or enterprise contracts.
Victor’s vision extends far beyond a newsletter. Several exciting developments are in motion:
These efforts are all aimed at one thing: making FinOps understandable and approachable to anyone who needs it whether they come from a DevOps team, a finance department, or a leadership role trying to control cloud spend.
There’s no fancy branding behind FinOps Weekly. No webinars full of sales pitches. No locked-down content behind paywalls.
It works because it speaks to the practitioner’s mindset. It doesn’t care about titles it cares about usefulness. If a DevOps engineer shares a working Terraform script that saves time and money, it gets highlighted. If someone from finance explains a new reporting model that simplifies allocations, that gets shared too.
It’s a space where value is judged on clarity and impact, not seniority or marketing.
If you’re part of the FinOps world or even just touching cloud cost in your role there are several ways to contribute and learn:
You don’t need to be an expert. If you care about improving cloud cost visibility, engineering efficiency, or cross-team collaboration—this is the place for you.
There’s a lot of energy in the FinOps space right now. New tools, frameworks, certifications, and vendor solutions are launching all the time. But amidst all that noise, voices like Victor Garcia’s stand out not because they’re the loudest, but because they’re the most grounded.
FinOps Weekly is a reminder that some of the most impactful work in tech happens quietly. In newsletters. In Slack threads. In open-source repos. In conversations that aren’t about selling, but about solving.
If more of the FinOps world leaned into that spirit of open collaboration and shared learning, we’d all be better for it.