How to introduce yourself in an interview

"Tell me about yourself" is not small talk. It is the question the rest of the interview is built on: whatever you put in those ninety seconds is what the panel will ask you about for the next half hour. Candidates who understand that steer the interview. Candidates who do not, recite a CV the panel has already read and then answer questions about whatever the panel found interesting instead.

What the recruiter is actually doing

Three things, all at once. They are checking whether you can organise a thought under mild pressure. They are looking for the two or three threads they will pull on later. And they are forming the impression that every subsequent answer gets measured against — which is unfair, and real.

None of those are helped by chronology. Starting at secondary school and walking forward spends your best seconds on your least relevant material.

The structure

Now. Then. Why here. In that order.

Now — one sentence on what you do and what you are good at. Not your job title; the thing you are actually known for. "I am a final-year computer engineering student, and most of what I have built is back-end — APIs, databases, the parts nobody sees."

Then — two or three sentences on the path that got you there, chosen for this job. This is the part that changes between applications. Pick the projects, the internship, the responsibility that this employer would care about, and leave out the rest. Give one result with a number in it if you have one.

Why here — one or two sentences connecting that to this role. Specific enough that it could not be said to another company.

Ninety seconds. Roughly two hundred words. It is shorter than most people expect, and that is the point: you are opening doors, not walking through them.

What to leave out

Your date of birth, your marital status, the town you grew up in, and your full education history. If they matter, they are on your CV and the panel will ask. Every sentence spent on them is a sentence not spent on the work.

Also leave out the adjectives. "Motivated", "dynamic", "hard-working", "passionate" — every candidate uses them, so they carry no information at all. Replace each one with the thing that would make someone else say it about you.

The version that fails

"So, I was born in Sfax, I did my baccalaureate in 2021, then I started at the university where I studied computer science for three years, and I really enjoyed it. I am a very motivated person and I learn quickly. I like working in a team. And now I am looking for an opportunity."

Nothing in that is false. Nothing in it is usable either. There is no thread for the panel to pull, no evidence for any claim, and no reason it was said to this company rather than any other.

The version that works

"I am a final-year computer engineering student, and most of my work is back-end — I am the person on a team who ends up owning the database. Last year I built the booking system for a small clinic, about two thousand appointments a month, and cut their no-shows by a third with automated reminders. I have been following what you are doing with payments infrastructure in Tunisia, and back-end at that scale is exactly where I want to spend the next few years."

Same length. Three threads the panel can pull — the clinic project, the no-show number, the interest in payments — and every claim has evidence behind it.

Practise it out loud, once

Not twenty times. An introduction rehearsed to the word sounds rehearsed to the word, and recruiters discount it. Say it aloud two or three times until the order is automatic and the sentences are still yours.

The useful test is hearing yourself. Talk2Hire records the session and gives you the transcript, so you can check what you actually said against what you meant to say — usually a longer, vaguer, more adjective-heavy version of it. Fixing that gap once is worth more than another read-through.

Then read the ten questions that follow it.