"Tell me about yourself": how to answer in a job interview

Three parts. Roughly thirty seconds each.

Now — where you are and what you are known for. Your current role, the scale you operate at, and the one or two things you are genuinely strong at. Not your job title read aloud; what you actually do.

How — the two or three moves that got you here, and the logic. Not every job. The moves that explain the shape of your career, each with the reason you made it. The reason is the part people leave out, and it is the part that turns a list into a narrative.

Why — what you want next, connected to this role. This is what makes the answer about them rather than about you, and it is where most answers simply stop early.

The order matters. Starting with "I graduated in 2011…" spends your best thirty seconds — the ones where attention is highest — on the least relevant information.

Fill this in, then read it aloud. Do not write the answer as a paragraph first; build it from these parts and let the sentences form when you speak.

Four rules for the filled sheet:

Leave out everything before the move that matters. If you have twelve years of experience, your first job is one clause or nothing at all. Graduates are the exception — for them, the degree and the internships are the material.

Every "why" must be forward-looking. "I left because the manager was difficult" is a fact about the past. "I moved because I wanted to own a P&L rather than support one" is the same move, told as a decision.

The through-line is the most valuable line on the sheet. Three moves with a visible thread reads as direction. The same three moves with no thread reads as drift, and the interviewer will ask about it.

Ninety seconds is 200 to 230 words. Write it, count it, cut it.

Three versions of the same structure at different stages. Use the shape.

Mid-career, staying in the same field

I'm a financial analyst at a retail group in Riyadh, where I own budgeting and forecasting for a SAR 300 million revenue line across four business units. The part I'm strongest at is turning messy actuals into something commercial teams will actually use — I rebuilt our monthly reporting in Power BI last year and took close-to-report from nine days to four.

I started in audit, which taught me to be careful with numbers but not much about the business behind them. I moved into industry after two years specifically to get closer to the decisions, and moved again into this role because it added forecasting and pricing rather than just reporting. The thread through all of it is that I keep moving toward where the numbers get used rather than where they get produced.

What I want next is more exposure to strategic planning, and this role sits in the planning function rather than reporting into it. That is the main reason I applied.

Career changer

I'm a project manager in construction, running fit-out projects up to SAR 40 million, and I'm moving into technology project delivery.

That sounds like a bigger jump than it is. What I've actually done for eight years is manage dependencies between people who do not report to me, against fixed dates, with real consequences for being wrong — which is most of what delivery management is anywhere. I started in site engineering and moved into project management because I was better at the coordination than the engineering. Over the last eighteen months I've been running the digital workstream on our projects, which is how the move started — I did the work before I decided to change field.

What I want is to do that full-time rather than as a side workstream, in an organisation where it is the main thing rather than an add-on. That is what this role is.

Early career

I graduated in supply chain from King Saud University two years ago and I've been at a 3PL in Jeddah since, currently as a planning coordinator.

What I've picked up is the operational detail — I run daily capacity planning across three warehouses, and I built the shift-forecasting sheet the team now uses. I chose supply chain deliberately during my degree after an internship in a distribution centre, because I liked that the problems are concrete and you find out quickly whether you were right.

What I want next is to work on the network side rather than single-site operations, which is why this role interested me — it covers planning across the region rather than one facility.

These examples are constructed to demonstrate the structure. The people, employers and figures are invented.

Notice what none of them does: none lists every job, none explains a gap or a grievance, none runs past two minutes, and none ends without connecting to the role.

Record yourself. Play it back and score honestly.

13–16: done. Rehearse twice more and stop. 8–12: almost always criteria 3 and 5. Add the reasons, add the ending. Below 8: rebuild from the worksheet rather than editing what you have.

Criterion 8 is the one that catches people who prepared well. An answer memorised word for word sounds memorised, and it collapses if you are interrupted. Rehearse the structure until the beats are automatic and let the words vary each time.

"Walk me through your CV." Same content, more chronological permission. Still ninety seconds, still ending on what you want.

"Tell me about yourself" as the opener of a screening call with a recruiter. Shorter — sixty seconds — and weighted toward whether you match the specification.

"So, what's your story?" Informal phrasing, identical answer. Do not let the casual tone pull you into casual content.

Asked again by a second interviewer later in the process. Give the same answer. They compare notes, and a materially different version reads as invention.

Expect it in either language, and prepare it in both. Not translated — rehearsed separately. The version you can deliver smoothly in your second language is shorter than the one in your first, and that is fine.

On a panel, deliver it to the room. Start with whoever asked, move your attention across the others as you go, and return at the end. A ninety-second answer delivered entirely to one person on a panel of five is noticed.

Keep personal detail out unless invited. Interviews here are often warm and conversational, and it is easy to drift into family and background because the tone permits it. The tone permits it; the assessment form does not have a box for it.

How long, exactly?

Ninety seconds. Two minutes is the ceiling. If you have more than two minutes of material, you have not chosen what matters.

Should I mention my personal life?

No, unless asked. If you want to add a human line at the end, one clause is enough.

What if I have a gap or a short stint?

Do not bring it up here. This answer is for framing. If they ask about it later, answer it directly then — pre-emptively defending something nobody has raised makes it larger than it was.

I get nervous and blank at the start.

Which is exactly why this is the one answer worth near-memorising. A fluent opening settles you for everything after it. If English is the pressure point, English interviews for Arabic speakers covers what to do about it.

Is it the same as "why should we hire you"?

No. This one frames who you are; that one argues why you over someone else. Different jobs, different answers.

Build it from the worksheet, record it, score it. The whole exercise takes under an hour and it improves every interview you have from now on, because the opening is the only answer that is genuinely reusable.

Then work on the rest: the interview question hub covers the other four question types, and the STAR structure covers the behavioural answers this one sets up.

If you have rehearsed it and still cannot tell how it lands, that is what another person is for — mock interview coaching, or the self-paced interview preparation course.