Two things here. 1. As an SRE, it becomes even more important to get the big picture of all things that make the a company’s systems and services tick. I’ve be

Two things here. 1. As an SRE, it becomes even more important to get the big picture of all things that make the a company’s systems and services tick. I’ve been surprised by the lack of high level block diagrams explaining from this perspective. The diagrams are often from the perspective of devs as they build the nitty gritty details. It can be quite daunting for a new SRE, even more so for a new grad. On the other hand, I usually spend my first month documenting everything I learn in the first month as an SRE, and it becomes the guide that gets passed on to future SREs. 2. The thought of preparing educative materials to onboard a new grad(vs an experienced engineer who is expected to only match their experience to the company specifics) is often missing even in highly organised and functional shops. Nurturing and helping a new grad into the company specific things is a lot more rewarding and advantageous in the long run. There are almost always these pockets of tribal knowledge that exists among the senior folks who were there when some problems were solved. It is counter productive to the team as every time someone touches those sections, they seek the review/approval from those that possess that tribal knowledge.