One interview question at a time, worked properly
Preparing for a DevOps, SRE or platform loop is mostly a problem of knowing which answers are deep enough. So you get one question at a time and the whole of it: what a strong answer covers, the number or mechanism it has to name, and the follow-up that tells an interviewer whether you have operated the thing or only read about it.
Never more than one email a week, and nothing else. No sharing your address, no selling it, and an unsubscribe link in every email that works on the first click. See the privacy policy.
What is in it
- The question, as it gets askedNot a topic and not a definition. The sentence an interviewer actually says, from the round it belongs to.
- The answer that clears the roundThe shape a strong answer takes, the number or mechanism it has to name, and the place most answers stop one step early.
- The follow-up that decides itThe second question, which is usually the real one. Most candidates lose the loop here rather than on the opener.
- A diagram, when the thing has stagesDrawn for the answer, with the mistake marked beside the stage it happens at. The same ones that sit inside the answers on this site.
Each email is one of these, cut down to fit an inbox. Read the real thing first and decide from that: what actually happens when you kubectl apply to a running pod, diagram included.
What is not in it
No roundups of other people's links, no news, and no second email selling you something three days later. There is no schedule to fill: if there is nothing worth sending, nothing gets sent. The list is for the question, and the day it stops being that is the day you should unsubscribe.
Not ready to hand over an address? The question bank and the concept library are open to read without one.