"Tell me about yourself" is the most common opening question in interviews — and the most fumbled. The winning answer is a tight 60–90 second story in three parts: present (who you are professionally now), past (the relevant experience that got you here), and future (why this role, this company, now). It's not your life story — it's a focused pitch for why you fit this job.
TL;DR
Use the Present → Past → Future formula: where you are now, the relevant journey, why this role next.
Keep it to 60–90 seconds — long enough to land, short enough to respect their time.
Tailor it to the job: only include past experience relevant to this role. Cut everything else.
Lead with a strong one-line identity ("I'm a data analyst who turns messy data into decisions for fintechs").
Avoid the traps: reciting your CV, starting from secondary school, oversharing personal details, or rambling.
Why does this question matter so much?
Because it's almost always first, and first impressions anchor everything that follows. A sharp, confident answer sets a frame of "this person is competent and knows what they want" that colours how the interviewer hears your every later answer. A rambling, unfocused one forces you to spend the rest of the interview climbing out of a hole.
It's also a test disguised as an icebreaker. The interviewer is checking: can you communicate clearly under light pressure? Do you understand what this role needs? Can you tell a coherent story about your career? Get this right and you've answered three unspoken questions before the "real" ones begin.
"We coach candidates that this question is a gift, not small talk," says Abraham Iyiola, Founder of CareerBuddy. "You know it's coming in basically every interview, so there's no excuse not to have a polished 75-second answer ready. The candidates who nail it walk in and immediately sound like the obvious hire. The ones who wing it start their life story from university and lose the room before the second question."
The Present–Past–Future formula
Present (who you are now)
Open with a crisp professional identity and what you currently do. "I'm a frontend developer with three years building React apps for fintech, currently at [company] where I lead the UI for our payments dashboard." One or two sentences. This is your headline.
Past (the relevant journey)
Briefly connect the dots that made you good at this — only the relevant parts. "Before that I cut my teeth at an agency shipping client products fast, which is where I got obsessive about performance and clean code." Skip anything that doesn't serve the role you're interviewing for.
Future (why this role, now)
Close by pointing forward at them. "I'm now looking to bring that to a product-focused team like yours — I've followed [company]'s work on [specific thing] and want to own frontend at a company scaling fast." This signals genuine interest and intent.
A worked example (mid-level marketer)
"I'm a digital marketer with about four years' experience, currently running paid acquisition at an e-commerce startup where I've cut our cost-per-acquisition by roughly a third over the last year. I started out in content and social, which taught me how to actually talk to customers, then moved into performance marketing because I love the measurability of it. I'm looking to step into a role with more ownership over the full funnel — and your company stood out because you're scaling into new markets, which is exactly the kind of growth challenge I want to work on." Sixty seconds, tailored, forward-looking. Done.
The traps that sink this answer
The CV recital. Listing every job chronologically. They have your CV — give them the story, not a re-read.
Starting too far back. "I was born in Enugu and went to primary school…" Start at the professionally relevant point.
Oversharing personal details. Marital status, number of kids, hometown drama — none of it belongs here. Keep it professional.
Rambling. No structure, no endpoint. Practise out loud and time yourself; aim for 75 seconds.
Being too generic. An answer that could be given to any company signals you don't really want this one. Tailor the future part.
Three more worked examples (so you can see the pattern)
Career-switcher (banker → fintech product): "I'm transitioning into product management after five years in retail banking, where I managed relationships for SME clients and saw first-hand where digital banking falls short. That frontline experience is exactly why I moved toward product — I've since completed a product course and led a side project redesigning a savings flow. I'm looking to join a fintech where my banking domain knowledge becomes an advantage, and yours stood out because you're building exactly the SME products I used to wish existed."
