Kainos logo

Kainos Software Engineer Interview Questions
& Process

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

Based on 37 interview experiences · FREE TO READ

2.3 Rounds average
Average Typical difficulty
67.6% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Kainos.

Showing 3 of 37
Kainos logo
Kainos

Software Engineer

Engineering · a year ago

Entry Average Positive experience Accept offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical Coding

We started with an intro call with a recruiter. They asked 5 questions about Kainos business and location, my favorite food, to tell them about myself, and why I want to work here and this role specifically. After that, there was a technical interview with a simple Leetcode question and more behavioural questions.

Confirmed questions6 questions
  • Can you tell me what Kainos does?
  • Tell me about yourself.
  • What's your favorite food?
Kainos logo
Kainos

Senior Software Engineer

Engineering · more than a year ago

Senior Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Phone screen Presentation
Interview formats
Behavioral Technical Presentation

I was contacted by a recruiter from outside the company. Round 1 was a 15-30 minute call with that recruiter, asking general questions about tech and my experience. Round 2 was a 45-minute technical call with a Senior Software Engineer where they asked more detailed questions about Java, my past projects, and leading a team. Round 3 was a 1.5-hour presentation of a past project I worked on, either as a team member or lead, followed by technical questions about the design and behavioral questions.

Confirmed questions8 questions
  • How would you safeguard your Java system against SQL injection or XSS attacks?
  • Could you discuss the SOLID principles and provide an example of when you applied one or more of them?
  • What are the advantages and disadvantages of Monolith vs. Microservice architectures?
Kainos logo
Kainos

Software Engineer

Engineering

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

The interview process had two stages. The first interview was competency-based, needing answers using the S.T.A.R. technique. Doing well meant moving to the second stage, a coding exercise with a LeetCode-style problem. The hiring manager seemed rushed in the second technical interview, wanting me to start coding before I fully understood the problem, and his negative demeanor made him seem like someone I wouldn't want to work with. I heard back a month later, confirming I didn't get the job, and I still haven't received feedback despite asking multiple times.

Confirmed questions2 questions
  • What is your motivation for seeking employment at Kainos?
  • Could you describe a recent project you were involved in?

Kainos Software Engineer Interview Questions

Quoted word for word from Kainos interview reports.

What are the reasons for choosing an RDS instance over an EC2 instance for hosting a database?

Read reports

What are the advantages and disadvantages of Monolith vs. Microservice architectures?

Read reports

How would you safeguard your Java system against SQL injection or XSS attacks?

Read reports

How would you program a magic 8 ball to generate a different answer each time it's used?

Read report

Can you show me how to reverse this string on the whiteboard?

Read report

Suppose the system we just deployed to production is experiencing a P1 incident. What steps would you take to resolve it?

Read report

How would you handle a situation where a stakeholder continuously alters requirements?

Read report

What would you do if you noticed a more efficient method while a teammate was presenting it to the group?

Read report

Formats, difficulty and experience

Across all 37 Kainos interview reports.

Interview formats

Technical 35.5%
Behavioral 32.3%
Group 16.1%
Coding 14%
Presentation 2.2%

Interview difficulty

Easy 10.8%
Average 81.1%
Difficult 8.1%

Candidate experience

Positive 67.6%
Negative 18.9%
Neutral 13.5%