3 ms·
there's a sort of bifurcation of SRE responsibilities with one branch focusing on software-enabled automation and the other on "systems engineering" aka sysadmi
by dilyevsky 3y ago
there's a sort of bifurcation of SRE responsibilities with one branch focusing on software-enabled automation and the other on "systems engineering" aka sysadmin. Both are called SREs at Google which seems to cause widespread confusion externally (and even within Google). Also see so called "Ben Treynor Curve"[0]
[0] - https://www.usenix.org/system/files/login/articles/login_june_07_jones.pdf https://www.usenix.org/system/files/login/articles/login_jun...
- lrem 3y agoWithin Google: Treynor’s curve is a hiring concept. Once in, you’re doing literally the same job. Being in a team doing greenfield development it took me three years to notice that my TL, with whom we’ve been defining the mathematical model, designing and implementing the system, is on the SysEng ladder.
- dilyevsky 3y ago> Once in, you’re doing literally the same job ok, but you don't tho (i'm sure there are exceptions). if you do, you will have issues with promo (ask me how i know) so if you don't care about that then sure. also if you're se, you had to interview to transfer out of sre to a pure swe role. i personally didn't have this particular problem but saw a few folks that did.