
Equal Experts Devops Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 8 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Equal Experts.
DevOps Consultant
It took like 2 months from resume submission to get them to actually interview me, and I had to reach out to 3 recruiters and even comment on their public post to get a response. First, there was a call with a recruiter, and then I was sent a take-home test. After I submitted it, I got feedback saying I showed technical incompetence because the reviewer apparently couldn't tell that my submission was a Python script.
- Complete a DevOps-related take-home test, choosing one out of three provided problems to solve.
DevOps Engineer
The interview process was challenging. The first stage was a take-home challenge that they said should be done in an hour, which I think is just to put pressure on. It took me 24 hours in total. The challenges were tough, so take their 'expected time' with a grain of salt if you're not a genius. The second stage was an interview with an Engineering Veteran. It's a pleasant pairing exercise where you interact with people and problem-solve together. The last stage was a formal chat with one of the Managers. It was friendly and semi-informal with a few interview questions thrown in. My experience from the interview through to working with the company confirmed everything they said. They are extremely professional people with a sense of humor, compassion, and drive. Everyone there is focused on excelling and delivering. I worked with them for 6 months as a contractor before moving to another client. I would be excited to return if they called with a great opportunity.
- Describe a situation where you attempted to influence a client, but they didn't listen, leading to failure. What alternative actions could you have taken?
DevOps Engineer
The interview process was three stages. First, a phone call with HR and a programming test. Then, a technical interview and pairing session. Finally, an interview with a partner. The HR person was really knowledgeable and spent time explaining how the company works and what they look for, going over my CV. I got a take-home test with no deadline. I messed up file permissions, but they emailed me about the problem and asked if I could fix it, plus some other questions. I answered and fixed it, which was good enough to move on. The second stage had me meet a Tech Lead. They seemed more interested in what I could do. We discussed my experience and company operations, then did a pairing exercise where I chose the language. We did some URL and JSON manipulation. The interviewer let me lead but asked questions and was like a friendly pairing buddy. We ran out of time, so I finished some on a whiteboard using pseudocode because they cared more about my problem-solving skills. The third stage was with a senior partner, mostly about company values and cultural fit. It was also a friendly chat, not a tough interview. Even though it's three stages, it didn't feel long, taking about a week total. I got fast feedback at every step. The HR person even offered me the job late Friday after the last interview. The best part was that I actually enjoyed it. Everyone seemed to be looking for reasons to hire me, unlike most interviews I've had. I'd recommend it even if you don't get the job.
- Was there anything you didn't expect or find particularly challenging during the interview?
Equal Experts Devops Engineer Interview Questions
Quoted word for word from Equal Experts interview reports.
“Can you implement Fizz Buzz?”
Read reports →“Are TDD and architecture key considerations for the challenges?”
Read reports →“What is your understanding of cloud services and scalability?”
Read reports →“Describe a situation where you attempted to influence a client, but they didn't listen, leading to failure. What alternative actions could you have taken?”
Read reports →“Explain your choices for infrastructure setup.”
Read report →“Can you discuss system design?”
Read report →“Can you describe your experience with CI/CD pipelines?”
Read report →“Tell me about a time you had a disagreement with someone and how you handled it.”
Read report →“Was there anything you didn't expect or find particularly challenging during the interview?”
Read report →Formats, difficulty and experience
Across all 8 Equal Experts interview reports.