A predecessor to the role I was applying for had become the department manager, after 15 years of effort with the company. He opened-up with a story of something that happened a long time ago for him, then proceeded to explain a set of printed network architecture diagrams, that had every layer enabled on the print (making it look unnecessarily complex). I was able to read and explain the diagrams and solved his riddles and technical questions. When it came to discuss the particulars of the role, I had so many questions around why certain parts of the system architecture and engineering teams had been organized in such a way that would cause such a long deployment cycle. This prompted a long and enjoyable history lesson around how they tried to deploy some of the tech I was asking about once before, long ago in his history with the company. I was when I had asked why these ideas were never revisited, that he seemed to have decided that he didn't like me anymore. Anyways, I ended up learning that this was an old-school IT manager guy, trying to start-up a devops team - but he wanted to run it like a break-fix tech-support type of iterative cycle, and i was unable to explain the benefits of the DevOps lifecycle, applied agile methodologies or even holistic approaches to problem solving.