The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations https://g.co/kgs/1cffqN
The DevOps 2.0 Toolkit https://g.co/kgs/ULqmRc
DevOps: A Software Architect's Perspective https://g.co/kgs/trJVDi
Effective DevOps: Building a Culture of Collaboration, Affinity, and Tooling at Scale https://g.co/kgs/LTMEay
In my experience, devops interviews are mostly concerned with your ability to write scripts against APIs and operate puppet or similar tools.
SRE interviews usually assume you will be working with home grown configuration management, they test programming and a lot more Linux and Unix basics.
Just my observation from interviewing for both titles.
* Seeking SRE
* Database Reliability Engineering: Designing and Operating Resilient Database Systems
* The Essential Deming: Leadership Principles from the Father of Quality
* Infrastructure as Code: Managing Servers in the Cloud
* Cloud Native Infrastructure
* the Scuba Paper from Facebook Research
* Kubernetes in Action
* Zen and the Art of Motorcycle Maintenance
* Advanced Programming in the Unix Environment
* Cloud Native: Designing Change-tolerant Software
* Understanding The Linux Memory Manager <-- kind of old (ie references the coming 64bit memory transitions), but super good
* Spring Microservices in Action <--- read even if you're not a Java or Spring head, asks questions like, "maybe you should think about service discovery, routing, tracing, etc"
The Practice of Cloud System Administration: Designing and Operating Large Distributed Systems, Volume 2 -- by the above plus Strata Chalup.
You need both.
Principles of Chaos Engineering
Take a look at the DevOps job postings of lately, tell me that what employers wants you to do is not exactly the same as you did 10 years ago as a sysadmin..
At least at my company, with two exceptions, if you want to be part of the DevOps team you need to pass a developer interview first.
I think any collection of Dilbert comics is an appropriate guide.
Modern devops == configuration management, CI tools, and expectation that you at least take an interest in containerisation.
(I tend to feel that, at least until you get to quite a large scale, there’s still a fair amount of value in “developers who aren’t scared to poke production servers when needed”, but it doesn’t really seem accepted to use the word “devops” to describe that kind of setup.)