See what's new

Testlify
HR & recruitment
Last updated on: 18 November 202611 min read

What is a technical interview? Formats, questions and how to run one

A technical interview checks if a candidate can do the job's core work. Learn the formats, question types, stages and a fair scoring rubric.

What is a technical interview? Formats, questions and how to run one

A technical interview is a job interview that tests whether a candidate has the specific skills and knowledge a role needs. Instead of only talking about past experience, the candidate solves a problem, explains a decision or completes a task while the interviewer watches how they think.

TL;DR / Key Takeaways

  • A technical interview checks if a candidate can do the core work of the role, through live tasks, technical questions and problem-solving, not just conversation.
  • A technical question asks about the tools, methods or problems of the job, such as "How would you find the cause of this slow database query?"
  • Common formats are the technical phone screen, live coding, take-home tasks, system design, debugging and case exercises for non-tech roles.
  • Most live technical rounds last 45 to 90 minutes. Take-home tasks should stay under 4 hours with a 30 to 45 minute debrief.
  • LinkedIn found 93% of talent acquisition pros say accurately assessing skills is crucial to quality of hire.
  • Fair technical interviews use the same questions, a written 1 to 5 rubric and independent scores before the debrief.
  • Decide your AI policy per round: 84% of developers use or plan to use AI tools, so say which rounds allow them and check the rest.
Summarise this post with:ChatGPTGeminiClaudeGrokPerplexity

What is a technical interview?

A technical interview is a structured round in the hiring process where a candidate shows the job-specific skills a role needs, usually by solving a problem, completing a task or answering technical questions about tools and methods. The interviewer scores both the answer and the reasoning behind it.

Technical interviews are most common for software, data, IT and engineering roles, where they often include coding or system design. They are not limited to tech jobs. A financial analyst may build a model, a marketer may audit a campaign, and a support agent may troubleshoot a customer issue from a log.

The round sits after the first screen and before the final decision. Many teams run a short technical screening step or an online skills test first, then use the live technical interview to go deeper with a smaller group.

Build your dream team — Book a product demo

What is a technical question in an interview?

A technical question in an interview is a question about the tools, methods, processes or problems of a specific job, asked to check whether the candidate can apply that knowledge. Technical questions, meaning job-specific questions rather than general ones about motivation or values, are the core of any technical round.

So what is a technical interview question in practice? It usually falls into one of five types:

Question type

What it checks

Example for a tech role

Example for a non-tech role

Tools

Hands-on knowledge of software and systems

Which version control workflow have you used on a team?

Which CRM reports do you build each week?

Process

How the candidate approaches work

How do you test a change before it goes live?

How do you close the books at month end?

Problem-solving

Reasoning on a fresh problem

How would you find the cause of a slow database query?

Sales fell 20% in one region. Where do you look first?

Situational

Judgment in a realistic scenario

A release breaks checkout at 6pm. What do you do?

A key supplier misses a delivery. What is your plan?

Knowledge

Concepts the role needs from day one

What is the difference between RAM and ROM?

What is the difference between gross and net margin?

For ready-made sets by skill, see these technical interview questions to assess problem-solving skills.

Technical interview vs HR interview: what each round checks

Why do companies use technical interviews?

Companies use technical interviews because a resume and a friendly conversation cannot show whether someone can do the work. A technical round turns claims like "advanced SQL" into evidence the whole hiring team can see and compare.

Hiring leaders agree that this evidence matters. LinkedIn's Future of Recruiting 2025 found that 93% of talent acquisition professionals say accurately assessing a candidate's skills is crucial to improving quality of hire. The same report found that companies running the most skills-based searches are 12% more likely to make a quality hire, and 89% of TA pros expect measuring quality of hire to matter more.

Technical interviews help hiring teams to:

  • Confirm real skill: Separate people who can do the work from people who can only describe it.
  • Compare fairly: Give every candidate the same task and the same scoring, so decisions rest on evidence.
  • Spot training needs: See which gaps a new hire would need help with in the first 90 days.
  • Show the job: Give candidates a realistic preview of the problems they would solve.

For a large-scale example of the technical interview meaning in practice, see how Amazon puts an online assessment before its phone screen and structured interview loop.

What are the main technical interview formats?

Technical interview formats range from a short phone screen to a half-day project, and the right one depends on the role and seniority. Most hiring teams combine two or three formats so that no single round decides the outcome.

Format

Best for

Typical length

Watch out for

Technical phone screen

Removing clear mismatches early

15 to 30 min

Hard questions here cause false rejections

Online skills test

Shortlisting large applicant pools

30 to 60 min

Needs proctoring to trust the scores

Live coding or pair programming

Engineers, data roles

45 to 90 min

Stress can hide skill; let candidates talk it through

Take-home task

Realistic project work

2 to 4 hours

Unpaid time; always add a debrief call

System design

Senior engineers, architects

45 to 60 min

No single right answer; score the trade-offs

Debugging exercise

Support, QA, backend roles

30 to 60 min

Prep the codebase or logs in advance

Case or work sample

Finance, marketing, operations

45 to 90 min

Keep the task close to real work

Pro tip: Match the format to the work. A support engineer is better tested on a log file than on an algorithm puzzle, and a senior engineer on design choices more than on syntax.

What happens in a technical interview?

