The Karat interview: a rubric, not a conversation
A Karat interview feels strange the first time because the usual social contract is missing. The interviewer is not your future colleague, has no stake in the team you would join, and cannot be charmed into overlooking a gap. They are a trained interviewer running a standardised round on the company's behalf, recording it, and filling in a rubric while you speak. That is not a bad thing — it is far more predictable than a conversation.
How the hour is spent
- Five minutes — introductions and an explanation of the format.
- Around ten minutes — short domain-knowledge questions in your stated area. Factual, quick, not a discussion.
- Forty to forty-five minutes — live coding in Karat's editor while you share your screen, typically one or two problems with multiple parts.
- Five minutes — your questions.
It is recorded and handed to the hiring company, which means two audiences: the interviewer scoring you live, and whoever at the company rewatches the tape later.
The domain questions are not a warm-up
The short factual segment catches people out because it feels like small talk. It is scored. If you said backend and Python, expect questions on the GIL, on how a dictionary resolves collisions, on what a database index costs on write.
Answer in two or three sentences and stop. A rambling four-minute answer to a thirty-second question costs you coding time you will want back later, and it reads as an inability to judge scope.
Why the problem keeps growing
Karat problems usually come in three or four parts, and the escalation is deliberate. Part one is comfortable. Part two adds a constraint. Part three frequently makes your part-one structure wrong — a list that now needs to be a heap, a single pass that now needs a cache.
Knowing that in advance changes how you write part one. Keep it clean and factored, name things properly, and do not inline everything into one function you will have to unpick under time pressure. You are not being graded on how fast you produced part one; you are being graded on whether you can still move when part three arrives.
Say the things that get written down
The interviewer records evidence against named competencies. Evidence means sentences they can quote. Three habits produce most of it:
- State the complexity before you are asked. "This is O(n log n) because of the sort, and O(n) space." That is one line, and it fills a rubric row.
- Ask about constraints and edge cases at the start. Input size, duplicates, empty input, whether the data fits in memory. Clarifying questions are scored, not tolerated.
- Narrate the brute force before you optimise it. "The naive version is quadratic; let me get that working and then cut it down." If you run out of time, you still have working code and a stated plan.
Silence is the one thing that cannot be scored. A person who thinks quietly for six minutes and produces perfect code gives the rubric almost nothing to hold on to.
Practical details worth knowing beforehand
You code in Karat's environment, not your IDE, so no autocomplete of the kind you rely on and no plugins. Spend ten minutes the day before writing a linked list and a hash map in a plain editor — the friction should not be a surprise on the day.
You will be asked to share your screen and the session is recorded. Have the desktop presentable, the notifications off, and one glass of water within reach: it is a fast hour, and it is the same hour whether or not you spent it explaining yourself out loud.
FAQ
Does Karat work for the company I applied to?
No. Karat conducts the technical round on the company's behalf with trained interviewers, records it, and passes the scored result and the recording to the hiring team, who make the decision.
Is the Karat interview recorded?
Yes, and the recording goes to the hiring company. Assume anything you say or show on your screen can be rewatched later.
Can I use my own editor in a Karat interview?
You code in Karat's own environment while sharing your screen, so practise once without your usual autocomplete and plugins before the day.
What happens if I do not finish the last part?
Partial progress with a stated plan scores. The parts escalate on purpose and many candidates who pass do not finish the final one — what is graded is how you reason and adapt, not whether every part compiles.