Intact logo

Intact Interview Questions
& Process

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

Based on 513 interview experiences · FREE TO READ

2.1 Rounds average
Average Typical difficulty
62% Positive experience

Which role are you interviewing for?

30 roles · 513 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Intact.

Showing 4 of 513
Intact logo
Intact

DevOps Engineer

Engineering · nearly a year ago

Mid Average Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical

The interview process started with an initial screening, followed by a second round with several team members discussing my experience. This round was more about them getting to know me and exploring my background. The third round involved more team members and a test of my technical knowledge. It wasn't a LeetCode-style test, but rather conversational. Although the job posting and everyone I spoke with described it as a DevOps role, the interview heavily focused on advanced Git topics, making me feel misled as it seemed they were seeking a Git administrator. When I inquired about other responsibilities like infra, monitoring, and AWS (all mentioned in the job description), they confirmed these would be part of the role but consistently steered the conversation back to Git. This felt dishonest; if they had advertised it as a Git Admin position, the interview questions would have been appropriate.

Confirmed questions1 question
  • Can you describe a situation where you had to resolve a complex dependency issue involving nested dependencies?
Intact logo
Intact

Security Analyst

Engineering · nearly a year ago

Entry Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Behavioral

I had a second interview with the manager and product owner, but I didn't feel like a good fit at all. It was a Monday morning at 9:30, and I felt like I was the last person they wanted to see. They asked extremely generic questions, nothing personalized, and no questions about our analysis or work methods. What I liked about the job description was that the responsibilities were very varied and required someone versatile, but in the end, the position had one essential mission because everyone had to specialize. So, two-thirds of the role involved knowledge that wouldn't actually be applied (?!). I decided to stop the recruitment process the day after my second interview.

Confirmed questions4 questions
  • Could you explain the CIA triad?
  • What is CVE?
  • What is CVSS?
Intact logo
Intact

Software Engineer Intern

Engineering · nearly a year ago

Intern Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding Behavioral

So for the interview process, they covered OOP, Java, Spring, and some behavioral questions about teamwork. There was also a bit of multiple choice trivia on Java, which was pretty easy if you know your stuff. They also touched on agile and the test pyramid. I was asked to give an example of when I had to face a challenging situation.

Confirmed questions8 questions
  • Can you explain the distinction between an abstract class and an interface in OOP, and provide an example?
  • What are your thoughts on OOP?
  • How would you describe your experience with Java?
Intact logo
Intact

AI Engineer

Engineering · a year ago

Entry Average Negative experience No offer 2 rounds
Interview process
Take home Recruiter call
Interview formats
Coding Behavioral

The recruitment experience at Intact was quite a letdown. After I finished and did well on their initial coding test, I was supposed to schedule the next part. But, they were really rigid about when I could do it, with only a few times available that were tough to make work. Even though I rearranged my own schedule and waited around for weeks, the HR people just stopped responding. No one got back to me, no news — just silence. It's a bummer to experience this kind of unprofessionalism, especially after putting in time and effort. A quick update or at least a heads-up would have been nice. I hope they get better at how they handle candidates and show them more openness and consideration.

Confirmed questions5 questions
  • Describe your experience with coding assessments.
  • What are your expectations regarding communication and updates during the recruitment process?
  • How do you handle inflexibility in scheduling professional appointments?

Intact Interview Questions

Quoted word for word from Intact interview reports.

Can you explain the difference between a random forest and a gradient boosted decision tree?

Read reports

Here's a brain teaser: how would you estimate the number of fish in a large pond?

Read reports

Can you recall the name of the method used to retrieve a website's URL?

Read reports

If financial data is missing, what key elements do you examine in a credit report?

Read reports

Can you explain the distinction between an abstract class and an interface in OOP, and provide an example?

Read report

Could you explain the concept of variance to someone without a university-level math background?

Read report

Can you explain what a storyboard is and what a VM (view model) is?

Read report

Can you answer basic Python questions, like the difference between a tuple and a list?

Read report

How would you explain a machine learning model to someone who is new to the field?

Read report

Formats, difficulty and experience

Across all 513 Intact interview reports.

Interview formats

Behavioral 49.1%
Technical 32%
Coding 6.8%
Other 6.1%
Presentation 3.2%

Interview difficulty

Easy 18.1%
Average 70.4%
Difficult 11.5%

Candidate experience

Neutral 21.2%
Positive 62%
Negative 16.8%

Reports by job function

Operations 140
Analytics 94
Engineering 92
Finance 85
Other 47
Sales 23