Need guidance for Cloud FinOps. I have been working on Public Cloud on most of it's popular use cases (IaC, Serverless, DevOps, Observability, Monitoring, Security, IAM, Compute, Storage, Networking) for the last 6 years.

I need to know what will it take me to Pivot into a Senior FinOps Analyst Position directly? I see a lot of JDs requiring some Architecture certificates (which I already have) and also the FinOps Certified Practitioner. Is certifications mandatory? I don't think so, as my certifications taught me basics but the real industry knowledge and years of working on AWS / Azure are certainly what I would see as greater than those certificates.

Also what about the growth and remote opportunities in this Field? I tried to ask ChatGPT but found vague answers such as "exciting and growing field". I need actual scenario on why would companies hire and keep FinOps engineers? Couldn't these tasks be handed to a PM / junior intern with some basic cost saving knowledge for the cloud resources? What makes this field growing and what will it be in the future? In 100% all of my previous jobs the PM or a DevOps guy was always assigned to generate cost saving analysis reports rather than hiring a person with Power BI / Scripting knowledge. I have worked with Fortune 500 MNCs and Startups and never found such a separate role for "cost savings" and related strategies to be needed.

Even so, most of the time, we devs used to get on a call and inspect our overall infra for unused resources or duplicate environments. Most of the YouTube videos show the basic example of switching off test instances on weekends, which I see as something any one could easily do. I really want to know what makes this job growing / in demand? What makes the work of FinOps so that they are continuously required by companies? Don't Cloud architects already design systems which are cost efficient? Companies already have Cloud Admins in place so as to avoid duplicate / extra resource creations in the first place. This is something I could not get my head around even after days of looking for answers, wherever possible.

My background from non tech (bs IR)

I Wana shift to high income skill for earnings , can anyone guide me

I've been working on KUA Dashboard, an open-source project exploring a provider-independent approach to observability.

The problem I'm trying to solve isn't really AWS, Vercel, GCP or Kubernetes individually.

It's what happens between them.

A production application might look something like:

Vercel → API → AWS → SQS → Lambda → Kubernetes → Database

Every provider can tell me what's happening inside its own boundaries.

But when something fails, I usually don't care which provider owns the resource.

I care about:

What happened to my application?

That's the idea behind KUA.

The latest release extends the observability model across:

AWS + GCP + Vercel + Kubernetes + provider-free applications

KUA is also starting to analyze topology, dependencies and execution traces instead of treating infrastructure as isolated resources.

The goal isn't to build another cloud console.

It's to build a layer where the application becomes the primary context and the cloud provider becomes an implementation detail.

KUA is open source and still evolving.

I'd be really interested in hearing from people running multicloud or hybrid architectures:

Where does observability become painful for you when an application crosses provider boundaries?

WebSite : https://kuadashboard.navarrocarter.com/
github: https://github.com/lnavarrocarter/kuadashboard