
Kainos Enterprise Architect Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 5 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Kainos.
Technical Architect
So the interview started with a 30-minute chat with another architect. He hit me with some basic programming questions relevant for an architect, like how I'd define a good class and asked about SOLID principles. It was also a chance for me to ask my own questions. Then, a couple of weeks later, we had a face-to-face session. There was one manager in person and another joined via Skype. I had to do a whiteboard presentation and they really dug into my design choices and my thought process. It was a good chance to highlight my skills and how they fit the role.
- What makes a class well-designed in programming?
- Can you explain the SOLID principles?
Technical Architect
The interview was about an hour and pretty chill. It covered a bunch of stuff like how I'd deal with team issues, manage workflows, do design and code reviews, and talk about customer NFRs and architecture designs. I also had to dig into the tech design of an app I worked on and handle questions about it. The questions were mostly easy, with a couple tough ones, but it felt friendly, no one was trying to trick me. The interviewers were nice and paid attention. I applied and interviewed within days, but haven't heard anything back in almost 4 weeks, even after emailing recruiting. Still no word.
- What's your approach to helping a teammate who's having a hard time with their tasks?
- Could you describe an application you've recently worked on?
- How would you approach challenging non-functional requirements?
Technical Architect
A recruiter reached out because of a referral, setting up a 1-hour meeting with the hiring manager at the London office to check my people skills. Then I went to their Reading office for another 1-hour meeting with a Technical Architect. After that, I had a 1-hour meeting with the CTO digital, which was super technical. The agent was nice and helpful. The hiring manager liked my skills and wanted me on the team. The technical architect was impressed with my tech and how I handle situations. The CTO had high expectations and wanted to see my technical skills, asking me to show designs from past work. He seemed really busy though. The hiring manager called a week later with feedback and wished me luck. The CTO wanted a full stack architect, but I'm more backend, and I guess the agency didn't realize until the CTO rejected me. Overall, it was a good experience, just wish the CTO had smiled! It's a good team, and their hiring process seems to help them get the right people for their new projects.
- Can you discuss your strategy for evaluating technology?
- Describe how you handle different scenarios.
- Please provide a design from a previous project.
Kainos Enterprise Architect Interview Questions
Quoted word for word from Kainos interview reports.
“What makes a class well-designed in programming?”
Read reports →“Can you explain the SOLID principles?”
Read reports →“In a customer meeting where the client objects technically to a solution you know is correct, how would you handle that situation?”
Read reports →“How would you approach challenging non-functional requirements?”
Read reports →“What's your approach to helping a teammate who's having a hard time with their tasks?”
Read report →“Can you discuss your strategy for evaluating technology?”
Read report →“Can you use the whiteboard to explain a project you were involved in?”
Read report →“Describe how you handle different scenarios.”
Read report →“Could you describe an application you've recently worked on?”
Read report →Formats, difficulty and experience
Across all 5 Kainos interview reports.