Integrant logo

Integrant Interview Questions
& Process

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

Based on 46 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
47.8% Positive experience

Which role are you interviewing for?

16 roles · 46 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Integrant.

Showing 4 of 46
Integrant logo
Integrant

Software Engineer

Engineering · a year ago

Senior Average Positive experience No offer 2 rounds
Interview process
Technical screen Onsite
Interview formats
Technical System Design

The interview was super insightful. It really focused on practical, real-world challenges that come up in day-to-day work. They used lots of real-life examples and scenarios, which made the whole discussion super relevant and engaging, and it was all about practical problem-solving.

Confirmed questions4 questions
  • Can you discuss design patterns?
  • Tell me about your experience with architecture.
  • What do you know about queuing systems?
Integrant logo
Integrant

Java Backend Software Engineer

Engineering · more than a year ago

Mid Average Neutral experience No offer 2 rounds
Interview process
Technical screen Recruiter call
Interview formats
Technical Behavioral

We had a technical interview covering specifics like java, spring, spring boot, reflection, junit, mockito, and dependency injection. Following that, I had an interview with the CEO, which was similar to an HR interview.

Confirmed questions5 questions
  • Tell me about Java OOP concepts.
  • How do you approach Data Structures?
  • Can you discuss your experience with Spring?
Integrant logo
Integrant

Talent Acquisition Manager

HR · more than a year ago

Manager Easy Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical

It was a really long process, like 3 months+, they barely followed up or gave updates. The process went from the Recruiter to the CEO's EA, which was weird. Senior leaders didn't even reply to thank you notes, showing poor leadership. They ghosted for over 2 months, I almost forgot. Then the CEO's EA called to say I was still considered and would get an update by end of Feb. Unexpectedly, I got an automated email at midnight from the Recruiter who vanished 3 months ago, saying I wasn't selected. A phone call would have been better after 4 interviews and giving them my time. They also recorded all video interviews without asking for consent beforehand, telling me at the start of the call, which is not okay and probably illegal in North America. There was 1 prescreen, 1 interview with the Recruiter, 1 with the Head of Operations, and 1 with the Founder/CEO. The vibe was cold and stiff, no smiles. I never got clear details about the role or expectations from any interviewer; each had a different vision, making it confusing. My questions weren't clearly answered either. Overall, a terrible candidate experience, I wouldn't apply again. They disrespected my time.

Confirmed questions3 questions
  • Can you tell me about the number of team members you managed in your background?
  • What ATS system have you used?
  • How many roles did you carry as a Recruiter?
Integrant logo
Integrant

Software Quality Lead

Engineering · more than a year ago

Lead Difficult Neutral experience No offer 3 rounds
Interview process
Recruiter call Technical screen Take home
Interview formats
Behavioral Technical Coding Presentation

Applied through LinkedIn and got a call almost immediately to schedule an interview within a week. The interview process took about 5 hours in total, with 3 hours dedicated to a written exam. The first part was an HR interview focusing on personality, ideal work environments, and willingness to travel. Then came the exam, taken on a not-so-great PC. The exam had three parts: first, essay questions mostly from the ISTQB Technical Test Analyst curriculum; second, connecting to a local DB and writing MySQL queries; and third, creating three basic testing documents (test cases, bug reports, test report) for a sample eCommerce project. After the exam, a technical reviewer reviewed the results with me.

Confirmed questions3 questions
  • Can you explain the what, how, and why behind automation testing tools?
  • Can you explain the what, how, and why behind performance testing tools?
  • Can you explain the what, how, and why behind stress testing tools?

Integrant Interview Questions

Quoted word for word from Integrant interview reports.

Is JavaScript multi-threaded, and how does it manage multi-threading?

Read reports

How can you achieve equal spacing between divs using Bootstrap?

Read report

What's the distinction between 'throw' and 'throw x' when handling exceptions?

Read report

Do you need to subscribe and unsubscribe to observables in Angular?

Read report

What's the difference between multi-threading and sync & await?

Read report

Formats, difficulty and experience

Across all 46 Integrant interview reports.

Interview formats

Technical 43.9%
Behavioral 34.2%
Coding 14.9%
Presentation 4.4%
System Design 1.8%

Interview difficulty

Easy 6.5%
Average 65.2%
Difficult 28.3%

Candidate experience

Positive 47.8%
Negative 30.4%
Neutral 21.7%

Reports by job function

Engineering 35
Operations 3
HR 2
Analytics 2
Product 2
Design 1