For hiring managers

What is a technical interview? Formats, what each one tests, and how to run one fairly

On this page
  1. How does a technical interview work?
  2. What are the main technical interview formats?
  3. How is a technical interview different from other assessments?
  4. What should a technical interview measure, and what should it leave out?
  5. How should a technical interview be scored?
  6. What rules apply to technical interviews?
  7. Can candidates use AI tools in a technical interview?
  8. Who should run a technical interview?
  9. A copy-ready technical interview plan
  10. Questions people ask

A technical interview is a job interview in which the candidate solves or explains problems from the role's technical field, such as writing code, designing a system, diagnosing a fault or answering structured technical questions, while an interviewer who knows the field scores the work against criteria set in advance. It is most associated with software engineering, but IT, data, engineering, finance and skilled-trade roles use it too: the U.S. Office of Personnel Management offers off-the-shelf technical structured interviews for federal IT and HR specialist roles (as of November 2026). In U.S. employment law a technical interview is a selection procedure like any test, so what it measures should be job-related, and candidates with disabilities may need an adjusted format.

How does a technical interview work?

Hiring processes differ, but most technical hiring runs some version of this sequence: a recruiter screen that checks experience and logistics, a shorter technical screen, one or more technical rounds, and a debrief. A single technical round usually follows the same shape:

  1. Introduction. The interviewer explains the format, what tools are allowed and how the round will be scored.
  2. The problem. A task from the job, stated so a qualified person could start without guessing what is wanted.
  3. Clarifying questions. Good candidates ask about inputs, constraints and what "done" means; that is part of what is being assessed.
  4. The work. The candidate writes, draws or talks through a solution and explains their reasoning as they go.
  5. Follow-ups. The interviewer changes a constraint, asks about an edge case or asks why one approach was chosen over another.
  6. Candidate questions and close. Then each interviewer scores independently before the debrief.

OPM describes its own versions as "competency-based" interviews that use "standardized, job-relevant questions and scoring criteria" to evaluate an applicant's ability to apply technical knowledge "in real-world" scenarios (OPM hiring assessments, checked November 2026). That is a good working definition for any employer: the same problems for everyone at a level, and a scoring guide written before the first candidate.

What are the main technical interview formats?

FormatWhat the candidate doesWhat it shows bestWatch out for
Live codingWrites working code in a shared editor while talking it throughProblem solving, code fluency, testing habitsPuzzles unrelated to the job; scoring speed when the job does not need it
System designSketches the architecture for a service or product and defends trade-offsDesign judgment, scale and reliability thinking; mostly for mid-level and senior rolesNo shared rubric, so scores track the interviewer's favorite design
Take-home plus walkthroughCompletes a task on their own time, then explains and changes it liveRealistic work without time pressureUnpaid scope creep and authorship questions; see evaluating a take-home
Pair programmingWorks on a problem with the interviewer as a collaboratorHow the person works with others, takes hints and explainsInterviewer steering too much, so the score reflects the interviewer
Debugging or troubleshootingFinds and fixes a fault in code, a system or equipmentDiagnostic method, the most common real task in many rolesFaults that need one piece of insider knowledge to spot
Technical deep-diveExplains a past project in depth: decisions, failures, what they would changeDepth and honesty about their own partRewarding storytelling over substance; probe for specifics
Structured technical questionsAnswers set questions about concepts and scenarios, scored against model answersBreadth of knowledge; works for roles outside softwareTrivia that can be looked up on the job

Which formats fit depends on what the job actually requires; a support engineer's loop should lean on troubleshooting, a platform engineer's on design. The essential duties of the role are the place to start; see what is an essential job function.

How is a technical interview different from other assessments?

TermHow it worksHow it relates to a technical interview
Technical screenA shorter first technical conversation or testA filter before the full technical round
Skills assessmentA standardized test of specific skills, often taken alone and scored on the outputMeasures the result; the interview adds the reasoning. See what is a skills assessment
Work sample testA real task from the job, done and scoredMany technical rounds are live work samples; see what is a work sample test
Case interviewA business problem worked out loudThe business-side counterpart; see what is a case interview
Behavioral interviewQuestions about past behavior ("tell me about a time")Usually a separate round; a technical deep-dive borrows its probing style. See what is a behavioral interview

What should a technical interview measure, and what should it leave out?

Write the criteria from the job before choosing problems. Criteria that usually transfer across technical roles:

  • Understanding the problem: asks the questions that matter before starting.
  • Approach: picks a workable method and can say why.
  • Correctness and quality: the result works and is readable or maintainable by others.
  • Verification: tests, checks edge cases or explains how they would.
  • Trade-offs: knows what the chosen approach costs and when another would be better.
  • Communication of reasoning: a colleague could follow the thinking.

Leave out what the job does not need: memorized syntax the person would look up, speed under a stopwatch for work that is not timed, brain-teasers, and anything about how the person sounds or looks. Accent, fluency beyond what the job requires and confidence are not technical criteria, and scoring them invites national origin and disability claims.

How should a technical interview be scored?

  1. Use the same problem, or problems of the same difficulty, for everyone interviewing at the same level.
  2. Write anchors for each criterion before the first interview: what a low, middle and high score looks like for this problem. Behaviorally anchored rating scales explains the method, and the software engineer scorecard has a filled example.
  3. Record what the candidate did and said, not "strong" or "weak."
  4. Score independently before the debrief, then discuss the evidence.
  5. Calibrate interviewers by having them score the same recorded or written session and compare.

