Your résumé lists what you did. It doesn't explain why it matters or where you're headed. In this issue, you'll build a short story you can say out loud in about 30 seconds that explains who you are, what you offer, and what you're looking to do next.

Have a Better Answer to "Tell Me About Yourself"

"So, tell me about yourself."

It's one of the most common questions you'll face in your career, and one of the hardest to answer well. You hear it in interviews, in promotion conversations, in your first 1:1 with a new manager, and in the hallway at meetups. Most people answer it the same way. They start with their current job and work backward. "Right now I'm at X. Before that, I was at Y..." And the other person's eyes glaze over.

Your résumé lists what you've done, but so does every other candidate's résumé. On paper, you all look equally qualified. Your résumé gets you the interview, but your story explains why your skills matter, how your thinking has evolved to bring you to where you are today, and where you're going next. When you answer with that kind of a story, your listener remembers it long after the conversation ends.

Once you have a story to tell, you can use it everywhere. It works in interviews and networking events, and it also gives you a starting point for your LinkedIn bio, a self-review, or the speaker bio for your next conference talk.

Your story has three parts. Your thread is who you are, your arc is how you've changed over time, and your trajectory is where you're going and why you're ready. Grab a pen or open a notes app, because each part ends with a short writing exercise.

Find your consistent thread

Your thread is the value you bring no matter what job you have. Maybe you're highly organized, or you build strong relationships fast. Maybe you can pick up anything. Your thread is the thing that shows up whether you're writing Go or running a PTA fundraiser.

Your skills are the things you've picked up along the way, and they change all the time. React, Kubernetes, and SQL are skills. Your thread is how you operate, like making messy systems understandable or getting people unstuck, and it'll outlast every framework you ever use. If your thread is "I know React," your story expires the day your team picks a different framework.

"I'm a hard worker" and "I'm passionate about tech" are what everyone says, so they won't help you stand out. A good thread is specific, and it describes something you do. "I turn chaos into processes" tells the listener what to expect when you join their team. So does "I learn the unfamiliar thing fast and teach it to everyone else."

To find your thread, look at what you already do without being asked. Work through these questions to help you find your thread:

• What do people come to you for, even when it's not your job?
• What do you do when nobody assigns it?
• What drains others but energizes you?
• What compliment do you hear over and over?

If you're not sure, start with the compliment question. If three different managers told you that you ask great questions, you can trust that it's true.

Your thread has to be consistent across your whole life. If you're the one who organizes the team's sprint backlog, you're probably also the one who keeps the family calendar and packs the gear for the camping trip. When you see the same behavior at work and at home, you've found a thread.

So once you have an idea for your thread, test it. Try to point to it in three unrelated places: a job, a different job or school, and something else outside of work. If you can find it in all three, it's your thread. If you can only find it in your current job, you need to keep looking.

Now take two minutes and write one sentence that starts with "I" and a verb. Make sure it holds up in more than one part of your life.

Once you have that, you'll strengthen it by explaining how you got there.

Map your arc

In any good story, the main character changes and grows. That's their arc. Now you have to explain yours.

A list of job titles in order only shows when things happened, like "I was a junior dev, then a mid-level dev, then a senior dev." Compare that to "I used to think my job was to write code. Now I think my job is to solve problems, and code is sometimes the answer." The second example tells you how that person thinks about their work. Your arc should do the same thing.

Characters in stories change because something happens to them that had a profound impact on them, so look for your turning point. It might be a failure or a project that went sideways. A mentor or a manager might have reframed something for you. It might have been a move to a new team or role that gave you a new perspective, or the moment you realized you'd been doing something wrong the whole time. Those are the most believable parts of your story, even if they feel like failures, because they show you can grow from a setback.

Once you've found your turning point, use this template to shape your arc:

I used to [belief or behavior]. Then [turning point]. Now I [new belief or behavior].

You may have more than one of these in your career. Pick the one that best supports where you're going next.

Answer these questions to help you define your arc:

