<story><title>SRE Teams: Hash</title><url>https://sreteams.substack.com/p/hash</url></story><parent_chain></parent_chain><comment><author>pram</author><text>I worked at a major software company that was implementing an “SRE” org and it was frankly pathetic. It basically had its genesis in some higher up hearing that Google does this thing, so we probably should too. That then later turned into a bunch of random DevOps&amp;#x2F;Sys Admins drafted into the new org reading the Google SRE book. It was a shamelessly cargo cult approach.&lt;p&gt;After a year all we really had was hundreds of Confluence pages specifying policy for this and that, a bunch of ceremony added around releases, and arbitrary SLA&amp;#x2F;SLOs defined. Almost zero actual technical work was accomplished. They then started filling the team with new grads who had neither devops or sysadmin experience, kind of cementing the perception that it was a non-technical role.&lt;p&gt;Either way I’m not a fan of the entire concept after being subjected to that suffering!</text></comment>
<story><title>SRE Teams: Hash</title><url>https://sreteams.substack.com/p/hash</url></story><parent_chain></parent_chain><comment><author>namanaggarwal</author><text>What I have seen in the companies that I have worked in&lt;p&gt;- Initially every engineer does everything&lt;p&gt;- Growth gives birth to independent
SRE teams. Now we have engineers who does only SRE&lt;p&gt;- We realised SRE is bottle neck for product teams. SRE teams are removed and all SRE are embedded into the product teams to do dedicated work for them.&lt;p&gt;- Other team members are now required to learn SRE stuff, especially now that terraform etc are there so we are back to everyone is a SRE&lt;p&gt;note that FAANG level companies go back to independent infra, SRE etc maybe because of niche and custom softwares they have.</text></comment>