Prepare
The third follow-up is the interview
Question banks teach recall, and recall is what a competent interviewer is trying to see past. Nobody is really assessing your answer to “what is Docker” — they are using it to decide where to start. What distinguishes candidates is what happens three questions later, once the surface answer has been given and the interviewer keeps going.
So these are chains. One opening question, then the follow-up that answer genuinely invites, down to something you would only know from having operated the thing. Each link gives you what a strong answer contains rather than a script, names the specific trap, and says what the interviewer is actually probing — which is usually not the stated question.
Answers start hidden on purpose. Answer in your head, then compare. That is the part that transfers to the room; reading a transcript produces people who recognise a good answer without being able to produce one.
- Docker · Junior to mid · 6 questions
Docker: from “what is it” to production
Starts at “What is Docker?” and ends at “You add a HEALTHCHECK and the container still takes 10 seconds to stop. Why?”
- Kubernetes · Mid to senior · 6 questions
Kubernetes: debugging under pressure
Starts at “A deployment says 3 replicas but only 2 pods are running. How do you investigate?” and ends at “How would you stop this class of problem from recurring?”
- CI/CD · Senior · 6 questions
CI/CD security: the pipeline as an attack surface
Starts at “How would you manage secrets in a CI/CD pipeline?” and ends at “Which of these would you fix first, and how would you justify the order?”