
Mirantis Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 32 interview experiences · FREE TO READ
Which role are you interviewing for?
18 roles · 32 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Mirantis.
Product Manager
So, the interview for the product role with the hiring manager went like this: We started with intros for about 5 minutes. Then we dove into product experience questions for about 30 minutes, where I asked about their problem-solving methods, how they work with sales and marketing, knowledge sharing, and their experience with developers and UX. Finally, the candidate got about 10 minutes to ask me questions.
- Could you walk me through your process for tackling a problem, from defining success criteria to execution and delivering results?
- Tell me about your experience working with sales and marketing teams. How did you approach those collaborations?
- What does your day-to-day collaboration with developers and the UX team look like?
Deployment Engineer
There were 4 interviews in total. The first one was with HR and covered typical non-technical questions. The second interview was a mix of general IT questions, touching on various areas without going too deep into any single one. For instance, questions ranged from linux process states to TCP segment structure, DNS authority servers, and caching strategies like cache-through and cache-aside. The third interview focused on three key areas: linux internals, networking, and python, with interviewers increasing the difficulty until the answer was no longer known. The final interview was with the engineering manager. It didn't involve direct technical questions but instead focused on a discussion about the future of technologies, requiring knowledge of trendy projects and current buzzwords.
- Could you describe Linux process states?
- What is the structure of a TCP segment?
- Explain Linux namespaces and cgroups.
Architect
The process started with emails and phone calls, then moved to in-person interviews. I first spoke with a recruiter who connected me to the hiring manager. After a good chat with the manager, he introduced me to the Director and VP. I then had a call with the Director, which led to an on-site interview where I met many people from the company. This on-site involved mini-interviews with the manager, developers, support staff, and the Director and VP. The atmosphere was relaxed, and the people were genuinely engaging. It was a unique interview where I felt they wanted me to succeed and showcase my knowledge, unlike other places that focus on what you don't know. I had other offers, but this interview made me feel something special about Mirantis.
- Can you discuss OpenStack architecture?
- What are your Linux fundamentals?
- Tell me about a time when...
Sales Operations Specialist
I was first contacted by a recruiter who wanted to set up a call. After chatting informally with the recruiter, I had an interview with the hiring manager, then another with the VP of sales, and finally, a round with two team members. I had to be flexible and arrange two of these interviews for the evening because the team is all based in the US. They told me at every step that the interview went well and quickly asked for my availability for the next one. Things were moving fast until the last stage when I didn't hear back from HR for days, then weeks. I emailed them asking about the decision timeline and was told 'in the next few days' and that 'the interview went well.' I was expecting an offer, given how positive the interviewers were. But I just kept waiting and heard nothing. I followed up again, and after some time, I got a standard rejection email, with no explanation for the delay or the rejection. It felt like they were just stringing me along. If they didn't think I was a good fit, they should have rejected me immediately. I later checked, and the position was still open, so it seems they're unsure about what they need. Overall, it was a bad experience, and I wouldn't recommend applying. Find a company that respects your time and experience. Mirantis doesn't.
- Regarding the Mirantis Mindset, which aspect resonates most with you?
Mirantis Interview Questions
Quoted word for word from Mirantis interview reports.
“What is the structure of a TCP segment?”
Read reports →“What is the difference between Python mutable and immutable types?”
Read reports →“Can you write quicksort in-place in python?”
Read reports →“How many VLANs can be created in a single network?”
Read reports →“Explain Linux namespaces and cgroups.”
Read report →“What exactly is Ceph, and how does it integrate with Openstack?”
Read report →“What do you understand by stateless High Availability?”
Read report →“Given a problem, perform a DFS.”
Read report →“Can you explain what the GIL in Python is?”
Read report →Formats, difficulty and experience
Across all 32 Mirantis interview reports.