Many of us are engineers, have an engineering/technical background, or work with engineers regularly. A common attribute we have all seen is the fixation on optimizing a single number/metric. At Indeed, we set Time > Cost as a priority, so we are moving away from dollar-based budgeting to incentivize velocity. This has turned out to be incredibly useful in shifting the conversation away from the price of cloud resources (a huge variable) to the number of resources needed. Sounds easy in practice, but there are some items you need to consider and be aware of before you start.
I have always had a passion for technology and innovation. I love solving problems, and I'm currently building out a FinOps based Cloud Economics team for the world's largest job site, Indeed.com.
