Karat interview experience can be quite different from traditional interviews. In this article, I’ll share my Karat interview experience, including the questions asked, process, and tips to crack it.
I had a Karat interview scheduled for a leading bank as online screening round. This is the first time I’m attending an interview that’s being conducted by a third party for a company.
Got naturally interested on this process, I wanted to know more about how this interview is taken and started searching online. Guess what, I couldn’t find a single video explaining about the interview pattern and all I could find was interview experiences of people who attended interviews to work for Karat.
So I decided to write this blog in the hope that this could be of help for someone to better prepare mentally for a Karat interview.
Disclaimer: Their interview pattern might not be the same for all companies and the companies themselves also could have partnered with them to frame the question areas.
P.S: Not revealing any questions I encountered to maintain ethics
So following is their interview pattern
- Introduction – 5 minutes
- Technical questions – 10 minutes
- Coding and debugging – 45 minutes
Introduction
This section is about both ways. The interviewer from Karat introduces about themselves and also explains about the interview pattern, which, you’re reading here, wink wink.
And then you introduce about yourself and the request would be to do that in under 60 seconds.
Technical Questions
So this part of the interview is questions on basics and intermediate concepts in your programming language of choice and depending on the role you’re opting for.
This section of the interview is a pretty much comfortable zone and you can complete this if you’re decently prepared.
Coding and Debugging
Now this is where things get interesting. This is not your regular, tell a program and you code it kind of a round. And this round tests how quick you’re with debugging and problem solving by assessing how many coding questions you’re able to solve in these 45 minutes.
It typically starts with debugging. You will be presented with a code and the corresponding test cases already written and the question for you would be to identify why one of the test cases fail and what’s the issue with the code.
And the intensity will get increased slowly asking to write logic for a test case that’s already written.
This is how this round goes and this is where I stopped so I don’t have further visibility on whether they will actually ask you to write a code from scratch along with test cases.
What I Liked
Was how unbiased the questions were and also how it focused more on your problem solving and critical thinking side rather than if you remember the syntax.
And the interviewer. OMG, they were really calm and composed and gave clarity right before the start of the interview on how the rounds will be.
They will also support you midway of the coding round if you need any guidance.
What I didn’t like
Was the lack of guidance online about the interview pattern which is not the case anymore, wink wink.
I hope this post might have given you some insights on what to expect from your Karat interview that’s scheduled real soon and how prepared you should be both technically and mentally.
Go get it. Good day to you 🫡.
