Career Playbook Series — Post 1
Along with my other articles, I decided to start writing a Career Playbook Series — practical, no-fluff guides to help you navigate every stage of your career journey.
Let's start with the most dreaded question in any interview: "Tell me about yourself."
It's almost always the opening question, and yet most candidates are spectacularly unprepared for it. In my years of interviewing people, I've seen two responses repeated over and over — either a nervous, rambling answer that goes nowhere, or a word-for-word recitation of the resume the interviewer is already holding.
Here's the painful irony: this question is meant to be an ice breaker. It's designed to ease you into the conversation. But for most candidates, it lands like a sledgehammer — instantly denting their confidence, setting a shaky tone for everything that follows. Recovery is possible, but it's an uphill battle until a comfortable question comes along and the nerves finally settle.
It doesn't have to be this way.
The Framework: PRATV
I've split my guidance into two tracks based on experience level — less than 2 years and more than 2 years — because what works for a fresh graduate doesn't always work for a seasoned professional.
To make the structure easy to remember, I created this acronym:
PRATV — Personal, Role, Accomplishment, Technical Skills/Passion, Vision
Think of it as your answer's skeleton. Each section should be tight and purposeful. This is not your life story — it's your opening argument for why you're the right person for this role.
P — Personal
Be direct and keep it short. This is not the main event.
Should you start with your name?
- Less than 2 years of experience: Yes. It may feel slightly awkward if the interviewer has already used your name, but start with it anyway, followed by your current role, designation, or college major.
- More than 2 years of experience: Skip the name — they know it. Open instead with your current role, years of experience, and your area of specialization.
How personal should you get?
Keep it professional. Avoid mentioning your age, hobbies, relationship status, or personal preferences. None of that is relevant here, and it uses up time you need for the stronger parts of your answer.
R — Role
Again, keep it brief. But here's the shift: instead of simply stating your job title, build a picture of what your role actually means.
Anyone can say "I'm a Financial Analyst." What's more memorable is describing the problem your role exists to solve and the kind of work you do to solve it.
Less than 2 years of experience: Be honest about where you are in your career. Don't inflate your title or invent responsibilities you haven't actually held — interviewers see through this quickly, and it comes across as deceptive rather than impressive. If you worked in a junior role, own it confidently. What matters is how you talk about what you did in that role, not how grand you make it sound.
More than 2 years of experience: Don't just state your job title — anyone can do that. Instead, build a picture of what your role actually means. Describe the problem your role exists to solve.
A — Accomplishment
This is where you start to separate yourself from the crowd. Position yourself as a solution provider and a problem solver — not someone who just showed up and did their job description.
Pick one or two concrete outcomes you've delivered. Numbers help. Impact helps more.
Less than 2 years of experience: If you mention a project or code you've worked on, be ready to show it. Have a GitHub link, a deployed version, a code repo, or even a Google Drive folder ready to go. This is non-negotiable. Too many candidates claim projects on their resume that completely fall apart the moment an interviewer asks a follow-up question. If you can't show it or speak to it in detail, don't bring it up — it will cost you far more than the points you thought you were gaining.
More than 2 years of experience: This is where you can spend the most time. Pick one or two concrete outcomes you've delivered and lead with impact. Numbers help — revenue saved, costs cut, time reduced, teams led. The more specific you are, the more credible and memorable you become.
T — Technical Skills / Passion
Don't just list tools and software — anyone can do that. Instead, express genuine curiosity about where your industry is heading. What trends excite you? What problems do you think are still unsolved? This signals that you're engaged, forward-thinking, and someone worth having a real conversation with.
- Less than 2 years of experience: Less is genuinely more here. An interviewer will be far more impressed by someone who knows 2 skills deeply and has actually applied them, than someone who lists 10 skills they've barely touched. Pick the skills you know best, speak to how you used them, and be honest about your level. Also, a word on what doesn't count as a technical skill — listing Windows, Unix, Microsoft Word, or Excel signals that you're padding. Leave those off entirely.
- More than 2 years of experience: Frame your skills through the lens of industry trends and the problems you've used them to solve — this is far more compelling than a plain list. Highlight 3 to 4 skills where you have strong, hands-on expertise and can speak to them in depth. Then mention 2 to 3 skills you're familiar with but haven't yet mastered — this shows self-awareness and a growth mindset, both of which interviewers respect. Be honest about the distinction. The goal is to spark a conversation, not to oversell yourself into a corner.
V — Vision
Close by briefly articulating what you hope to do in this new role. What do you want to contribute? What kind of impact do you want to have? This shows the interviewer you've thought about the role seriously — and it ends your answer on an ambitious, future-facing note.
Spend at least 10 minutes on the company's website and LinkedIn profile before you walk in. Look at what they do, what they're building, and where they seem to be heading. This is the bare minimum. If an interviewer has taken the time to read your resume carefully, it is only fair that you return the courtesy. Yet time and again, when I ask candidates what they know about my company, the answer is essentially nothing — and all it would have taken was 2 minutes on their website. Remember, you're potentially asking this organization to invest 2 to 3 years in you. The least you can do is show up knowing what they do.
- Less than 2 years of experience: Keep your vision simple and grounded. This is not the moment to announce that you'll redesign the entire platform or rewrite the codebase — statements like that come across as naive rather than ambitious. Instead, express a genuine curiosity to learn, grow, and contribute within the scope of the role. A simple, honest vision delivered with enthusiasm is far more powerful than an overreach that raises eyebrows.
- More than 2 years of experience: This is where you can be bolder. Show genuine eagerness to join the team and paint a picture of how your skills and experience can make an impact — on the team, the product, and the wider organization. Connect what you've seen on their website or LinkedIn to what you bring. This tells the interviewer you're not just looking for any job — you're interested in this job, at this company, for real reasons.
The Shift That Changes Everything
Most candidates frame their answer like this:
"I've worked at X company, did Y, and my background is in Z."
The problem? Nobody is hiring your past. They're hiring what you're going to do for them next.
Try reframing your answer around the value you create and what excites you right now:
"I help [companies/industries] do [specific value you create]. Right now, I'm most excited about [a trend, challenge, or opportunity in your space]."
Here's how that shift looks in practice:
Past: "I'm a marketing director with 12 years of experience leading teams at Fortune 500 companies."
New: "I help tech companies build product loyalty through authentic storytelling. I'm particularly excited about how AI is transforming personalised customer experiences."
Past: "I'm a full-stack developer specialising in Python and React."
New: "I design distributed systems using Python microservices and React-based frontends. I'm focused on building event-driven architectures that stay reliable under heavy load."
Past: "I'm a financial analyst with 8 years of experience in corporate finance, managing budgets and preparing reports for senior leadership."
New: "I help mid-sized companies identify where they're quietly losing margin and turn that into a clear roadmap for growth. Right now I'm particularly focused on how real-time financial dashboards are changing the speed at which leadership teams can make decisions."
Why This Format Works
- You position yourself as a solution provider, not a job seeker
- You demonstrate forward-thinking and genuine engagement with your field
- You create natural conversation openings — interviewers will want to follow up
- You spark curiosity rather than reciting a CV they've already read
- You showcase expertise without sounding self-important
One final rule: keep your entire answer under 60 seconds.
A great answer to "Tell me about yourself" isn't a monologue — it's an invitation to a conversation. Say enough to intrigue them, then let the dialogue begin.
Top comments (0)