[m3drano]

I've been running as SRE for the last decade, running critical stuff like authentication (which mostly all services depend on). I'm a software engineer.

I cannot disagree more: our team is healthy, oncall is quite a fine activity to do (and compensated, of course), we have plenty of engineering work to do.

I've had five promotions (and tripled salary) and done so working on plenty rewarding activities over time. I've done from deployment automation, to capacity planning, distributed system design, large data migrations, designing ietf standards for auth protocols, wrote client sdks, now we even do AI for different things (including model development).

I'd recommend to not generalize from "I didn't like it / the experience wasn't a match for me" to "the role is shitty".

[rr808]

I work in financials, so not tech

> oncall is quite a fine activity to do (and compensated, of course),

Overnight on call is never compensated. I know some tech companies pay but I've never seen it.

> deployment automation, to capacity planning, distributed system design, large data migrations, designing ietf standards for auth protocols, wrote client sdks, now we even do AI for different things (including model development).

To me that is mostly SWE work (capacity planning and migrations perhaps is SRE). in regulated environments SREs are explicitly forbidden from making changes to the code base.

> I'd recommend to not generalize from "I didn't like it / the experience wasn't a match for me" to "the role is shitty".

Agreed.

[pas]

where? also Google? can you elaborate on what makes it a "smooth sailing" compared to what you have seen/heard? thanks!