First call from an outside recruiter. Quickly scheduled a 2nd call with a lead engineer. The call didn't leave a lot of room for conversation or being casual; emphasis was placed on it being a pure tech screen. I asked questions about the team, the company's trajectory/goals (why they are hiring), current issues they're looking to solve, and what technology, tools, or vendors they use. There was little room for organic conversation and the interviewer was visibly irritated when I asked questions about other teams. It's clear they want to move to the cloud, but I didn't get a clear answer on how they intend to approach that change. Because the role was stated "DevOps" with preferred requirements of cloud, virtualisation, and automation, I expected that info to be up front, but I was met with contempt instead. Maybe that speaks to how they run things (more impersonal by design). The engineer proceeded to ask network-specific trivia and some AWS VPC questions, but did not give much room for discussion. I got the impression this was more of a pass/fail or they were looking for textbook answers. I wasn't a good fit because of this, but I did not have a good experience because any attempt to elaborate or discuss tech in general was met with haste or interruptions. I did not get a good view of a day-to-day experience of the company or what they expected specifically from a DevOps role. I think it'd be important for them to define exactly what they are looking for in order to find talented candidates; but maybe this is by design. As far as DevOps and corporate/banking is concerned, I got the impression they need someone to do tasks as they are made instead of being a part of a larger architectural/policy design effort. My overall impression was that individuality and creativeness don't seem important here; maybe they'd rather have people who know the facts and can do tasks point-blank with no questions asked while the company/management figures out the bigger picture.