| 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 - 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. - 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. - 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. 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. 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 :) |