> I think this is the point where we're getting too serious about the discipline.
In my opinion, we are not serious enough. The role of the cited sysadmin is dying or dead in the modern company.
As an SRE, you are expected to directly contribute to the product to improve SLOs as well as several other dimensions you quoted (like user happiness).
I've personally performed code refactoring to reduce build job duration slowing down pipelines for _everybody_ in a component I was unfamiliar with. The code review was then performed by a code owner and the PR merged.
> The contracts define what kind of guarantees you have to give and on what timeline.
That's why you commit to ship product increments, not hard deadlines. See the failed launch of healthcare.gov, for example.
> How is SRE supposed to quantify if the users are happy?
The same way a dev would: review with stakeholders, "show-and-tell" where you collect feedback and improve your domain knowledge by focusing on the customer problem instead of your own vision of the solution.
> Or tell the devs how to design their apps to fail less often?
This is precisely why SREs would provide value by direct contribution.
> you literally end up an executive director of product.
We are all ambassadors of the product and can contribute past our designated "boundaries". That's what cross-functional is all about. No, you cannot make business decisions but if it is code, you have very high leverage.
> If we really want to make products that users are happy with, we need to teach executives how to achieve it, not SREs.
This has not happened yet and I suspect it never will.
> SREs shouldn't be driving the bus from the back row [..] Let's teach executives how to set everyone up to succeed [..].
Agreed. Do you have a concrete proposal? Without fundamental organizational change, this is impossible. Conway's law still applies, so does its inverse. Meaning you can break down silos (including at executive level) by migrating from component to cross-functional feature teams.