Interview consists of a screening by a recruiter. I was discovered by a recruiter for this position. After that I was given an online test to which measured my Linux/Networking/Configuration Management/Scripting Skills. The next few steps were a series of onsite and off-site phone and in person interviews which typically lasted for an hour. I talked to 2-3 Deployment Engineers in the Austin and California offices as well as the Deployment Engineer Manager. Topics covered Openstack, Configuration Management, Operating Systems, etc. Think about your typical high level ops/engineering role questions. I got through all of this over the course of four weeks and was given a verbal offer. I did not receive the offer within the deadline the recruiter initially told me. I waited roughly a week after to give them time. I was given a very nebulous answer that there are a few internal financial and managerial roadblocks that they must resolve before presenting a formal offer. All whilst this time by the way the job is still posted. As a matter of fact it was re-posted several times. I waited a week and a half later to contact the recruiter about the status and I was told that there was a hiring freeze on their end. I am aware that Openstack's presence in the Cloud Computing space has started to dwindle in lieu of AWS and others which has forced Mirantis to change its business strategy over the past few years which could explain reviewers of the company stating mass layoffs and re hirings. This could explain the reason why my offer didn't manifest into anything physical. I feel like I was given the runaround a little bit after verbally accepting something. It could be upper management as mentioned but it could have been a situation where they were fishing for candidates. I interviewed previously this year as well and a recruiter stopped contacting me as well so who knows.

There were 4 interviews. First one with HR and usual set of non-technical questions. The second interview had a log of general questions, related to different areas in IT. There were no digging deep into some particular topic, but a lot of areas were touched. For example, after question about linux process states, there were question about TCP segment structure, DNS authority server, cache-through and cache-aside etc. The third interview was concentrated on three main topics: linux internals, networking and python. Interviewers asked harder questions until you didn't know the answer. The last interview was conducted by engineering manager. There were no direct technical questions, but the conversation was built around future of the technologies, therefore you should follow some trendy projects and modern world buzzwords.