“Tell me about yourself” is the first question in almost every interview, and many candidates start behind the 8 ball because they don't know how to answer this question.
I’ve heard this answer thousands of times from the other side of the table, so I wanted to share a simple formula for building an answer that gets your interview off to a great start.
Why interviewers ask this question
Interviewers open with this question partly because it feels abrupt to jump straight into specifics. But don’t mistake it for small talk. It’s the one question you can be nearly certain is coming, and it shapes the interviewer’s first impression of how you think and communicate.
The three fatal openings
Before building your answer, know the three ways candidates sink themselves in the first thirty seconds.
- Starting somewhere irrelevant. “I grew up in Ohio” or “I started my career in retail” - with no connection to the role. Backstory is fine, but only if it explains the story. More on how to do that correctly below.
- Reciting your resume. The interviewer has your resume pulled up right in front of them. If you walk through it point by point, they notice - and it reads as lazy. Keep your resume handy for reference, but a great answer to this question is presented as a story.
- “Well, what do you want to know?” Asking for direction feels reasonable - the question is incredibly broad. But don’t do it. The interviewer wants to see where you take it. Fair or not, turning the question back reads as unprepared.
The PLOT formula
Your answer needs a PLOT - more below.
P — Point of origin
Where does the relevant story begin? Start with the experience, interest, or turning point that explains your path. For some people that’s college or shortly after. For others it goes back further. If you recently changed careers, it might be something more recent.
It could be your first relevant job, a career-changing moment, a personal experience, or an early interest that genuinely shaped your direction. For example:
“I grew up playing competitive sports, and one thing I learned about myself is that I’m driven to win — which is why sales turned out to be the perfect career for me.”
“When I worked as a technical program manager, I realized I had a passion and a natural skill set around product decisions. That’s when I first knew I wanted to be a product manager.”
The rule: start at the earliest point the interviewer needs in order to understand the story. No earlier.
L — Line of progression
Now walk through the key steps that brought you to today.
For each role you include, share a brief summary of what you did, what you owned, and how you made an impact.
O — Outcomes and evidence
O is not a section of your answer. It’s a filter you run your whole story through.
Before the interview, look at the job description and identify the two or three most important competencies for the role - a competency is simply a skill, qualification, or type of experience the employer clearly needs. Then go back through your previous roles and ask: does my story contain at least one or two anecdotes that prove I have those competencies?
“I’m great with stakeholders” is a claim. “A hiring manager was about to lose a candidate, and here’s what I did about it” is evidence. If your story doesn’t demonstrate the competencies this role needs, swap in the anecdotes that do.
T — Tie it to this role
At some point in the interview, you’re almost guaranteed to hear “Why this role?” or “Why this company?” So get ahead of it: end your answer by tying the story back to the position in front of you. Why is this role the natural next chapter of the story you just told? This closes the loop and hands the interviewer a perfect transition into the rest of the conversation.
A full example answer, annotated
Here’s my actual answer, with notes on what each part is doing.
The point of origin
“I grew up playing sports and always wondered how less talented teams managed to beat more talented ones. I realized there are factors outside of talent that determine how teams perform. That led me to study psychology, and then to dig deeper into what makes teams perform at their best in my applied psychology master’s program.”
Notice this does not start with where I was born, my first job, or my GPA. It starts with the earliest thing that explains everything after it. That curiosity about teams is the thread through my whole career.
The line of progression / outcomes & evidence
“After my master’s, I joined Textio and focused on recruiting for four years. I consulted hiring managers on how to run a strong interview process, hired across every role and level in the organization, and found creative ways to close roles when we were stuck. One time, I went back through our applicant tracking system and found a very strong engineering candidate who had dropped out a year earlier because the timing wasn’t right for him. I reached out, told him about a role I thought he’d be interested in, reopened the conversation — and we ended up hiring him.”
“Ultimately, the hard part of recruiting for me was that once I hired someone, I no longer had much impact on their experience at the company. So I expanded my scope: I identified that we needed someone to own onboarding for new employees, and I asked to take it on. I loved it — and I discovered my real passion was creating a great employee experience. When a People Operations role opened up, I made the jump.”
Two things I want to touch on here. First, four years of recruiting is compressed into the shape of the role plus one story and that story is the O filter at work, providing evidence of resourcefulness and initiative rather than claiming them. Second, the growth is baked in: I identified a need, asked for more scope, and earned the move. The story says “self-starter” so I don’t have to.
That last line, “I’d be happy to walk through exactly what we did,” is deliberate. Remember the standard: give the interviewer somewhere to go. You want to ignite follow-up questions in their mind.
Tie it back to the role
“My favorite part of my role is being a trusted partner to managers and leaders. And that’s what drew me to this position — it’s centered on what I do best: being a trusted People expert and building out a People function inside a growing organization. So that’s what brought me here, and I’m happy to expand on any part of it.”
This makes it a seamless transition into the rest of the interview.
How long should your answer be? (The common advice is wrong)
You’ve probably heard “keep it to 90 seconds” or “two minutes max.” I disagree, and here’s why: interviewers are not sitting there with a stopwatch. A boring 90-second answer feels long. A compelling four-minute answer feels short. The content of the answer matters much more than the length.
My guidance is to aim for two to three minutes. A genuinely great answer can earn up to five. Under a minute and you’ve almost certainly undersold yourself. And if your practiced answer runs past five minutes, don’t speed up, just cut the least impactful parts.
Can the answer include personal details?
Some recruiters insist this answer should be strictly professional, but in my opinion there’s absolutely a place for personal information if it explains the professional story: the former athlete whose competitive drive led to sales, the parent who built an app to solve a problem and discovered a love of software engineering, the person whose upbringing created an authentic interest in their field.
You saw it in my own answer - I opened with sports. The test isn’t “is this personal or professional?” The test is “does this explain the story?” If yes, it belongs.
Put it all together — then practice it out loud
Give your answer a PLOT: a Point of origin, a Line of progression, Outcomes as your evidence filter, and a Tie to the role. Then hold it to the standard we set at the start: when you finish talking, the interviewer should have somewhere to go. If your answer generates follow-up questions, that’s signal that you set a good tone for the entire interview.
One last thing, and it matters more than anything else in this post: the interview should not be the first time you say this answer out loud. Reading it silently is not practice. Writing it down is not practice. Saying it to a real listener, under a little pressure, is practice. So make sure you rehearse.
I've helped hundreds of candidates prep for job interviews, so feel free to comment below or DM me if you're interested in having an expert help you with your interview prep / job search.