<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Hans Chung on Medium]]></title>
        <description><![CDATA[Stories by Hans Chung on Medium]]></description>
        <link>https://medium.com/@jabcrosshook?source=rss-958640bf3d71------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*2Laande6rd4UfFQ5.jpeg</url>
            <title>Stories by Hans Chung on Medium</title>
            <link>https://medium.com/@jabcrosshook?source=rss-958640bf3d71------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:45:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jabcrosshook/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Witnessing SRE at Alphabet]]></title>
            <link>https://medium.com/@jabcrosshook/witnessing-sre-at-alphabet-2ff82197c5a1?source=rss-958640bf3d71------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ff82197c5a1</guid>
            <category><![CDATA[site-reliability-engineer]]></category>
            <dc:creator><![CDATA[Hans Chung]]></dc:creator>
            <pubDate>Mon, 31 Jul 2023 20:28:53 GMT</pubDate>
            <atom:updated>2023-07-31T20:28:53.458Z</atom:updated>
            <content:encoded><![CDATA[<p>From mid 2020 to 2023, I was a product manager for Alphabet’s home-grown SRE incident response and management tool (IRM). JJ at Rootly suggested that folks would benefit from hearing my point of view and war stories. He wanted to know how I went about influencing SRE policy in a multi-headed monster like Alphabet. In my blog I will cover what I observed as a fly on the wall during incidents and retrospectives as well as what I distilled as a product manager for this domain. I refer to my responsibility as a domain and not just a product because a large part of SRE is people, training, policies and frameworks.</p><p>Even though Alphabet was where the book on SRE was written, SRE at Alphabet varied wildly, from a few playbook-free SWEs supporting a service to highly-trained, multi-rotation SRE teams for the back-end of an application. Beyond SRE maturity, the other dimension of variety was B2C vs B2B. As a product manager I had to understand and balance the needs and drivers of something like YouTube vs Google Compute Engine vs a small recently acquired product.</p><p>SREs tend to be opinionated and I’ve heard “You are wrong” a few times at the end of my presentations. After a few minutes of usual SRE rant, the conversation ends up as an insightful discussion that refines my view. So I welcome your rants and corrections.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ff82197c5a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>