Answering "tell me about yourself"

What's really being asked

Not your biography. They're asking: why are you here, what can you do, and is the next hour worth spending on you.

It's the opening question of almost every interview and it sets the tone. A good answer steers the conversation your way — what follows are questions about what you yourself raised.

A two-minute template

1. Who you are now, one sentence. "Junior developer, I've been writing Python for about a year."

2. Where you came from, briefly. If you changed careers, one line, not a life story. "I worked in logistics, wrote scripts for reports, got drawn in and decided to switch."

3. What you built with your hands. The main part. One or two projects: what, why, your role. Mention team work here if there was any.

4. What you can do. Three or four technologies, not a list of twenty.

5. Why you're here. Tie it to their posting: "your requirements are the same things I've worked with, which is why I applied".

Two minutes. Then stop and let them ask.

An example

Junior developer, writing Python for about a year. I came from a neighbouring field: I worked as an analyst, started automating my own reports, enjoyed it, and moved into development properly.

The most recent thing I built is an expense tracker working from photos of receipts: file intake, reading the amount, monthly reports. Built entirely by me, deployed, I can show you the link.

Before that, a team project with three of us. I owned the database and part of the logic, and that's where I first ran into reviewing other people's code.

I'm solid with Python, FastAPI and PostgreSQL. Your posting lists the same set, which is why I wrote.

Common mistakes

• A biography from childhood. Nobody is interested.
• Retelling the CV. It's already been read.
• A list of qualities. "Responsible, quick-learning, stress-resistant" is noise.
• A ten-minute monologue. After three minutes they stop listening.
• Too short. "Well, I learned Python and I'm looking for work" gives nothing to grab onto.
• Apologising. "I don't have experience yet but I try hard" puts you in a weak position immediately.

How to prepare

Say it out loud and time it. Out loud, not in your head. Almost everyone's first attempt is either forty seconds or six minutes.

Trim to two and repeat three or four times. Don't memorise word for word; you need the frame — five points in the right order.

What to mention without fail

Working with other people, if you have. Most beginners don't, and mentioning it almost always prompts the next question — which means the conversation moves onto your ground.

Better still if someone other than you can describe your part: with a confirmation from the person you worked with, "and what exactly did you do" stops being an awkward question.