This book will at best get you an L5 gig at FAANG; for Staff eng positions (L6+) you need significantly more depth and rigor.
Becoming the best in one field is almost impossible: there is always someone more studied than you. However, becoming "competent" in two or three different fields can lead to a strong advantage.
Yes, you should reach for depth in your field. But you should also reach for breadth when its easy. There are sometimes easy ways to differentiate yourself over your peers.
----------
I feel like there needs to be a good collection of books that teach the "simplest tricks" of a field.
Ex: Cryptography Engineering is the "simplest" explanation of cryptography. There's not enough math to understand any crypto-algorithm, but by just laying out the names of common algorithms + their common uses, the book teaches the "easiest" bits of crypto to those outside of the field.
Maybe that's the niche for this book? I haven't read it, but if its written clearly enough, it can be used for someone like me to explore a field I don't work in on a day-to-day basis.
--------
Breadth of study vs depth of study are two different styles of study. They're not necessarily more or less important... they're just two different ways of creating your own niche in your organization.
For sockets / pipes / terminal stuff in Unix, I ultimately just had to skim over "Advanced Programming in the UNIX Environment" cover-to-cover.
There's just a lot of things the UNIX dudes have already implemented with regards to inter-process communications, files, threads, processes, signals, and the like.
Once you know what UNIX (and Linux) have to offer, then you can start leveraging it. You don't really need to understand everything, you just need to know things to a level that "I can look it up later when I need it".
Again: you're going for breadth, not depth. Skimming over concepts and "remembering them for later". You'll know when you need it, and can come back to the book for depth later on.
---------
For "Tee", and "Awk", and "expect", and stuff... I followed blogposts at Linode and Slicehost back in the day which covered a lot of interesting sys-admin tricks. I'm pretty sure the Slicehost pages are lost (the company was bought out by Rackspace years ago. I don't know if any of that stuff was archived)
I never was a professional sys-admin. But knowing about Awk, Tee, or various other "standard command-line tools" that web-developers use all the time allows me to script up a lot of things related to testing code, Makefiles, and the like.
I basically got that experience from just messing with servers: trying to run my own mail server or web server on the side. Cronjobs, automation, etc. etc.
It is available on O'Reilly/Safari
* Addressing scaling bottlenecks with a large focus on reliability and fault-tolerance.
* Concepts orthogonal to the core ask (ex: security, privacy, auth n/z, compliance).
* Cost. Ultimately the most scalable architecture may not be very cost effective; the 2nd best option might be much cheaper and merits discussion.
These are for large scale design questions. Questions to L6 candidates are posed (deliberately) ambiguously to see if they can tease apart the important/finer details.