How to Answer "Tell Me About Yourself" in an English Interview

Almost every English-language job interview starts with the same line: "So, tell me about yourself." It sounds relaxed, but this is where many non-native speakers lose their footing. Not because they have nothing to say, but because they don't know where to start. They talk for too long, then lose the thread halfway through a sentence.

The good news is that this is the easiest question to prepare for. You know it's coming, and you already know the answer: your own work history. All you need is a structure and a few sentences you can say comfortably.

What the interviewer is really asking

When an interviewer says "tell me about yourself," they don't want to know where you grew up or what you did in high school. What they mean is closer to: "Tell me who you are professionally, and why you make sense for this job."

They use your answer for three things:

• The big picture. Are you a backend developer, a designer, a finance admin, a support specialist?
• The thread. Does your experience point toward this role?
• What to ask next. Whatever you mention here often becomes the next question.

That last point matters. Anything you say in your opening, expect to be asked about in more detail. So don't mention a project you can't explain.

The four-part structure: now, before, proof, why

If speaking English under pressure is hard for you, this structure is the safest choice. It's simple enough to remember even when you're nervous.

Part	What goes in it	Sentences
1. Now	Your current role and focus	1–2
2. Before	The experience that led you here	1–2
3. Proof	One concrete achievement or project	1–2
4. Why	Why this role makes sense for you	1–2

That's 6–8 sentences. If each one is short (about 12 words or fewer), you'll finish in 60–90 seconds. That's the right length: enough to give a clear picture, not so long that the interviewer starts waiting.

Sentence starters you can use

For the "now" part:

I'm a backend developer with four years of experience.

Right now, I work as a frontend developer at a logistics company.

I'm a freelance graphic designer. I mostly work with small businesses.

For the "before" part:

Before that, I worked in customer support for two years.

I started my career as a junior web developer.

For the "proof" part:

Last year, I built an inventory app used by three stores.

One project I'm proud of is a payment integration I led.

For the "why" part:

I'm applying because I want to work on products at a bigger scale.

This role fits what I enjoy most: building APIs that people rely on.

Full example answers

Here are three examples for different backgrounds. Notice that every sentence is short and free of idioms. The numbers and details are placeholders; use your own facts.

Developer with work experience

I'm a backend developer with four years of experience. I mostly work with Python and PostgreSQL. Before this, I was a junior developer at a small agency. There, I learned to ship fast and talk to clients. Last year, I rebuilt our order system. It now handles more orders without slowing down. I'm applying because I want to work on a product with real users. And I like that your team works remotely across time zones.

Recent graduate

I recently graduated in computer science. During college, I did a six-month internship as a web developer. I built internal tools with React and Node.js. My final project was a booking app for a local clinic. The clinic still uses it today. I'm looking for my first full-time role. I want a team where I can learn from senior engineers.

Career changer

I worked in accounting for three years. Two years ago, I started learning data analysis. I used it at work first, to automate monthly reports. That saved my team about two days each month. Since then, I've finished several projects with SQL and Python. Now I want to move fully into a data analyst role. This position combines both sides: finance and data.

If the job asks for something you haven't done, don't invent it. Be honest and point to what's closest:

I haven't worked with Kubernetes in production yet. But I've deployed apps with Docker, and I'm learning Kubernetes now.

We cover this "not yet, but something similar" pattern in more depth in how to explain your projects in English.

The most common mistakes

1. Reading your CV out loud. The interviewer already has your CV. Listing every job and every year makes the answer long and flat. Pick only what's relevant.

2. Starting from childhood or university. Unless you're a recent graduate, start with your current role. Going backward (now first, then the past) makes the answer feel relevant right away.

3. Going on too long. Many candidates talk for three or four minutes because they're afraid of leaving something out. This is only the opening. Details can come later.

4. Long, complicated sentences. A sentence like "I am a person who has been working in the field of software development for approximately four years in several companies which…" easily falls apart in the middle. Split it into two or three short ones.

5. Memorizing word for word. If you forget one word, the whole answer can freeze. Memorize the outline and the key points, not the script. Let the sentences change a little each time you practice.

6. Not landing the answer. An answer that trails off creates an awkward pause. End with your "why," then stop. Silence after you finish is normal.

7. Making claims you can't back up. "I'm an expert in AI" will immediately lead to technical follow-ups. Mention only what you actually know well.

A fill-in template

Copy this template and fill it in with your own facts. Keep the English simple.

1. Now:     I'm a [role] with [X] years of experience in [field].
            I mostly work with [tools/tech/clients].
2. Before:  Before that, I [previous role or experience].
3. Proof:   One thing I'm proud of is [project/result].
            It [simple impact: saved time, made X faster, who uses it].
4. Why:     I'm applying because [reason tied to this role].

Once it's filled in, read it out loud and time yourself. If it runs over 90 seconds, cut the least important sentence. Usually that's one from the "before" part.

How to practice without memorizing

Effective practice isn't reading the same text again and again. It's rebuilding the answer from cues. Try this:

1. Write your full answer using the template above.
2. Reduce it to four keywords, for example: backend – agency – order system – remote.
3. Say the answer while looking only at the keywords. Record yourself on your phone.
4. Listen back. Mark the places where you hesitated.
5. Simplify the sentences in those spots, then try again.

Do this three to five times a day for a few days before the interview. If you have a full week, follow the seven-day English interview prep plan as well.

Also prepare a 30-second version. Sometimes the interviewer says "briefly introduce yourself," or time is short. The short version only needs parts 1 and 4.

Pre-interview checklist

• My answer has four parts: now, before, proof, why.
• It takes 60–90 seconds to say.
• Each sentence fits in one breath.
• There's one concrete result I can explain in more depth.
• Everything I mention is true and on my CV or in my real experience.
• The "why" part says something about this company or role.
• I have a 30-second version.
• I've recorded it and listened back at least once.

This opening question is usually followed by others that are just as predictable. See the list in the most common English interview questions.

Summary

"Tell me about yourself" is your chance to steer the interview. Answer in the order now, before, proof, why. Use 6–8 short sentences, finish in 60–90 seconds, and mention only what you've actually done. Practice from keywords, not from a memorized script.

Repartee can help during the interview itself: it shows the question with an Indonesian translation and a short English answer script built only from your own profile. Claims in the script are checked before it's marked as verified, so no experience gets made up.