A technical interview usually follows five stages: a short screen, a skills assessment, a live technical round, a deeper discussion of design or past work, and a scored decision. Each stage narrows the pool and adds evidence for the next one.

What happens in a technical interview, from screen to decision
  1. Screen: A recruiter or engineer checks the basics, such as core tools and years of hands-on work.
  2. Assess: Candidates take an online test or short coding task, so only people with the core skills move on.
  3. Live round: The candidate solves a problem in front of the interviewer and explains each step out loud.
  4. Deep dive: The interviewer asks about design choices, trade-offs and real projects the candidate has shipped.
  5. Decide: Each interviewer scores alone, then the team meets for a short debrief and makes the call.

Candidates often ask whether the technical interview is the final interview. The answer depends on the company: some end with it, while others add a hiring manager or HR conversation after it.

Which roles need a technical interview?

Any role where a specific skill decides success on day one needs a technical interview. Software engineers, data analysts, DevOps engineers, IT support, QA testers and cybersecurity analysts almost always get one.

Non-tech roles benefit too. Accountants can reconcile a sample ledger, marketers can review a live campaign, and customer support agents can answer a tricky ticket. The rule is the same: test what the person will do in the first month, not trivia.

How do you conduct a technical interview?

A technical interview is conducted best when the questions, task and scoring rubric are fixed before the first candidate arrives. That structure is what makes scores comparable across candidates and interviewers.

The US Office of Personnel Management notes that structured interviews use rules for asking, observing and scoring answers, which cuts interviewer discretion and improves agreement between interviewers. Follow these steps:

  1. List the must-have skills: Start from the job description and pick the 3 to 5 skills the role cannot do without.
  2. Pick one format per skill: Use a live task for hands-on skills and a discussion for design judgment.
  3. Write the rubric first: Describe what a 1, 3 and 5 answer looks like for every question.
  4. Brief the panel: Tell interviewers which skill each person owns, so no one repeats questions.
  5. Tell candidates the format: Share the length, tools and AI rules in advance so nerves do not hide skill.
  6. Score alone, then debrief: Each interviewer submits scores before the group meets.
Technical interview scoring rubric with a 1 to 5 scale

For the wider method, see the structured interview glossary entry.

Key takeaway: Decide what good looks like before you meet anyone. A rubric written after the interview tends to describe the candidate you already liked.

How is AI changing technical interviews?

AI is changing technical interviews because candidates now use AI tools at work every day, which forces hiring teams to decide what each round should measure. The Stack Overflow 2025 Developer Survey found that 84% of respondents use or plan to use AI tools in their development work, and 51% of professional developers use them daily.

That changes the round design in three ways:

  • Set an AI policy per round: Many teams keep the live round AI-free and allow AI in take-home tasks, then ask candidates to explain every line.
  • Test AI judgment: The same survey found that 46% of developers distrust the accuracy of AI output. Ask candidates to review and fix AI-written code to see how they catch errors.
  • Check integrity: For online rounds, use proctoring such as tab tracking, copy and paste blocking and AI-assistance detection, so scores reflect the candidate's own work.

What mistakes should hiring teams avoid in technical interviews?

Hiring teams most often go wrong by testing puzzles instead of the job, letting each interviewer improvise, and skipping the scoring rubric. Each of these makes scores hard to compare and pushes good candidates away.

  • Puzzles over real work: Brain teasers measure puzzle practice, not job performance.
  • Unstructured rounds: Different questions for each candidate make fair comparison impossible.
  • Hostile pressure: Interrupting or rushing candidates tests nerves, not skill.
  • Take-homes with no debrief: Without a follow-up call you cannot confirm who did the work.
  • Too many rounds: Each extra stage adds days, and strong candidates often accept other offers first.

How does Testlify support technical interviews?

Testlify supports technical interviews by handling the skills test before the live round and adding structure to the interview itself, so engineers spend their time only on candidates who already showed the core skills.

  • Skills tests first: Choose from 3,500+ tests, including coding tests with a live coding environment in 45+ programming languages, or build a custom assessment from a job description with the AI test builder.
  • Live and AI interviews: Run live coding and pair-programming interviews, or two-way AI interviews by video, voice or chat, with 25+ question types.
  • Integrity checks: 20+ proctoring checks, including AI-assistance detection and copy and paste blocking. See anti-cheating and proctoring.
  • Fits your stack: Results sync to 100+ ATS and HRIS tools, including Greenhouse, Lever and Workday.

For how assessments and interviews work together, read what technical assessments are and why they matter.

Ready to run better technical interviews?

Start with a skills test that matches the role, then spend live interview time only on candidates who passed it. Browse the Testlify test library or start a 7-day free trial, no credit card needed.

Frequently asked questions

Yash Patel
Yash Patel

Wordpress Developer

Yash Patel is a Wordpress and SEO Specialist at Testlify with 3+ years of experience in technical SEO, on-page optimization, and content strategy. He works on improving Testlify's organic presence and produces content focused on hiring, talent assessment, and HR technology.

LinkedIn

Get started.

Hire on proof, not resumes.

Run your first skills-based assessment free — no credit card required.

We use cookies to enhance your browsing experience, serve personalised ads or content, and analyse our traffic. By clicking "Accept All", you consent to our use of cookies.