Collibra logo

Collibra Software Engineer Interview Questions
& Process

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

Based on 15 interview experiences · FREE TO READ

3.5 Rounds average
Average Typical difficulty
40% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Collibra.

Showing 3 of 15
Collibra logo
Collibra

Software Engineer

Engineering · nearly a year ago

Mid Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Phone screen Take home Technical screen Onsite
Interview formats
Coding Technical Other

I went through a few interview stages. It started with HR, then the hiring manager. After that, I got an assignment which was pretty easy to complete, and then I was supposed to interview with the team. I didn't make it to the final round because I wasn't prepared for a live coding portion, which wasn't really relevant to my current role. It wasn't difficult, just unexpected. Overall, the process was okay.

Confirmed questions1 question
  • Live coding: solve BFS and DFS problems.
Collibra logo
Collibra

Software Engineer

Engineering · a year ago

Senior Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Technical screen Onsite Background check Offer
Interview formats
Coding Technical Technical Behavioral Behavioral

It was a nice interview process with a few steps: first, a 30-minute chat with the recruiter. Then, a 30-minute live coding session where I had to build some basic features for a React todo list. After that, a 60-minute deep dive technical interview, finishing with 15 minutes to code two simple React hooks that had one key difference. The final stage was an in-person visit to the office: a 60-minute meeting with a product manager and another 60-minute meeting with an engineering manager. Finally, they extended an offer, and a background check was done through Sterling. I felt like my time was valued and got a good impression of the company.

Confirmed questions1 question
  • What's the distinction between throttle and debounce, and in what scenarios would you implement them?
Collibra logo
Collibra

Software Engineer

Engineering · a year ago

Staff Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Take home Technical screen Onsite Panel Offer
Interview formats
Coding Technical System Design Behavioral

We start with an intro call to get to know you and make sure you're a good fit for the role. If that goes well, you'll do a coding challenge. Pass that, and we'll move to a technical round where we'll dive deep into core Java, Spring, and database concepts, plus a design round. Finally, there's a manager round.

Confirmed questions2 questions
  • Asked to code in Java and Spring.
  • Asked design questions.

Collibra Software Engineer Interview Questions

Quoted word for word from Collibra interview reports.

What's the distinction between throttle and debounce, and in what scenarios would you implement them?

Read reports

Could you explain the benefits of using composition compared to inheritance in object-oriented programming?

Read reports

When you're designing a REST API, what factors do you take into account?

Read report

What's your take on the importance of comments in code?

Read report

Formats, difficulty and experience

Across all 15 Collibra interview reports.

Interview formats

Technical 36.8%
Coding 26.3%
Behavioral 26.3%
System Design 7.9%
Other 2.6%

Interview difficulty

Easy 26.7%
Average 66.7%
Difficult 6.7%

Candidate experience

Neutral 20%
Positive 40%
Negative 40%