Immuta logo

Immuta Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 14 interview experiences · FREE TO READ

3.6 Rounds average
Average Typical difficulty
64.3% Positive experience

Which role are you interviewing for?

6 roles · 14 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Immuta.

Showing 4 of 14
Immuta logo
Immuta

UX Developer

Design · more than a year ago

Entry Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Presentation
Interview formats
Technical Presentation

The initial recruiter call felt really promising, like it was a good match. Then I had a mildly technical interview with the hiring manager, which also went really well. After that, I was invited to speak with the team and prepare a project to present. I sent over my availability, but then I just didn't hear anything back. I emailed the recruiter a few days later and got an out-of-office reply. So, I followed up again the next week and got an apology and a promise to schedule something ASAP. Still nothing. I sent one last email a week after that, mostly expecting a formal rejection or maybe an explanation. No response again. I guess they found another candidate, which is fine, but I had actually slowed down my job search because this one seemed so promising. It's a shame because the role sounded great and I was super excited. Really unprofessional and disappointing experience overall.

Confirmed questions1 question
  • Walk me through the code and design for a few of your recent projects.
Immuta logo
Immuta

Software Engineer

Engineering

Entry Average Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral

I applied online for a job in Boston, but then got a call from a recruiter who was eating and choked while talking to me. She asked if I was in NYC because the job was actually there, not Boston, and they wanted someone in the office. I told her I planned to move to Boston. The whole call felt sloppy and confusing. She then talked about the company getting its series c and series d funding, and when I asked why they took it, she said they weren't expecting the offer and just took the money. It seemed like a naive response and didn't explain the business goals or how they'd use the money and manage investor expectations with that kind of growth. My advice is to get your recruitment team sorted out.

Confirmed questions1 question
  • Can you tell me about your background?
Immuta logo
Immuta

Data Engineer

Engineering

Mid Average Positive experience No offer 4 rounds
Interview process
Recruiter call Technical screen Take home Onsite
Interview formats
Behavioral Technical Coding

I had 3 interviews and a technical task. It started with a recruiter call, then a chat with the Head of Data Engineering. After that, I had a simple API-oriented task where I had to use Immuta's API. The process concluded with an onsite interview with 2 Senior Data Engineers. The whole thing took about a month from applying to the last stage, though it was a bit longer because I applied in December and the holiday season slowed things down.

Confirmed questions2 questions
  • Can you tell me more about a specific project, including the elements you used?
  • In a past project, what led you to select certain tools over others?
Immuta logo
Immuta

Solutions Engineer

Engineering

Mid Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Take home
Interview formats
Behavioral Technical

First, I had a chat with someone from HR to get the lowdown on the company and see if I'd be a good fit culturally, and they told me what was next. Then, I met the folks I'd be working with and they hit me with a bunch of technical questions. Lastly, I got a pretty involved homework assignment that gave me all I needed to complete it on a platform.

Confirmed questions3 questions
  • Could you explain the distinction between virtual machines and containerization?
  • What differentiates Docker from Kubernetes?
  • How would you troubleshoot basic issues, detailing the process to identify the root cause?

Immuta Interview Questions

Quoted word for word from Immuta interview reports.

Could you explain the distinction between virtual machines and containerization?

Read reports

What are your strategies for managing interdepartmental communication?

Read report

Can you tell me more about a specific project, including the elements you used?

Read report

Can you share an instance where project requirements evolved?

Read report

In a past project, what led you to select certain tools over others?

Read report

Formats, difficulty and experience

Across all 14 Immuta interview reports.

Interview formats

Behavioral 37.5%
Technical 31.2%
Presentation 15.6%
Coding 15.6%

Interview difficulty

Easy 7.1%
Average 92.9%
Difficult 0%

Candidate experience

Positive 64.3%
Neutral 14.3%
Negative 21.4%

Reports by job function

Engineering 7
Marketing 3
Design 3
Sales 1