As a junior SRE that got hired in this role as a new grad, I find these resources quite handy for anyone that would like to step into SRE. I would like to add three other ideas<p>- Reading the SRE book from Google to get a glimpse of the SRE philosophy. A lot of companies rebrand their Sysadmin or DevOps roles as SRE because it's trendy. Many businesses do not need SRE and need to make sure they understand the idea behind it before doing so.<p>- Learning Golang for such a role is becoming increasingly vital. So many SRE tools including Kubernetes, Prometheus, and Terraform are written, and extended, in Go that it's almost a requirement next to learning Bash.<p>- A lot may disagree on this one, but get yourself some certifications. SRE is kind of a broad role and companies do not know how to assess the skills of candidates, and unfortunately they often rely on certifications to do so. You don't have to enroll in the most challenging ones as a junior, but just one or two basic certifications to get a rough idea of a provider or service capabilities. Choose wisely.<p>It can be difficult to show off any personal project in such a field, but you could try to create your own infrastructure as a side project, self-host some services and provision them with Ansible for example.<p>But most importantly as a new SRE, find yourself a good team and good mentors within that team. Getting into SRE without any previous experience is a hell of a ride, but a very rewarding one. Like previously said, SRE roles are jack of all trades and the field is so broad you never stop learning :)
As a non-developer whose code would probably make your average SRE's brain implode, how competent would this 'course' make me?<p>I started my IT career 2 years ago and my programming isn't that strong. I got pinged for a SRE job recently (my background so far is very much Linux based so I must have matched some filter) but I'm not strong in development, k8s (or even containers), or all of the other cool stuff I see on HN. I know I can lab stuff out, but that's not anywhere close to doing it live.<p>I don't want to be a SRE for Google, but I'd like to learn some more on the reliability side of my world and bring things like Git, Puppet, System design, etc and not be left behind in this wave that's approaching. My organization isn't too involved in the cloud, so a lot of upcoming tech seems out of reach.
I'm going to have to check this out. My knowledge concerning some of the topics is relatively ragged, and this could go far in strengthening that base.
Noticed in the NoSQL section that they still call Cassandra as wide column DB. It’s not true for a long time - CQL requires schema definition, and although it’s possible to emulate old behavior, it’s not wide column anymore - people just copy old things...
a quick search for LinkedIn SRE jobs returns:<p><pre><code> - Senior SREs
- Staff SREs
- Manager, SRE
- SRE Intern
</code></pre>
assuming senior, staff and manager roles would not accept non-traditional candidates...so this applies to interns?
with cloud being the talk of the industry these days. how pervasive are SRE roles. I would wager a good system admin | SRE can save a company thousands if they provisioned their own hardware i.e colo instead of cloud instances etc
I'm not sure, but maybe this is only for internal transfers? I mean this is obviously less difficult than the interviews of the big ones, or maybe Linkedin doesn't have difficult interviews?
looks pretty good but still missing a lot of other things such as CI/CD, Software Testing, Bug management, Feature Development, Code Review as per Styleguide etc that should be taught to any newbie SWE based on the team/company workflow
Title nitpick but this curriculum is for not just for non traditional hires—<p>> At Linkedin, we are using this curriculum for onboarding our non-traditional hires and new college grads into the SRE role.