
Immutable Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 18 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Immutable.
Software Engineer
First, you'll have a phone screening to see if you're a good fit. Then, there's a video interview with the Hiring Manager, where they'll check your behavioral and technical skills. Remember to use examples relevant to the job.
- Describe a past challenge you faced and explain how you resolved it.
Software Engineer
The hiring process moved pretty fast, with two initial screens followed by a two-part technical assessment. I think the last step was supposed to be a behavioral interview, but I withdrew before getting to that stage. The first few rounds were alright, but the technical part was quite strange. I was told it would be in one programming language, but it ended up being in another. The entire exercise was conducted on some ad-filled free website that also had issues running any code. The system design portion felt more like a Q&A session rather than actual design work. It wasn't overly difficult, but the questions were very dated, focusing more on reciting 'correct' answers than on problem-solving or design ideation. Luckily, I'd read some reviews here and decided to back out before the next round.
- Could you describe a project you were proud to have completed?
Software Engineer
The interview process involved a few stages. First, there was a recruiter screening call to go over my experience and explain the interview process, while also trying to sell me on the company. After that, I had a call with a senior technical team member to assess personality fit and soft skills. The next step was a live pair programming session with two members of the engineering team. This was supposed to be a 1.5-hour meeting where I'd get a URL to a live coding web app. The problem was split into two parts: 45 minutes for system design and the rest for implementing a portion of it. However, the experience with the live coding part was not great. The online tool they used was problematic and difficult to use. Also, the interviewers were very quiet and not very responsive to questions about the assignment during the design phase. Things got a bit better during the implementation part, as the tool was more manageable and the interviewers were more engaged. Overall, it was a mediocre experience, and I think they should reconsider their technical interview approach.
- Can you design a sequential ID generator for a marketplace context?
- Could you implement a part of the assignment?
Immutable Software Engineer Interview Questions
Quoted word for word from Immutable interview reports.
“Can you design a scalable sequential ID generator that produces IDs like 1, 2, 3?”
Read reports →“Could you implement a trading question in Golang?”
Read reports →“Can you design a sequential ID generator for a marketplace context?”
Read reports →“Could you now code a portion of the design you just created for the sequential ID generator?”
Read reports →“Design a system and then implement the business logic”
Read report →“Could you devise a system for generating IDs for a marketplace, and demonstrate some of its functionality and code?”
Read report →“How would you approach scaling a solution to handle increased load?”
Read report →“Describe your process for documenting a solution so that other team members can understand it.”
Read report →“Describe a situation where you lovingly spoke your mind.”
Read report →Formats, difficulty and experience
Across all 18 Immutable interview reports.