I have worked at several places where SRE meant different things:
- A virtual, first responder team on call rotation for all the services because developers didn't want to be on call for their own stuff.
- Another name for a platform engineering / DevOps team.
- A team who built nothing, maintained nothing and were not paged for anything. They just collected metrics, built dashboards and spread the gospel of SRE with a big focus on form over function. IME they were annoying to work with, frequently missed the point specially when it came to stateful workloads and were ultimately just an incident factory.
I was going to say the same. In my experience I can say without hesitation green field projects is how you advance your career, become visible and get promoted.
You say this because you are on HN, very senior and/or living in a bubble.
In the vast majority of programming jobs out there you are not paid to solve problems: you are told very clearly what to do, how to do it and what technology you have to use for the job.
People don't hire analysts they hire "Java programmers".
Or, you could have been suddenly cheated on and exposed, or divorced and recently entered the dating market, or thinking about opening up your relationship after decades of monogamy.
- A virtual, first responder team on call rotation for all the services because developers didn't want to be on call for their own stuff.
- Another name for a platform engineering / DevOps team.
- A team who built nothing, maintained nothing and were not paged for anything. They just collected metrics, built dashboards and spread the gospel of SRE with a big focus on form over function. IME they were annoying to work with, frequently missed the point specially when it came to stateful workloads and were ultimately just an incident factory.