<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Vicki Garret</title>
    <description>The latest articles on DEV Community by Vicki Garret (@vicki_garret_).</description>
    <link>https://dev.to/vicki_garret_</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4184489%2F959c1a91-afdb-4d64-a28d-f52525686856.png</url>
      <title>DEV Community: Vicki Garret</title>
      <link>https://dev.to/vicki_garret_</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/vicki_garret_"/>
    <language>en</language>
    <item>
      <title>Work in FinOps, Where Engineering Meets the Cloud Bill💸</title>
      <dc:creator>Vicki Garret</dc:creator>
      <pubDate>Wed, 14 Oct 2026 12:22:36 +0000</pubDate>
      <link>https://dev.to/vicki_garret_/work-in-finops-where-engineering-meets-the-cloud-bill-5agc</link>
      <guid>https://dev.to/vicki_garret_/work-in-finops-where-engineering-meets-the-cloud-bill-5agc</guid>
      <description>&lt;p&gt;Hey everyone! &lt;/p&gt;

&lt;p&gt;I'm a FinOps Engineer working in Big Tech, with 5 years of experience in the field.&lt;/p&gt;

&lt;p&gt;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. 😅&lt;/p&gt;

&lt;p&gt;I'm particularly interested in four things:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Cloud cost optimization:&lt;/strong&gt; getting more value out of the infrastructure we already have.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;FinOps automation:&lt;/strong&gt; because if a human has to repeat the same task every month, there's probably an opportunity to automate it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Data and cost allocation:&lt;/strong&gt; making cloud spending visible, understandable, and attributable to the teams and services behind it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Working with engineering teams:&lt;/strong&gt; turning cost awareness into better technical decisions.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What do I believe about FinOps?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I don't think FinOps is about cutting costs at all costs.&lt;/p&gt;

&lt;p&gt;It's about understanding what we're paying for, why we're paying for it, and whether we're getting the value we expected.&lt;/p&gt;

&lt;p&gt;Sometimes the answer is optimization. Sometimes it's better visibility. Sometimes it's helping a team understand the trade-offs behind an architectural decision.&lt;/p&gt;

&lt;p&gt;And sometimes, the best optimization is realizing that the expensive thing is actually worth it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why am I here?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I want to learn from people who are solving similar problems in different environments.&lt;/p&gt;

&lt;p&gt;And remember: the goal isn't to make the cloud cheap.&lt;/p&gt;

&lt;p&gt;It's to make the cloud worth what it costs. 🚀&lt;/p&gt;

&lt;h1&gt;
  
  
  FinOps #CloudComputing #DevOps #CloudCostOptimization
&lt;/h1&gt;

</description>
      <category>automation</category>
      <category>cloud</category>
      <category>devops</category>
      <category>infrastructure</category>
    </item>
  </channel>
</rss>
