Technical Interviews
Level 2 Β· Interviews
How firms test the skills a job needs. Live coding, the take-home task and system design, what each one checks, and what to do when you get stuck.
Course contentsLesson 4 of 8
Level 1 Β· Finding the job
Level 2 Β· Interviews
Level 3 Β· Pay and promotion
Level 4 Β· Roles in tech
After this lesson you can
- Name the three common kinds of skills test
- Say what each kind is testing
- Keep talking when you are stuck
12 mincovers 1 glossary entries
Worth reading first: Job Interviews and STAR
How firms test the skills a job needs
A technical interview is one where you show your skills by doing a task, not just talking about them. The three common kinds are live coding, a take-home task and system design. Each tests something different. Many tech firms use two or more of them, after a first short call.
In live coding, you solve a small problem while an interviewer watches, often for about an hour. The answer matters, but so does how you get there. Say what you are thinking. Ask questions about the problem before you start. A clear approach with a small bug often beats a silent, perfect answer.
A take-home task is a small piece of real work done alone, over a few days. It is closer to the actual job and less stressful for many people. It also takes more of your time. Keep to the limit they set, and write a short note on the choices you made and what you would do with more time.
A system design interview asks you to sketch how a large system would fit together, such as a photo sharing app. It is mostly for senior roles. There is no single right answer. The interviewer wants to hear the trade-offs: what you chose, what it costs, and what would break first as the system grew.
Prepare for the kind you will face. Ask the recruiter what the stages are and what each one covers. Most will tell you. For live coding, practise solving problems out loud with a timer. For system design, practise drawing and explaining a few common systems from end to end.
Similar tests exist outside coding. A designer may be asked to walk through past work or do a short design task. An analyst may get a set of data and an hour to find something in it. A writer may get an editing test. The rule is the same: show your thinking as well as your answer.
The common mistake is going quiet when stuck. Silence tells the interviewer nothing. Say what you have tried, what you think the problem is, and what you would try next. Interviewers often give hints to people who talk, and they can only judge what they can hear.
Worked example
Two candidates, one problem
Two candidates get the same live coding problem. One works in silence for 40 minutes and gets the right answer. The other talks through each step and misses one edge case.
The second one gets the offer. The interviewers saw how she thinks, how she took a hint, and how she would work on a team.
The words for this lesson1
Check yourself
You get stuck halfway through a live coding problem. What should you do?
Finished this lesson?
Marking it complete also marks its 1 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.