The first 90 seconds of a tech interview

The interviewer is not scoring your life story. They are trying not to hire the wrong person, and they decide most of that in the first minute and a half. After that, confirmation bias does the rest: the call becomes a hunt for evidence that the first impression was right.

That is why the opening is not small talk you can throw away. It is the frame. A stiff, rehearsed start makes every later answer sound like damage control. A calm, specific start makes the same facts sound like proof.

This holds on calls with a hiring manager, a panel, or an exec. It does not save a wrong design on a whiteboard. There, the ninety seconds are irrelevant and the work on the screen is the whole test.

Small talk is a signal, not a topic

"How are you?" is a handshake. They are checking whether you are in the room. A robotic paragraph about being "excited for the opportunity" is the worst version, because it tells them you are reading. One human sentence is enough. Then let them lead.

Do not try to be memorable here. Trying too hard reads as nerves. Matching their energy does more: short if they are short, a beat longer if they are.

How to answer "tell me about yourself"

It is the first real question, and most people waste it walking the CV from university to now. That is a tour. They already have the file. They asked you to choose.

Three beats, in this order:

1. The problem you actually solve: one sentence, in their language, not your job title
2. One proof: a result with a number, the same kind of claim that survives on the CV. How you say it is result first
3. A bridge to this role: why that problem looks like theirs, then stop and let them pick it up

The line that dies in the first minute:

So I started as a junior in 2016, then I moved to a bigger company, I have worked with React and Node, I am passionate about clean architecture and I think I would be a great fit.

The line that survives:

I build the reporting layer so product teams stop waiting on engineers for every number. Last role I replaced a manual SQL pipeline and cut reporting from days to hours. Your posting is asking for the same self-serve setup, so I would start there.

Same career. The second one gives them a thread they can pull. The first one asks them to find one.

Keep it under a minute. If you need a second example, wait until they ask. Two stories in the opener is a person who does not know which one matters.

What the first minute is for

You are not trying to cover the stack. You are trying to lower the risk of hiring you before they have a reason to doubt. A number they can test does that. A list of tools does not. A recap of the About page does not. "I saw you value ownership" is a tell that you spent five minutes on the site.

If they interrupt, let them. An interruption in the first minute is usually them grabbing the thread you wanted them to grab.

Where this does not apply: a structured screen that starts with a coding task, a take-home walkthrough, a system-design prompt with no intro. There is no opening to win. There is only the work.

A short checklist before the call

• You have one sentence for the problem you solve, not a title dump.
• You have one result with a number you can defend on a follow-up.
• You can name, in their words, why that problem looks like this vacancy.
• Small talk is a sentence, not a speech.
• You can stop talking and let them take the thread.
• You know this will not save a live coding round. It does not have to.

The CV's job was to get the call. The first ninety seconds decide whether the rest of it is a conversation or a recovery.