SRE isn't a technical role. I mean, unfortunately we Ops folk are commonly given way too many responsibilities, so it's common to be technical. But if you read

SRE isn't a technical role. I mean, unfortunately we Ops folk are commonly given way too many responsibilities, so it's common to be technical. But if you read the SRE books, it's actually describing business management processes, product ownership, project management, NOC, monitoring, incident management, etc. Nowhere does it say "to be a good SRE you need to know how to use tcpdump". In addition, Operations is much more of a traditional trade than a technical skillset. You can't read a book about being an electrician and then expect to do a good job wiring up a 100 amp panel and not killing somebody. You have to be an apprentice first, then after a few years a journeyman, and after a decade or more a master. Until you work under someone and have years of experience, you're not going to be very good. This LinkedIn curriculum is just one example of many companies that misunderstand and underappreciate the true nature and purpose of the role, and make a sad attempt to cut corners by hoping they can turn a total newbie into a journeyman by learning some Linux commands. Doesn't work that way. (But thanks, LinkedIn, for telling me that I don't want to work there)