Codility logo

Codility Software Engineer Interview Questions
& Process

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

Based on 10 interview experiences · FREE TO READ

2.2 Rounds average
Difficult Typical difficulty
40% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Codility.

Showing 3 of 10
Codility logo
Codility

Software Engineer

Engineering · half a year ago

Entry Difficult Negative experience No offer 2 rounds
Interview process
Take home Technical screen
Interview formats
Coding Technical

It started with a pretty easy online assessment on their own platform. After that, there was one technical interview with the manager and some senior devs. They hit me with a LeetCode hard question and some technical C++ questions, which was a bit odd since the role was for Python.

Confirmed questions3 questions
  • Could you solve a LeetCode hard problem related to prefixes?
  • Did you encounter a LeetCode hard question during the interview?
  • Were you asked any technical questions about C++?
Codility logo
Codility

Software Engineer

Engineering

Mid Difficult Positive experience No offer 2 rounds
Interview process
Take home Recruiter call Technical screen
Interview formats
Technical Behavioral

The interview process involved an online test and then two video calls. Each video call had two interviewers, one focusing on technical aspects and the other on background. The interviewers were very friendly. The online test and the questions during the video calls were of moderate difficulty, but they required quick and accurate implementation.

Confirmed questions1 question
  • Can you flatten a tree in the context of version control?
Codility logo
Codility

Software Engineer

Engineering

Entry Difficult Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Technical screen
Interview formats
Behavioral Technical

The interview process was quite disappointing. It started with an honest and friendly HR recruiter call that I really enjoyed. After that, there were supposed to be two technical rounds. The first was a discussion with a team lead, which felt promising initially, like talking to a future colleague. However, it turned into a confusing theoretical assessment where I had to spot visual bugs in a GIF of user interaction. The task's objective was really unclear, and I had to ask several times what I was supposed to do. When I tried to explain what I thought were issues, the interviewer cut me off and told me to focus on just one problem and how to fix it. Even then, the task remained vague, and the rules seemed to change. It was hard to suggest solutions without knowing the tech stack, state management, or seeing the code, just from a GIF. The interviewer ended by saying there were no right or wrong answers, which felt odd and unproductive. It might be useful for someone who's good at visual debugging, but I don't think it showed my technical skills well. I hope others don't have this experience. I later received an email saying they moved forward with other candidates.

Confirmed questions2 questions
  • What made you decide to apply for this job?
  • Can you explain why you decided to apply for this role?

Codility Software Engineer Interview Questions

Quoted word for word from Codility interview reports.

How would you reverse a linked list using only O(1) memory space?

Read reports

Could you solve a LeetCode hard problem related to prefixes?

Read reports

If you had to explain what an API is to a 60-year-old, how would you do it?

Read reports

Did you encounter a LeetCode hard question during the interview?

Read report

Formats, difficulty and experience

Across all 10 Codility interview reports.

Interview formats

Coding 40%
Technical 35%
Behavioral 25%

Interview difficulty

Easy 0%
Average 40%
Difficult 60%

Candidate experience

Negative 50%
Positive 40%
Neutral 10%