- Oct 18, 2021
- 3 min read
Updated: Mar 31, 2024
The shift to the cloud created new professions, one of them is the role of FinOps Engineering. Ziva Tubul explains how keeping cloud costs down became an emerging engineering field
The appearance of new technologies always creates new professions, and just as the appearance of cars created the car mechanic, the shift from data centers to cloud storage created cloud experts. One of the lesser known of them is the FinOps Engineer.
Ziva Tubul wasn’t always into FinOps - a domain defined as the intersection of people, processes, and technology, as it relates to managing the financial operations of a business. She started her tech career at Intel where she was an Operations Engineer. Only a few years ago, while working on a big cloud cost reduction project at HP, she became hooked on the new emerging domain.
When Ziva got an offer from Wix earlier this year she didn’t hesitate. “The truth is I interviewed at three companies and was accepted to all of them,” she says with a smile. “So why didn’t I have any doubt which one of them I’d choose? First, because Wix had a great reputation. But then - only after I started my interviewing process here - I realized that it’s also a very powerful player in the Financial Operations (FinOps) Engineering field that I specialize in,” she says.
So what is FinOps and what do you do in your role?
“After companies began hosting all their data on the cloud and not on regular data centers, the old purchasing process of hosting space ceased to exist. While in the past companies purchased space and paid a flat fee for it, these days engineers are in charge of expenses that are now determined by usage. In this reality, FinOps people are the gatekeepers for cloud related expenses and those who bridge the gap between the developers who are in charge of expenses and the budgets that need to be controlled. This shift created a need for people who know how to use the cloud effectively and efficiently when it comes to costs. That’s what I do.”
So how do you do it?
“Basically, we’re a part of the strategic planning of our cloud usage. We analyze our costs and create predictions based on usage and growth rate. We negotiate with service providers over costs and we’re a part of every purchase process related to Wix’s infrastructure needs. We lead a cost optimization agenda and we educate and embed the FinOps culture into the organization so that engineers across Wix will create an efficient and cost effective process from the very beginning of their work.”
What does it take to be a FinOps Engineer?
“Since FinOps is the bridge between engineering and budget management, a FinOps engineer has to understand both the tech and financial realms. They need to have analytical skills, a familiarity with the production environment and a deep understanding of cloud architecture and infrastructure.
"On top of that, because we’re committed to embed the FinOps culture within the organization we work in, one of the most important skills a FinOps Engineer must have is the ability to motivate people and to lead processes.”
What are the main challenges?
“Since we’re at the intersection between finance and technology, we need to be on top of the latest technologies as they're changing very rapidly, and to constantly manage and optimize them. We’re always trying to be proactive: me and my manager - we’re only two in our team - are constantly thinking of ways to get people to address this subject. It means researching different models and checking out alternative services and asking questions like how picking a specific service serves Wix. Thinking in such a manner from the beginning saves us time and costs of fixing things later on.”
What’s your favorite part of the job?
“This domain is built out of a variety of things and it’s very diverse. It’s innovative and groundbreaking and we’re at a time where organizations understand the need for cost effective cloud management, so it’s an exciting place to be in. I love the fact that what I do directly influences Wix’s business and that each day I learn something new and grow. FinOps is a pretty new domain, and Wix is ahead of the curve. I joined 7 months ago but my manager has been doing it at Wix for 5 years. Other organizations are only beginning to understand that there’s a need for such a role.”
The intersection of generative AI and creative workflows is rapidly redefining what we consider “original” work, and your article captures the tension between automation and artistic intent beautifully. What I find most promising is how these tools are moving from novelty to utility—they're no longer just gimmicks but are becoming integrated into professional design pipelines, helping artists iterate faster and explore variations that would otherwise take hours. One platform that exemplifies this shift is built around a simple prompt‑to‑image engine, yet it offers granular control over style, composition, and even mood. I've been experimenting with it for my own projects and documented some of the results at https://aimeigen.com/. It’s a testament to how AI can amplify human creativity rather than…
In an era where data privacy regulations are tightening and developers constantly need realistic test datasets, the challenge of generating valid yet non‑identifiable information is more critical than ever. Your post does an excellent job of framing the trade‑offs between realism and anonymity, especially when dealing with address fields that must pass format validation without exposing real user data. I've been using a lightweight utility that solves exactly this problem—it produces region‑compliant addresses on the fly, supports multiple country formats, and integrates easily into CI pipelines. For anyone working on similar testing or privacy‑preserving scenarios, I highly recommend checking out https://addressgenerator.org/. It’s a small but powerful tool that reflects the kind of pragmatic engineering you’re advocating for here.
Mobile accessibility has become the backbone of user retention, yet many platforms still treat it as an afterthought. Your discussion on seamless login flows and cross-device synchronization resonates deeply with what I've observed in the field—users expect instant, frictionless access without sacrificing security. One implementation that caught my attention recently is the approach taken by a dedicated mobile companion, which prioritizes both speed and data integrity. You can explore their architecture and feature set at https://rocokingdom.app/. They've managed to reduce authentication latency while maintaining robust session management, which aligns perfectly with the principles you outlined about balancing convenience and protection in modern app design.
The way modern gaming platforms are evolving goes far beyond just entertainment—they're becoming complex ecosystems of strategy, community engagement, and real-time data processing. What struck me in this article is how similar the challenges are to building scalable web services, especially when you have to balance player retention with performance optimization. I've been following a project that takes a structured approach to game mechanics and world-building, and they document their design philosophy quite openly at https://rocokingdomworld.org/. It’s interesting to see how they break down character progression and resource management into measurable metrics, much like what you described here. That overlap between game design and systems thinking is what makes this space so compelling to watch.
Reading through the way platforms like Wix are shaping cloud control and FinOps conversations, it’s clear how much emphasis is now on efficiency, governance, and scalable systems in modern tech stacks. In a similar way, Writiva brings attention to structured digital thinking through its content approach, where clarity and usability matter as much as output. That overlap between operational discipline and communication strategy reflects how interconnected tech, finance, and content ecosystems are becoming across platforms like Writiva.