1. How can you include re-use parts of code in different jobs? ( I guess chatgpt or google will not be able to answer this if someone did not know it) I answered anchor tag or include but the interviewer was looking for "extends" was very excited to tell me about it :-) 3. some work related question, a bit vague but did not really understand what the interviewer was asking. He also did not do follow up questions, so he either thought I am miles off or as I said I did not understand the questions. but there was no concrete questions, nothing related to why I took a a decision, not from a technical perspective. 2. Hilarious question: Are dockerfiles reproducable? : After the interviewer explained to me the answer I realised the interbviewer does not understand how docker image tagging work( I am assuming he has used latest tag and always found a slight different version of the image) but at this point I have already wanted this interview to end. 3. Are docker containers stateful or stateless(This was the only fair question in the interview) . But then there was no follow up question, He just went on explaining how containers can be made stateful with volumes. well partly wrong explanation, not all type of volumes provide statefulness, because docker also has non-persistent volums. But as I said I wanted the interview to end. and never seen such arrogant people in my life before. 4. What does dev ops mean to you? 5. Difference between ansible and terrraform? (Google: interview question for dev ops engineers)