What is a technical interview? Round types, scoring and how to prepare

A technical interview is a job interview where you show you can do the engineering work by doing some of it in front of someone. You write code, design a system, walk through a past project or explain how you handled a hard situation, and the interviewer scores how you think as well as what you produce. Most hiring processes chain several of these rounds into a loop.

What is a technical interview?

A general interview asks about your experience. A technical interview samples it. Instead of telling the interviewer you can debug a slow query, you get a slow query. Instead of saying you have designed services at scale, you sketch one on a shared canvas while they push on your choices.

The output matters, but less than most candidates expect. Two people can reach the same working solution and get different scores, because one clarified the problem, tested the code and explained trade-offs while the other went quiet and typed. The interviewer is trying to predict what working with you on a real problem would be like.

Technical interviews are standard for software engineers, and similar formats are used for data, machine learning, infrastructure and security roles. They happen on video calls, in shared editors and on whiteboards, and the same handful of round types shows up in most of them.

The six round types and what each one scores

Not every process uses all six, and the names vary. These are the formats you are most likely to meet.

Phone screen

The first technical conversation, usually 30 to 60 minutes on a call. It may be a recruiter checking background and logistics, or an engineer asking a short coding problem or a few knowledge questions. It scores basic fluency: can you write working code in your language, explain your own resume, and communicate well enough to be worth a longer loop?

Prepare by solving easy and medium problems out loud in a plain editor, rehearsing a two-minute summary of your background, and knowing every project on your resume well enough to take a follow-up. Phone screen interview questions lists what tends to come up.

Live coding

You solve one or two algorithm or practical coding problems in a shared editor while the interviewer watches, typically in 45 to 60 minutes. It scores problem solving, correctness, code quality, testing and communication. Many interviewers care as much about how you reach the solution as whether you finish, so narrating your approach and taking hints both count.

Prepare by learning the recurring patterns rather than memorizing problems, and by practicing with a timer while you talk. Live coding mock: narrate under a timer has a loop for the talking part, and coding interview patterns covers the patterns. Some processes put a timed online assessment before this round. If an assessment is proctored, follow its rules. Online coding assessment prep covers that format.

Take-home assignment

A small project you build on your own time, usually with a suggested limit of a few hours, often followed by a review call. It scores how you work when nobody is watching: scoping, structure, tests, documentation and the trade-offs you write down. The review call scores whether you can explain and defend what you built.

Prepare by time-boxing, writing a clear README, and rereading your own code before the call. Take-home assignment interviews goes through scoping and the review in detail.

System design

An open prompt such as "design a chat service", usually 45 to 60 minutes, and more common for mid-level and senior roles. It scores how you gather requirements, estimate scale, choose components and reason about trade-offs and failures. There is no single correct diagram.

Prepare by learning the building blocks (caches, queues, databases, load balancers) and running full designs aloud against a clock. Start with system design interview questions, then go deep on one block with caching in system design interviews.

Project or experience deep dive

The interviewer picks a project from your resume and keeps asking why. Why that architecture, what broke, what you would change, which part was yours and which was the team's. It scores depth, ownership and honesty, and it quickly exposes resume lines you cannot back up.

Prepare one or two projects in detail: the problem, the constraints, the design, a real failure and the result. Project walkthrough interview prep has a structure for the story.

Behavioral

Questions about how you work with people: conflict, failure, disagreement, ownership, a tight deadline. It scores judgment, collaboration and self-awareness, and in many processes it carries real weight in the final decision rather than being a formality.

Prepare six to eight true stories that each cover a few common themes, and practice saying each one in about two minutes. Behavioral interview questions with answers has examples, and the STAR method that does not sound rehearsed helps with delivery.

How a typical technical interview loop is sequenced

Processes differ by company, team and level, so treat this as a common shape, not a rule. Ask your recruiter for the actual sequence. Most will tell you the round types and their length.

1. Recruiter call. Background, role fit, logistics and sometimes salary expectations. Little or no technical content.
2. Technical screen. A phone screen with a coding problem, an online assessment or a take-home. This is the main filter before the full loop.
3. The interview loop. Several rounds, often three to five, on one day or spread over a week. A common mix is one or two coding rounds, a system design round for experienced roles, a project deep dive and a behavioral round.
4. Debrief. Interviewers compare written feedback. Many companies decide on the whole loop rather than a single round, so one weak round does not always end your chances.
5. Offer or team match. Some companies match you to a team after the loop, which can add one more conversation.

What interviewers look for in every round

The format changes but the signals overlap. Across rounds, interviewers usually write feedback on some version of these:

