When you get the "Tell me about yourself" question in an interview, answer using the "present — past — future" formula: who you are and what you do now, the experience that brought you here with 1–2 results, and why this particular role appeals to you. Keep the whole answer under two minutes and only about what's relevant to the job. Below is the formula step by step, examples for junior and middle IT roles and a non-IT role, plus the typical mistakes.
Why the recruiter asks this question
"Tell me about yourself" sounds like a warm-up, but it's actually the first test. In those two minutes, the interviewer decides whether you can get to the point, whether your story matches your CV, and whether your career has a clear logic to it. Your first answer sets how closely they'll listen to everything that follows.
As a recruiter, I notice that the strongest candidates don't necessarily have the best experience. In the first minute, they simply answer the key question for me: why this person fits this role. The rest of the conversation just confirms that impression.
The "present — past — future" formula
This structure works because it mirrors how a recruiter thinks: first — who's in front of me, then — is there proof, and finally — do our goals line up.
-
Present — 20–30 seconds
Your current role, level, field and main area of responsibility. "I'm a middle Python developer with 4 years in backend, currently working on a payment system for a fintech product."
-
Past — 40–60 seconds
The path that brought you here, plus 1–2 achievements with results. Not a list of every job you've had — just what's relevant to this role.
-
Future — 20–30 seconds
What you're looking for next and why this role fits. This is where you tie your story back to the job.
Altogether — about 1.5–2 minutes. If it runs longer, trim the past: that's usually where the extra detail piles up. If the interviewer wants more, they'll ask, and then it's a conversation, not a monologue.
Example answers
The names and details in the examples are made up. Don't copy them word for word — take the structure and plug in your own.
Junior in IT (first job or career switch)
I'm a junior QA engineer. Six months ago I finished a testing course, and before that I spent three years as a clinic administrator, where I handled patient scheduling through an online system. That's where I started noticing bugs and writing developers detailed descriptions of how to reproduce them. On the course, I built a practice project: I tested an online store, wrote over a hundred test cases and my first automated tests in Postman. Now I'm looking for a team where I can grow in web application testing, and your product for clinics feels close to me — I know those users from the inside.
Why it works: the previous non-IT experience isn't hidden — it's turned into an advantage. There's a concrete practice project and a clear connection to the company.
Middle in IT
I'm a frontend developer with 4 years in React and TypeScript, the last two at a product company building an online booking service. I was responsible for the client dashboard: I rebuilt it off the old stack, and the page started loading twice as fast. Before that, I spent a year and a half in outsourcing on e-commerce projects, where I learned to get up to speed in someone else's code quickly. Now I want to have more impact on the product — to take part in decisions, not just implement tasks. Your opening has a role on a product team with analytics — that's exactly what I'm looking for.
Why it works: level and stack right away, one measurable result, clear logic behind the switch, and motivation that draws directly on the job posting.
Non-IT role (sales manager)
I'm a B2B sales manager with 5 years working with corporate clients in logistics. Right now I manage a portfolio of twenty regular clients and handle upselling. Over the past year, I moved two clients from one-off orders to annual contracts. I started out with cold calls, so I know the full deal cycle — from first contact to contract renewal. I'm looking for a company where I can work with bigger deals and a longer sales cycle, which is why your key account manager position interests me.
Why it works: the scale of responsibility is clear, there's a result, it shows growth from cold calls to key accounts, and the motivation matches the next step.
Weak vs. strong answer: a comparison
- "Well, my name is Olena, I'm 29, I'm from Kharkiv…"
- "I graduated with a degree in economics, then worked at a bank, then at an insurance company, then…"
- "I was responsible for working with clients and various tasks."
- "I'm job hunting because I want something new."
- "I'm a data analyst with 3 years in retail, currently building reporting for the procurement team."
- "I came into analytics from finance, so I have a solid grasp of how the business reads the numbers."
- "I automated a weekly report, so the procurement team now gets the data on Monday morning instead of Wednesday."
- "I want to work with product data, and on your team analytics actually drives product decisions."
Common mistakes
- Reciting your CV point by point. The recruiter has already read it. Your job is to explain the logic, not repeat the content.
- Starting with your childhood or university. If you have more than two or three years of experience, your education should almost never come first.
- Talking for 5 minutes. A long monologue signals that you can't get to the point — and that's an important skill in any role.
- No numbers or results at all. "I did marketing" says nothing. "I launched an email campaign that became our second-biggest sales channel" says something.
- Not tying it to the job. An answer without the "future" part leaves the recruiter wondering: so why us?
- The same answer for every company. The present and the past can stay the same, but the future should be tailored to each specific role.
How to prepare your own version
- Open the job posting and write out the 3 main requirements. Your answer should touch on at least two of them.
- Write one "present" sentence. Role + level or years of experience + field + main area of responsibility.
- Pick 1–2 results from the past that best match the requirements. Ideally with a number or a visible outcome.
- Write the "future" for the specific company. What you want to do next and why this role is the logical next step.
- Say it out loud with a timer. Aim for under 2 minutes. Record yourself and listen back: where you drag, where it sounds rehearsed.
- Don't memorize it. Remember the structure and the key facts, but let the wording stay natural.
The hardest part here is capturing your present and future in a single sentence each. That's your positioning: who you are on the market and where you're headed. Positioning questions are exactly where the COScafe resume builder starts — those same answers then feed into both your CV and your "tell me about yourself," so the version on paper and the one in the interview line up. And to check whether your positioning comes through in your current CV, run it through our free CV review.
If the interview is for an IT role and you're still deciding where to apply, start with our article on how to find a job in IT in 2026.
In short
- The formula: present (who you are now) — past (1–2 results) — future (why this role).
- Under 2 minutes, only what's relevant to the job.
- At least one concrete result instead of a list of duties.
- The "future" part — tailored to each specific company.
- Your story matches your CV, and your wording is natural, not rehearsed.