Skip to content
DevFlash

Technical interview

Technical interview: what to expect and how to prepare

A roadmap from the first conversation to the closing questions, shaped around the role and interview format.

  • 5 min read
  • 5 sections
  • Updated November 2, 2026

This guide is under editorial review.

In 1 minute

  • Confirm format, duration and allowed resources; processes can vary across teams.
  • Prepare real experiences, distinguishing your contribution, constraints and observed results.
  • Practice tasks relevant to the role and turn interview questions into specific study work.

A technical interview explores how you solve software problems, sometimes through a practical task. It may involve previous projects, reading code, implementation or architecture decisions. There is no mandatory sequence shared by every role. Start by finding out which format to expect and what kind of evidence you will need at each stage.

Preparing for everything at once makes your study time unfocused. This roadmap turns a job description into a workable agenda: confirm the stages, select experience stories, practice relevant tasks and prepare questions. Use the technical question examples later to rehearse individual answers. The focus here is connecting the stages so that your preparation matches the conversation you will actually have.

How a technical interview works

Separate the format from the subject. A JavaScript discussion might use questions, a snippet to interpret or a live exercise. A take-home assignment requires a different approach because you also need to read instructions, run the project locally and submit it. Ask whether someone will observe the task and whether you will present your solution afterward. This clarifies preparation without asking for advance access to interview questions.

Keep the answers in a short note. If a stage has not been confirmed, record that uncertainty instead of filling the gap with someone else's experience. Processes can differ across teams. An initial conversation also helps you judge whether the role matches your current goals, desired responsibilities and available time for assignments outside working hours.

A funnel with progressively narrowing stages, ending in a sealed envelope glowing amber.
Confirm the stages and format of the specific process; the funnel is illustrative and does not promise acceptance.

Use the role as your preparation map

Read the description for concrete work: building interfaces, integrating APIs, investigating failures or maintaining an existing application. Match each responsibility with an experience and a gap in your knowledge. If interface work is central, prioritize browser fundamentals and the front-end interview roadmap. An optional tool should not consume your preparation time while the main responsibility still feels difficult.

Confirm the practical rules too. Documentation access changes how you rehearse, while the session length helps you select a suitable exercise. Do not infer permission to use tools from your current workplace habits. Recreate the stated conditions in a practice session and notice which questions come up before you write any code.

  • Confirm the duration, language, format and participants.
  • Ask about the editor, environment, documentation and permitted tools.
  • Record the submission deadline and how to report a problem.

Explain experience through evidence

Do

  • Choose two projects you can explain beyond their technology list. For each one, describe the problem, your responsibility, the main constraint and a decision you made.
  • Distinguish your contribution from the team’s work. If the outcome was not measured, describe observed behavior. A small delivery you understand gives the interviewer more to examine than a large system described only in broad terms.

Avoid

  • Inventing percentages for an outcome that was not measured.

Prepare a deeper layer for each story: a rejected alternative, a failure you found and something you would change today. This helps when follow-up questions move beyond your rehearsed introduction. For conflict, collaboration and responsibility, organize the facts with the behavioral interview guide. Personal and academic projects are useful evidence when you identify their actual context instead of presenting a simulation as paid work.

Plan for practical work and architecture

For practical preparation, choose a short task and write down the expected behavior before implementing it. Explain the inputs, output and an edge case. The example below is only a rehearsal of that contract: it adds already validated quantities. An empty cart produces zero; validating values received from a network would be a separate responsibility. Stating that boundary lets you discuss scope without building layers the task does not require.

If architecture is included, start with the user and the main workflow. Ask which data exists, which failures matter and what constraints have been stated. Sketch responsibilities before selecting tools. Set aside a separate rehearsal to explain alternatives and limitations. You do not need to turn every small exercise into a full system diagram, but you should recognize when the question shifts from implementation to the organization of a solution.

type CartLine = { quantity: number };
export function totalUnits(lines: readonly CartLine[]): number {
return lines.reduce((total, line) => total + line.quantity, 0);
}

How to review preparation and close the interview

Before the interview, review selectively. Open your environment, check access to the call and revisit your project notes. Avoid replacing your whole plan with a new topic discovered at the last minute. A short rehearsal reveals whether you can explain what you already know. The interview communication techniques help you shorten answers and ask for clarification without losing the thread.

  1. Close open points

    At the end, describe unfinished work precisely: separate what you verified from what remains a hypothesis.

  2. Ask about the role

    Ask about the role's responsibilities, code review and the next steps.

  3. Record and study

    Afterward, record questions while the context is still fresh. Turn one of them into a specific study task. This is more useful than deciding to relearn the entire stack because one question was difficult.

Frequently asked questions

What is a technical interview?

It is a stage for discussing development knowledge and decisions through concrete examples. It can include code, projects or architecture. Confirm the format and expected depth with the person organizing the process.

What are the stages of a technical interview?

Possible stages include an experience discussion, a practical task and a solution review, but there is no universal order. Ask for the planned sequence, duration and purpose of each meeting so your preparation fits the actual process.

How do I prepare for my first technical interview?

Start by understanding the role and selecting a project you can explain. Review its underlying concepts, practice a small task under the stated conditions and prepare questions. Describe academic or personal work honestly, including your own contribution.

What should I ask at the end of the interview?

Ask what problems the new hire will face, how work is reviewed and what happens next. Prefer questions that have not already been answered and that help you evaluate the role without requesting confidential information.

Practice with real tests

Solve front-end exercises in the browser, with the same tests a reviewer would run.

See the exercises