Software Engineer applicants have rated the interview process at Mutiny with 2.9 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 79% positive. To compare, the company-average is 58.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 16 days to get hired, when considering 14 user submitted interviews for this role. To compare, the hiring process at Mutiny overall takes an average of 15 days.
Common stages of the interview process at Mutiny as a Software Engineer according to 14 Glassdoor interviews include:
Phone interview: 30%
One on one interview: 30%
Presentation: 15%
Group panel interview: 10%
Skills test: 10%
Background check: 5%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 2 weeks. I interviewed at Mutiny in Oct 2021
Interview
The process included multiple stages. I was pleasantly surprised by the approach. Instead of relying on algorithms, the problems were related to close what an engineer would perform daily. In general, it was one of the best interview processes.
Interview questions [1]
Question 1
Q: Add caching solution to endpoints. Give reasoning.
I met with the CTO for an initial screening, hoping to learn more about the team and culture. Unfortunately, he seemed completely uninterested from the start and largely refused to answer my questions about Mutiny’s people or processes. When I asked how he actively fosters the company’s professed culture and values, his response was literally, “It pretty much handles itself.”
As someone who’s followed the CEO’s talks on the importance of thoughtful hiring and cultural stewardship, this was really disheartening. If culture is important to you, don't be fooled by their public messaging
Interview process tries to simulate real work. The question setup is in marketing tech, so they want to see how you think in real world terms. The interviewers are super supportive.
First round was a phone screen with the CTO. The call went well and moved forward to the coding interview. The interviewer for the coding interview was an early engineer at the company and was very difficult to understand. The base question was easy, but when he started asking follow-ups I had a hard time understanding him and he had a hard time understanding me. It ruined the interview. Very disappointed that they don't have a higher bar for who they choose to let interview!