What rules apply to technical interviews?

  • It is a selection procedure. The Uniform Guidelines define selection procedures to include "performance tests" and even "informal or casual interviews" (29 CFR 1607.16(Q)). Title VII allows "professionally developed ability" tests that are not "designed, intended or used to discriminate," and a practice that screens out one group more than others must be "job related for the position in question and consistent with business necessity" (42 U.S.C. 2000e-2(h) and (k)). Where the Guidelines stand in November 2026 is on cognitive ability tests in hiring.
  • Accommodations. The ADA requires tests to be given so that results "accurately reflect the skills, aptitude, or whatever other factor" they measure rather than a sensory, manual or speaking impairment, "except where such skills are the factors that the test purports to measure" (42 U.S.C. 12112(b)(7)). The EEOC's guidance on 29 CFR 1630.11 names extra time as a possible accommodation unless speed is one of the skills tested. Steps are in ADA accommodations in interviews.
  • Records. Employers covered by Title VII and the ADA keep any personnel or employment record they make or keep, including "other records having to do with hiring," for at least one year (29 CFR 1602.14).
  • Recording and AI scoring. Recording a round needs the consent your state requires; see is it legal to record a job interview. Automated scoring of coding tests can fall under state and city AI hiring laws; see AI hiring laws by state.

Can candidates use AI tools in a technical interview?

That is the employer's decision, and the fair approach is to decide it per round and say so in the invitation: no AI, AI allowed for lookups, or AI allowed as a full tool with the candidate explaining every line. Rounds built around follow-ups (change a requirement, explain a choice, extend the solution) show understanding whatever tools are in use. Question design, live follow-ups and verified final rounds are covered in how to prevent cheating in technical interviews, and the tools candidates use are described in AI interview cheating tools explained.

Who should run a technical interview?

Someone who does or has done the work, trained on the rubric and shadowed before interviewing alone (see interviewer shadowing). Recruiters without the technical background run the screen before it, where they can still check claims and logistics; see interviewing for technical roles as a non-technical recruiter. Teams without enough interviewers can buy the round from a vendor; see interviewing as a service and technical interview platforms. We make Interview Signal, a desktop app that transcribes the interviewer's call without a bot joining; in a technical round it hears the conversation only, not the shared editor or screen, as described on Interview Signal for technical interviews.

A copy-ready technical interview plan

TECHNICAL INTERVIEW PLAN (example; one per round)
Role and level: ____________________  Round: ___ of ___
Interviewer(s): ___________________  Trained on rubric: [ ] yes
Format: [ ] live coding [ ] system design [ ] take-home walkthrough
        [ ] pair work [ ] debugging/troubleshooting
        [ ] technical deep-dive [ ] structured technical questions
Job duty this round tests: _________________________________
Problem (same for every candidate at this level): ___________
Allowed tools and AI rule (stated in the invitation): _______
Accommodation contact in the invitation: [ ] yes
Criteria and weights:
  Understanding the problem   ___%
  Approach                    ___%
  Correctness and quality     ___%
  Verification / edge cases   ___%
  Trade-offs                  ___%
  Communication of reasoning  ___%
Anchors written for 1 / 3 / 5: [ ] yes
Planned follow-ups: 1) ____________ 2) ____________
Not scored: speed (unless the job is timed), syntax recall,
accent, appearance, school or employer names.
Scores and evidence submitted before debrief by: __:__ on __/__

The plan is an example to adapt. Keep the filled plans with the hiring records, so that a question about why one candidate passed and another did not can be answered from what was written at the time.

Questions people ask

What happens in a technical interview?

An interviewer who knows the field gives the candidate a problem from the job, such as writing a function, designing a system, finding a fault or explaining how they would handle a technical scenario. The candidate asks clarifying questions, works through it while explaining their reasoning, and answers follow-up questions about trade-offs and edge cases. The interviewer scores the approach and the result against criteria set before the interview.

Are technical interviews only for software engineers?

No. Any job with a technical core can use one: IT support, data analysis, engineering, finance, laboratory work and skilled trades. The U.S. Office of Personnel Management, for example, offers off-the-shelf technical structured interviews for federal IT specialist and HR specialist roles, built on standardized questions and scoring criteria.

What is the difference between a technical interview and a coding test?

A coding test is usually completed alone and scored on the output, often automatically. A technical interview is a conversation with a qualified interviewer who can see how the candidate thinks, ask follow-up questions and judge trade-offs. Many hiring processes use both: a test or take-home to screen and a live technical interview to probe.

Can a non-technical recruiter run a technical interview?

A recruiter can run the screen before it, checking experience, logistics and claims, but the technical round itself should be scored by someone who knows the field, because the scoring depends on judging whether an approach is sound. Some employers outsource that round to interviewing-as-a-service vendors.

Do candidates get accommodations in technical interviews?

They can. The ADA requires tests to be given so that results reflect the skill being measured rather than a sensory, manual or speaking impairment, unless that skill is what the test measures. Common adjustments include extra time, a different editor or input method, written instead of spoken questions, and breaks. Tell candidates in the invitation how to ask.