• Clarification. Do you ask about inputs, constraints and goals before you start?
• Structure. Can you break a vague problem into steps and say the plan before you execute it?
• Communication. Can the interviewer follow your thinking without having to ask?
• Correctness. Does the code run, does the design handle the stated load, is the story accurate?
• Trade-offs. Do you name what each choice costs, or present it as free?
• Response to hints. When the interviewer nudges you, do you take the hint and adjust?

Only one of those is about the final answer. That is why practice that only checks whether you got the solution leaves gaps.

Example: how to open a live coding question

Here is an invented example of the first two minutes of a coding round. The problem: given a string, return the index of the first character that does not repeat, or -1 if there is none.

Example: "Let me check the inputs first. Can the string be empty, and is it only lowercase letters or any characters? OK, any characters, possibly empty. The obvious approach compares each character with every other one, which is O(n squared). Better: one pass to count characters in a hash map, then a second pass to find the first one with a count of one. That is O(n) time and O(k) space, where k is the number of distinct characters. I'll write that, then test an empty string, a string where everything repeats, and 'swiss', where the answer should be index 1."

Nothing in that opening is clever. It clarifies, states a baseline, improves it, gives the complexity and plans the tests before writing code. That shape works for most coding problems, and it gives the interviewer something to score even if you run out of time.

How to prepare for each round

If your loop is a few weeks away, split your time by what the loop contains rather than evenly. A two-week technical interview preparation plan lays out a day-by-day version.

• Phone screen: easy and medium problems aloud in a plain editor, plus a two-minute background summary.
• Live coding: one pattern a day, two timed problems while narrating, and a short review of where you got stuck.
• Take-home: a dry run on a sample assignment with a strict time box and a README.
• System design: one full design a week aloud in 45 minutes, plus short sessions on single building blocks.
• Project deep dive: a written outline of one or two projects, and five hard follow-up questions you answer out loud.
• Behavioral: six to eight stories, each said aloud in about two minutes and mapped to common themes.

Whatever the round, say your answers out loud. Reading solutions builds recognition. Speaking under a clock builds the skill the interview actually measures.

Common mistakes

1. Preparing only for coding. Many loops include design, project and behavioral rounds that weigh as much. Find out what is in yours.
2. Going silent. Long silences leave the interviewer nothing to score. Think aloud, even when you are unsure.
3. Skipping clarification. Jumping straight into code or boxes means solving the wrong problem with confidence.
4. Memorizing answers. Memorized solutions and stories crack at the first follow-up question. Learn the reasoning behind them.
5. Overclaiming on your resume. Every line is fair game in a deep dive. If you cannot talk about it for five minutes, reword it.
6. Treating behavioral as a formality. In many processes a weak behavioral round can outweigh a strong coding one.

A weekly practice loop

1. Map your loop. Write down the rounds in your actual process and how long each one is.
2. Pick the weakest round. Spend most of the week on it, not on the one you already enjoy.
3. Practice aloud with a timer. Match the real length of the round, and do not pause the clock.
4. Review one thing. After each session, write one sentence on what slowed you down.
5. Redo the weak part the next day. Repeat only that phase or story until it comes out smoothly.

Follow-up questions are where most rounds are decided, in every format. How to answer follow-up questions in interviews is worth a session of its own.

Practice each round on the matching HIDEA AI surface

HIDEA AI is a desktop app for macOS and Windows with four separate surfaces, and each one maps to part of a technical loop. You speak or type every answer yourself.

• Verbal: the phone screen conversation, the behavioral round and the talking part of a deep dive. Answers are grounded in your resume and the job description.
• Live coding: phone screen coding and live coding rounds. A response leads with a plain-English approach, then code in the language you picked, then time and space complexity.
• System design: design rounds. You get an overview, components, a rendered architecture diagram and trade-offs, which you then redraw in your own words.
• Project: deep dives and take-home review calls. It answers questions about your own code from a local folder you bind at setup.

Mock interviews, where the app asks the questions, listens and scores the round, are verbal-only, 20 or 30 minutes, and on Pro and Pro+. Fifteen session minutes a day is free, with no credit card. The Report tab scores each saved session so you can see which part to redo. See the interview copilot overview and the pricing page.

If you plan to use any tool during a live round, check the employer's rules first. What some employers publish shows how to read them.

Where to go next

• Plan the next two weeks: technical interview preparation plan.
• Start the design track: system design interview questions.
• Get ready for remote rounds: virtual interview tips.
• Set up the app: the setup guide, or download HIDEA AI.