• What did you believe about your work five years ago that you don't anymore?
• What can you do now that you couldn't do before?
• What mistake taught you the most?
• If you could go back in time, what would you tell yourself on day one of your first job?

Take two minutes and fill in the template. Start with the mistake question if nothing comes to mind. That's a quick way to find a turning point.

Once you've got your arc, you can explain what's next for you and why it's the right move.

Point your story forward

Your thread explains why you're suited to what's next, and your arc explains why you're ready now. Your trajectory names where you're headed. When you tell it well, your next step feels obvious. The listener thinks, "Of course that's next. Look where you've been." Your trajectory gives people a reason to believe in you and what you offer.

That only works if you're specific. "I want to grow as an engineer" and "I want to be a leader someday" don't tell the listener where you're headed. Compare them to this:

I want to own developer experience for an internal platform, because I've spent three years being the person who unblocks everyone else.

Name the problem you want to own or the role you want. Then attach the "because." The "because" is your evidence.

Look for a project where you did the next-level work without the title, or feedback that points toward the new role. Things you built, taught, or led on your own time count too. If you want to be a tech lead, when have you already led? If you want to move into developer education, what have you already taught? If you can't find any evidence, that's useful too. It tells you your next step is to go create some.

These questions will help you find your direction:

• What problem do you want to own next?
• What's already pulling you in that direction?
• What proof do you have today?
• What's the smallest next step you could take this month?

Take two minutes to name your direction and your evidence. If you only have the direction, write down the evidence you'd need and how you could get it.

Put it together

Now combine your three answers into one short paragraph:

I [thread]. I used to [old], but [turning point], so now I [new]. That's why I'm [next].

Aim for something you can say out loud in about 30 seconds. It'll feel clunky the first time, and that's fine. A draft you can revise beats a blank page.

Here's how it looks for Sam, a hypothetical backend developer:

• Thread: "I build systems other people can trust."
• Arc: "I used to measure success by features shipped. Then I was on call for an outage I caused because I wrote code with no tests or alerts. Now I design for failure first."
• Trajectory: "That's why I'm moving into reliability engineering. I've already led our incident review process and built our alerting playbook."

Sam's thread shows up in the arc, and the trajectory ends with evidence. Anyone who hears this understands why Sam wants a reliability role, and Sam can say it in under a minute. And in an interview, this story can answer some other questions the hiring manager has on their list before they even ask them.

Once you have your story, say it out loud to a friend or a coworker. Then ask them, "What thread did you hear?" If what they heard isn't what you meant, your examples aren't aligned, and you still have work to do.

Keep your story current

You'll tell your story to different people for different reasons, so change what you emphasize based on who's listening. In an interview, emphasize your trajectory so they know why you want this role now. When you're shooting for a promotion, focus on your arc and your evidence. With a new manager, emphasize your thread so they know how to get the best out of you. And at a networking event, keep it short. Share your thread and one line about where you're headed.

Your story will change over time as you grow and face new challenges. Revisit your story every six months or after any big project, especially if you get feedback that changes how you see your work. You should also keep a running list of your wins as they happen. Julia Evans calls this a brag document, and her post includes a template you can start from.

You started with a résumé. Now you have a story. Go tell it to someone.

Things to Explore

• Video Teleprompter Lite is an iOS app that lets you record videos while displaying the text right on the screen. The front-facing cameras work well on newer phones, so this is a great way to create content on the go while maintaining eye contact with your audience.
• Paperless-ngx is an open-source document management solution you can use to catalog, search, and manage documents, PDFs, and scans. You can self-host it, and recent versions let you allow LLMs to access your documents. If you want to go paperless but not store your stuff in the cloud, this could be the right solution for you.

Parting Thoughts

Before next month's issue, practice tuning your story for different listeners:

• Think of two people who'll hear your story in the next few months, like an interviewer and a new manager. Which part of your story should you emphasize for each one? Rewrite your opening sentence for both.
• Cut your story down to one sentence you could say at a networking event. What did you have to leave out, and does your thread still come through?

As always, thanks for reading.