# Coding interviews: what to do in the first five minutes

> Most coding interviews are decided before the first line of code. Restate the problem, ask about the inputs, work one example by hand, and say the simple solution first.

Source: https://hintvo.com/blog/coding-interview-first-five-minutes | Last updated: November 20, 2026 | Reviewed: 2026-11-20

Most coding interviews are decided before the first line of code is written. Spend the first five minutes making sure you are solving the right problem: restate it, ask about the inputs, work one example by hand, and say the simple solution out loud before the clever one.

## Minute one: say the problem back

Restate the problem in your own words and wait for a yes. It feels slow. It is the cheapest way to find out you misread the question, and interviewers count it in your favor.

## Minute two: ask about the inputs

- How large can the input get?
- Can it be empty? Can it contain duplicates or negative numbers?
- Is it sorted? Does the order of the output matter?
- What should happen with invalid input?

## Minute three: one example by hand

Take a small input and walk through it step by step, out loud. You will usually notice the pattern you need while doing it. If the interviewer gave an example, make a second one of your own with an awkward case in it.

## Minutes four and five: the simple solution first

Say the brute-force approach and what it costs in time and memory, even if you already see something better. It proves you have a working answer, and it gives you a baseline to improve. Then say what you would change and why.

## While you write

- Keep talking. Silence looks the same whether you are stuck or thinking.
- Name your variables properly. It is free and it reads as care.
- When you finish, run your example through the code line by line before saying you are done.

## When you are stuck

Say what you are weighing: "A map would make lookups fast, but then I lose the order. Let me think about whether I need the order." That sentence often gets you a hint, and a hint taken well is not a failure.

> **Where Hintvo fits:** when a coding question is on a shared screen, Hintvo reads it from the screen and suggests the approach, the trade-offs and the code. In practice interviews you can ask for a hint, the approach or the full solution. Use Hintvo only where AI help is allowed. Check the rules of your company, school or interviewer first, and respect a no. See [the interview copilot](https://hintvo.com/interview-copilot).

## Related

- [AI interview copilot that answers from your CV](https://hintvo.com/interview-copilot.md): How does Hintvo AI help in a job interview, and how do I practice with it?
- [System design interviews: a structure that holds when you are nervous](https://hintvo.com/blog/system-design-interview-structure.md): How do I structure a system design interview?
- [Is AI allowed in your interview? How to find out, and what to do either way](https://hintvo.com/blog/is-ai-allowed-in-your-interview.md): How do I find out whether AI tools are allowed in my job interview?
