A technical interview is a job interview that tests the specialist skills a role needs by having you solve problems, not just describe your experience. In software it usually means coding and system design; in other fields it can mean calculations, case questions, design reviews or troubleshooting. Interviewers usually assess both your answer and how you reason.
Technical interviews usually come after a recruiter screen or an online assessment, and a hiring process often includes several of them, each covering a different skill. Most also include a few behavioral questions.
Types of technical interview
| Format | What you do | Common in | What's assessed |
|---|---|---|---|
| Coding interview | Solve one or two problems in a shared code editor or on a whiteboard while explaining your thinking | Software, data and machine learning roles | Problem solving, correct code, complexity, communication |
| System design | Sketch the architecture of a large system and discuss trade-offs | Mid-level and senior software roles | Scalability, reliability, trade-off reasoning |
| Technical deep dive | Answer questions on your field's fundamentals, such as SQL, statistics, networking or circuit analysis | Most technical roles | Depth and accuracy of knowledge |
| Take-home assignment | Build or analyze something on your own time, then discuss it | Software, data and design roles | Quality, judgment, how you explain decisions |
| Technical phone screen | A shorter first round, often one problem | Software roles | Baseline skill before longer rounds |
| Hands-on or practical test | Debug, troubleshoot or complete a lab or tool task | IT, DevOps, hardware and engineering roles | Practical skill in realistic conditions |
| Project review | Walk through your past work in depth | Senior and specialist roles | Ownership, depth, decisions |
Some companies publish what their rounds look like. Amazon's SDE II interview prep page describes a loop of four 55-minute interviews, tells candidates to expect at least one software system design question, and asks for syntactically correct code with "no pseudo code" (as of October 2026). Its prep page for university technical roles says Quality Assurance Engineer interviews may combine verbal and coding exercises, in interviews of about 45 to 60 minutes each. For the shorter first round, see our technical phone screen guide; for take-homes, see what reviewers look for in a take-home assignment.
How a technical interview works
A typical coding round follows this order, though every company runs its own variation:
- Introductions. A minute or two about you and the interviewer.
- The problem. The interviewer states a task, sometimes deliberately vague.
- Clarify. You ask about inputs, edge cases and constraints, and confirm an example.
- Plan. You describe an approach and its time and space complexity before writing code.
- Code. You write working code while narrating your choices.
- Test. You walk through examples and edge cases and fix any bugs.
- Extend. The interviewer adds a constraint or asks how you would optimize.
- Your questions. A few minutes at the end for you to ask about the team and the work.
System design rounds follow a similar arc: requirements, rough estimates, a high-level design, then deeper dives into the parts the interviewer cares about. See what a system design interview is for the full picture.
Example: a short coding exchange
Example exchange written by us for illustration.
- Interviewer: "Given a list of meetings as start and end times, can one person attend all of them?"
- Candidate: "Can a meeting start exactly when the previous one ends? And can the list be empty?"
- Interviewer: "Back-to-back is fine. An empty list means yes."
- Candidate: "Then I'll sort by start time and compare each meeting with the one before it. If a start is earlier than the previous end, there's a conflict. Sorting makes it O(n log n) time; the check itself is a single pass."
- Candidate, after coding: "Let me test it. An empty list returns true,
[[1,3],[3,5]]returns true, and[[1,4],[2,3]]returns false."
The interviewer is scoring more than the final code: the clarifying questions, the complexity stated up front and the tests run without being asked.
Technical interview vs behavioral interview
| Technical interview | Behavioral interview | |
|---|---|---|
| Focus | What you can do now | How you have acted in the past |
| Typical prompt | "Design a rate limiter" or "Write a function that…" | "Tell me about a time you disagreed with a teammate" |
| Evidence | Your working solution and your reasoning | Specific stories with results |
| Structure that helps | Clarify, plan, build, test | The STAR method |
| How to practice | Timed problems and mock rounds | A story bank rehearsed out loud |
Most hiring processes include both. See what a behavioral interview is and what the STAR method is for the other half, and our AI interview glossary for related terms.
How to prepare for a technical interview
- Start from the job description. The skills it names are the best guide to what you'll be asked. Ask the recruiter for the format of each round and which languages you can use.
- Practice by pattern, not by volume. The coding interview cheat sheet maps problem wording to core patterns, and the Big-O complexity visualizer helps you state complexity with confidence. For a schedule, see how to prepare for a coding interview in two weeks.
- Review system design if you're mid-level or above. The system design cheat sheet covers capacity estimates, latency numbers and core components.
- Practice talking while you solve. Mock rounds out loud matter more than silent practice. CoPilot Interview's Mock Interview lets you choose the mix (behavioral, technical, system design, coding) and your coding language, reads each question aloud, scores each answer out of 10 with what to fix and a model answer, and never auto-submits coding questions, so you can think in silence. Start with the free AI mock interview, which also has a browser version with nothing to install.
- Rehearse the remote setup. If the round is on Zoom, Microsoft Teams or Google Meet, test your editor, audio and camera first; our coding interview tips for Zoom and Teams cover the details.
- Prepare your questions. Have two or three ready from our list of questions to ask at the end of a technical interview.
CoPilot Interview also makes a coding interview copilot. If you consider any AI tool for a real round, follow the rules of the employer or assessment you're in — many people use it only to practice, which works on the free plan. CoPilot Interview is not affiliated with Microsoft Copilot or GitHub Copilot.
Common technical interview mistakes
- Coding in silence. The interviewer can't give credit for reasoning they can't hear.
- Coding before clarifying. Solving the wrong problem quickly is still the wrong problem.
- Skipping tests. Walk through at least one normal case and one edge case before you say you're done.
- Not stating complexity. Give the time and space cost of your approach without being asked.
- Designing without requirements. In system design, agree on scale and features before drawing boxes.
- Bluffing. If you don't know a fact, say so and explain how you would find out or reason toward it.
- Ignoring the behavioral part. A strong solution with weak collaboration signals can still cost you the offer.
Rehearse a technical round out loud
CoPilot Interview's free AI mock interview asks coding, system design and behavioral questions from your résumé and a job description, and scores each answer out of 10 with what to fix and a model answer. 15 minutes a day free, no credit card.
Try a free AI mock interviewFAQ
What happens in a technical interview?
You solve problems related to the job while an interviewer watches and asks questions. In software that usually means writing code or designing a system; in other fields it can mean calculations, troubleshooting or questions on fundamentals. Your reasoning counts alongside the answer.
How long is a technical interview?
Each round commonly runs 45 to 60 minutes, and a full process can include several rounds. Amazon, for example, lists four 55-minute interviews in its SDE II interview loop. Ask your recruiter for your own schedule.
Do non-software jobs have technical interviews?
Yes. Data analysts may get SQL or statistics questions, engineers may get calculations or design reviews, IT staff may get troubleshooting scenarios, and investment banking candidates are often asked accounting and valuation questions. Any role built on specialist skills can include one.
Can I use pseudocode in a coding interview?
It depends on the company. Some accept pseudocode while you plan, but many expect real, runnable code. Amazon's SDE II prep page asks for syntactically correct code rather than pseudocode. Ask the recruiter which languages are allowed.
What is the difference between a technical interview and a technical phone screen?
A technical phone screen is a shorter, earlier round, often a single problem, used to decide whether you move on. Later technical interviews go deeper and may add system design or domain questions.