The video call connects, the hiring manager smiles, and then comes the question that opens almost every interview, “So, tell me about yourself.” You take a breath and start at the beginning with where you studied, your first job, the one after that…
Many people answer this way, and it’s easy to see why. Picture a career changer interviewing for a junior data analyst role. They open with “Well, I studied chemistry at university, and then I did my teacher training, and after that I taught at the same school for eight years…”
Ninety seconds later, they’ve reached the bootcamp. The hiring manager is still waiting to find out why a chemistry teacher is in this interview. Whoops, that’s a long road to the point!
What the Question Is Really Asking
“Tell me about yourself” sounds like an invitation to start at the beginning, but it’s really a request for your positioning statement as a brief spoken answer. The interviewer wants to know who you are now, what makes you credible, and how that connects to this role.
It’s usually the first question, so your answer also shapes what the interviewer listens for next. The Muse has a guide to this question with example answers. A pitch that ends by connecting your experience to this role hands them their next question. One that ends with “…and, well, that’s me” leaves them to pick something at random from your CV.
You already did the hard thinking in positioning.md, back in Translate Your Past, Position Your Future. Your pitch gives that statement a little room to breathe and turns it into spoken language. If it won’t come together, the statement usually isn’t settled yet, so go back to it rather than polishing your delivery.
Present, Past, Future
A pitch that works usually has three beats:
- Present: What you do now, or what you’re doing to get there, in one sentence.
- Past: The thread from your earlier work, with one concrete piece of evidence. That’s a story from your story bank, told in a single sentence.
- Future: Why you want this role at this company, keeping the focus on them as you finish.
Here’s the same career changer’s pitch, rebuilt with those beats in mind:
I’m a data analyst in training. I’ve just finished a bootcamp where I analyzed local air-quality data with Python and SQL for my capstone project. Before that, I taught chemistry for eight years, and the part I enjoyed most was the data.
I rebuilt our department’s grade tracker when two formulas disagreed, and I presented exam trends to the governors. That’s why this role caught my eye: you need someone who can explain messy data to people who aren’t analysts.
That’s about 80 words, so it takes well under a minute to say at a typical pace. Teaching is still in there, but now it’s one sentence of evidence, and you’ve practically written the hiring manager’s next question for them.
Notice what else is missing. There’s no apology!
Imagine a QA engineer returning after a career break who opens with “I should say up front that I’ve been out of the industry for three years, so I’m a bit rusty.” The first thing the interviewer hears is the concern. Openings like “I don’t have a CS degree, but…” or “I’ve only been coding for a year…” do the same.
If a concern belongs in your pitch at all, give it half a sentence in the past beat and state it plainly. You’ll prepare full answers to those questions later in this section.
Notes, Not a Script
It’s tempting to write a perfect paragraph and memorize it. But recited pitches sound rehearsed. They also break down when the interviewer interrupts with “Sorry, which bootcamp was that?” and you lose your place. And nobody says polished written phrases like “a results-driven professional with a passion for data” out loud to another person.
So write your pitch as three bullet points of a few words each, and practice from those. Each run will sound a little different, and that’s the point. You’re telling the same story each time, just with small changes in wording.
Then practice in a way that shows you what you actually sound like. Say your pitch out loud or record it on your phone, then type what you said, including ums and false starts. A transcript reveals rambling that a written draft hides.
People speak at roughly 130 to 150 words a minute in an interview, so 60 to 90 seconds is about 130 to 220 words. Timing yourself gives you a better measure than that estimate. If you’re over two minutes, cut the past beat first.
One Core, Three Rooms
The same three beats work for different listeners, but the ending changes. Give a recruiter a shorter version that names the role and explains why you’re a good fit in plain language. For a hiring manager, expand on one piece of evidence and explain why you want to join this team.
Give someone at a meetup who asks “So what do you do?” the shortest version, with less emphasis on the job search. End with a question for them, such as “What are you working on?”
Now it’s your turn. Grab a pen and paper and write your three bullet points for your top target role, using positioning.md and your story bank. Say the pitch out loud twice, a few minutes apart, and type what you said each time. Then write the recruiter, hiring manager, and meetup endings side by side. Save all of it under a “Pitch” heading in a new file named interview_prep.md in your career folder.
If you’re still unsure how your target role differs from its neighbors, the section on different developer paths in Python Skills That Get You Hired can help you name it precisely.
Up next, you’ll take on the questions that usually come right after the pitch, the ones that start with “Tell me about a time when…”
