Early Warning Services Devops Engineer interview questions

My experience with Early Warning started off on the wrong foot, when the recruiter attempted to tell me that my skillset was not suited for the role I was applying for, but that I should instead apply for the same role as an associate position. The compensation in that role was low in my range, but knowing my own skillset and capability to advance quickly I was more than willing to consider the option despite the condescending nature it was provided to me in. I like Early Warning, they are a big player here in Arizona. I was willing to make some concessions to work with a company that I felt was paving the future. I will most likely not be applying to Early Warning in the future, unless I start hearing more positive experiences from past employees and news of a better culture overall. Ultimately these things can be overlooked if the interview process was overwhelmingly positive, but mine was not. Early Warning went with a two interview approach for this position, the first interview with the hiring manager was frankly not impressive. His questions were read from a script and he clearly did not know some of the topics he was questioning me on very well. The hiring manager told me with a high degree of confidence that there is no such thing as a private IPv6 address, which is not correct. RFC 4193 defines ULA addresses which are more or less the functional equivalent of a private IPv4 address. Other statements made by him were indicative of a lack of experience and an overabundance of ego. My second interview with the team was more positive, their personalities were excellent and their experience and knowledge was much more clear. My concerns of culture fit were mostly dismissed with this interview. My advice is don't try to undersell inexperienced candidates with a different role, just offer them less. Don't let your hiring managers conduct technical interviews. Don't ever make an offer below a candidates minimum.