How to answer “Tell me about yourself” when you’re changing careers
Open with one piece of work you already do that the new role needs. Tell that story first, then walk through your job titles.
Ghosted editorialPublished 15 min read
On this page
- Pick the one piece of work that crosses over
- Alex, from support to QA
- Make sure it survives the follow-up
- From hospitality to operations
- Three questions that find your crossover
- Story first, then the job titles
- Say it, then stop and let them ask
- Where a career-change answer loses them
- A checklist before the interview
- Write down what they asked next
- Questions people ask about “Tell me about yourself” in a career change
Start here
Pick the one piece of work that crosses over
When you’re changing careers, “Tell me about yourself” hides a second question: why should someone from your field do this job? Your job titles can’t answer that. One piece of work can. Find the part of what you do now that the new role needs, and open with it. Three checks find it.
- The posting. Read it for the one thing the role exists to do. Not the list of tools: the work. “Turn customer reports into test cases” is the work; “experience with Jira” is a tool.What they need
- Your week. Find the part of your current job that already does that work, even if it’s a small part. It’s often the bit you volunteer for, or the bit colleagues bring to you.What you do
- One time. Pick a single occasion you did it, with a detail you can describe: what was wrong, what you noticed, what happened next. If you can’t name one, try another piece of work.Your proof
Then say it in that order: the piece of work, the time you did it, and why you want more of it. Your job titles come after, if they come up at all. Fill in the brackets and say it out loud a few times, in your own words.
I work in [your current field]. The part of my job I’m best at is [the piece of work the new role needs].
Recently, [one time you did it: what was wrong, what you did, what happened].
That’s the work I want to do all day, which is why I applied for [role] at [company].
That’s a shape, not a script. The next section shows it filled in, and what each part is doing.
Why not start with your first job?
Because a career change told in order makes them wait for the relevant part. Start with the piece of work that crosses over, and the rest of your history becomes the background to it rather than the reason to doubt it.
Worked example
Alex, from support to QA
Alex works in customer support for a billing software company and is applying for a QA Analyst role at Northline. Alex has never had a testing job title. Here’s the answer, as Alex would say it:
I work in support. My favourite tickets are the ones I can reproduce, narrow down and hand to an engineer with a clear test case.
The one I think about most: three customers in one week said their invoices showed the wrong tax. Nobody could make it happen. I noticed all three had changed their billing country that month, so I tried that on a test account and got the same wrong tax. I wrote down the exact steps, and the engineer fixed it from my notes without needing to ask the customers anything.
That’s the part of my job I want to be my whole job. Your posting asks for someone who can turn customer reports into test cases, and on my best days that’s what I already do. So when I saw this role, I applied.
It’s short enough to say in about a minute, and it never claims a title Alex doesn’t have. Here’s what each part is doing.
The opening
“I work in support. My favourite tickets are the ones I can reproduce, narrow down and hand to an engineer with a clear test case.” Four words for the current job, then straight to the piece of work that crosses over. “Reproduce”, “narrow down” and “test case” are words a QA team uses about its own work.
The bug
“Three customers in one week said their invoices showed the wrong tax.” One real case, with a detail they can ask about: the billing country. It shows the method, not just the interest. Anyone can say they like finding bugs; this says how Alex finds them.
Why more of it
“That’s the part of my job I want to be my whole job.” The reason for the change, said as a move towards something, not away from support. Then one line that ties it to the posting, in the posting’s own words.
Notice what’s missing. No list of every job since school. No apology for being new to testing. No claim of skills Alex hasn’t used. The interviewer can see the career change; the answer tells them why it makes sense.
The next question
Make sure it survives the follow-up
An opening answer is also an invitation. As a career coach tells The Muse, what you say helps the interviewer work out their next question. Whatever you mention, they’ll probably ask about, which is why the piece of work you choose has to be real and recent. Here’s what an interviewer might ask after Alex’s answer, and why each one is easy to answer when the story happened.
- They might ask: How did you work out it was the billing country?
What Alex can say: “I put the three accounts side by side and looked for anything they had in common. The country change was the only thing all three shared that month.”
- They might ask: Have you done any formal testing?
What Alex can say: “Not with that title. What I have done is write reproduction steps for the bugs I send to engineering. I can show you how I write them up.”
- They might ask: Why leave support?
What Alex can say: “I’m not leaving the customers behind. I want to catch these problems before they reach them, rather than after.”
- They might ask: What would you find hardest here?
What Alex can say: “Planning tests for something nobody has reported yet. In support, the customer finds the bug first. I’d want to learn how your team decides what to test.”
| They might ask | What Alex can say |
|---|---|
| How did you work out it was the billing country? | “I put the three accounts side by side and looked for anything they had in common. The country change was the only thing all three shared that month.” |
| Have you done any formal testing? | “Not with that title. What I have done is write reproduction steps for the bugs I send to engineering. I can show you how I write them up.” |
| Why leave support? | “I’m not leaving the customers behind. I want to catch these problems before they reach them, rather than after.” |
| What would you find hardest here? | “Planning tests for something nobody has reported yet. In support, the customer finds the bug first. I’d want to learn how your team decides what to test.” |
The second row is the one people dread, and it’s the one honesty makes easiest. If the true answer starts with “no”, say “no” first, then say what you have done. Inventing a testing course or a side project to avoid the “no” is the answer that falls apart, because the next question is about the course.
They’re listening for the next question
“Tell me about yourself” often comes first, and what you say shapes what they ask next. A specific story gives them something good to follow up on; a list of job titles gives them nothing to pick up.
Another example
From hospitality to operations
The same shape works far from tech. Sam has spent four years in restaurants, the last two as a shift supervisor, and is applying for an operations coordinator role at a logistics company.
I’ve spent four years in hospitality, the last two as a shift supervisor. The part of the job I’m best at isn’t on the floor. It’s the rota and the stock order.
Last spring we kept running out of the same things on Saturdays. I went back through two months of orders, matched them against the bookings, and moved our order day so the delivery came before the weekend instead of after it. We stopped running out, and the manager asked me to take over the ordering for the whole week.
That’s the work I want to do all day: looking at how things actually run and making next week go better than this one. That’s why I applied for the operations coordinator role.
The opening
“The part of the job I’m best at isn’t on the floor.” It names the old career in one line, then turns straight to the part an operations team would recognise as theirs.
The problem
“We kept running out of the same things on Saturdays.” A problem anyone can picture, and a method they can ask about: old orders matched against bookings.
Why more of it
“Making next week go better than this one.” A plain description of operations work, said by someone who has already done a small version of it.
The likely follow-up is “What did you use to track the orders?” If the honest answer is “a spreadsheet”, that’s a good answer. Say it, say what was in it, and say you’d expect to learn whatever system they use. Nobody hiring a career changer expects their tools on day one. They do expect you to know what you actually did.
Sam’s crossover
- The role needs
- Someone who plans stock and schedules so the week runs smoothly
- Sam already does
- The rota and the weekly stock order
- One time
- Saturday shortages, fixed by moving the order day
Build your own
Three questions that find your crossover
- What does the role do all day? Read the posting for verbs, not nouns. “Investigate”, “schedule”, “train”, “report”, “reconcile”. One or two of them describe most of the job.
- Where do you already do that verb? Look at your current week, your last job, and the jobs you take on that nobody asked you to. The crossover is often a side task, not your main one.
- When did it matter? One occasion where doing it well changed something: a problem fixed, a mess avoided, a person helped. That occasion is your story.
- Moving from: Customer support
- Moving to
- QA or testing
- The work that crosses over
- Reproducing a customer’s problem and writing the steps down for an engineer
- Moving from: Hospitality
- Moving to
- Operations
- The work that crosses over
- Planning the rota and the stock order
- Moving from: Teaching
- Moving to
- Learning design
- The work that crosses over
- Rewriting a lesson after a class got stuck on it
- Moving from: Retail
- Moving to
- HR or recruitment
- The work that crosses over
- Training new starters on their first shifts
- Moving from: Office admin
- Moving to
- Data analysis
- The work that crosses over
- Building the monthly report everyone uses
- Moving from: Nursing
- Moving to
- Health tech
- The work that crosses over
- Explaining a new system to colleagues who don’t trust it yet
| Moving from | Moving to | The work that crosses over |
|---|---|---|
| Customer support | QA or testing | Reproducing a customer’s problem and writing the steps down for an engineer |
| Hospitality | Operations | Planning the rota and the stock order |
| Teaching | Learning design | Rewriting a lesson after a class got stuck on it |
| Retail | HR or recruitment | Training new starters on their first shifts |
| Office admin | Data analysis | Building the monthly report everyone uses |
| Nursing | Health tech | Explaining a new system to colleagues who don’t trust it yet |
If you find two pieces of work, keep both. Lead with the one closest to what the posting describes, and save the other for later in the interview, when a different question opens the door to it. The interview prep sheet has a line for exactly this: the problem the job exists to solve, and your example of solving it.
Use their words for the work
If the posting says “investigate defects” and you say “look into weird tickets”, you’re describing the same thing in a way they have to translate. Borrow their words for the work, but never for experience you don’t have.
The shape
Story first, then the job titles
A common structure for this answer is present, past, future: what you do now, how you got there, what you want next. The Muse sets it out and adds that if there’s a strong story about what brought you to the field, you can start with that instead. For a career change, that’s usually the better order.
Lead with the crossover
- The interviewer hears why you fit in the first few sentences
- Your old career becomes the place you learned the work
- It invites a follow-up you can answer well
Walk through every job
- Familiar, and easy to prepare
- Spends most of the answer on work they aren’t hiring for
- Leaves them to work out the connection themselves
Skip the old career
- Tempting if you feel it counts against you
- Your CV shows it anyway, so it looks like you’re avoiding it
- Throws away the experience that makes your story believable
Your CV should tell the same story in the same order. If the answer leads with reproducing bugs but the CV buries it in the fifth bullet of a support job, move it up. Our guide to tailoring a CV to a job description shows how, and writing CV bullets without numbers helps when the work you did didn’t come with a metric.
On the day
Say it, then stop and let them ask
There’s no proven right length for this answer. The Muse notes that advice ranges from 30 seconds to two minutes, and quotes a coach who finds people start losing steam after a couple of minutes of talking without a break. The three-part shape above fits comfortably in that range. When you reach “that’s why I applied”, stop. A pause is their cue to ask, not a gap you need to fill.
Practise it out loud, not in your head
Say it to a friend, or record it and listen back later. Answers that read well on paper often have one sentence that’s hard to say. You’ll only find it by saying it.
Don’t learn it word for word
A memorised answer sounds memorised, and one interruption can knock it off course. Learn the three parts and the story. Let the sentences come out a little differently each time.
Change it for the person in front of you
A recruiter wants the big picture: why this move, why now. The hiring manager wants more of the story: how you found the bug, what you wrote down. Keep the shape and change the depth.
Listen for the other versions of the question
“Walk me through your CV”, “Tell me about your background” and “What brings you here?” are the same question. Give the same answer, starting where the question starts.
If they say “walk me through your CV”
They’re asking for the order of things, so give it, briefly. Then slow down at the job where the crossover happened and tell the story there. The order is theirs; the emphasis is yours.
What goes wrong
Where a career-change answer loses them
Apologising for the change
“I know I don’t have a traditional background, but…” tells them to look for the problem before you’ve shown them anything else. Lead with the work; let them decide whether the background matters.
Passion with no proof
“I’ve always loved data” is a feeling. “I built the monthly report the whole office uses” is evidence. Say the evidence and the feeling comes across on its own.
Claiming what you haven’t done
Calling yourself a tester because you’ve read about testing, or rounding a weekend course up to “training”. One follow-up question and it unravels, and it takes the true parts of your answer down with it.
Running down the old field
“I’m burnt out on customers” or “retail was a dead end” makes them wonder what you’ll say about this job in two years. Talk about what you’re moving towards.
The life story
Childhood interests, degree, gap year, three jobs, then the point. By the time you get to the crossover, they’ve stopped listening for it.
A story nobody can check
“I’m good at solving problems” with no occasion attached. Without a single time and place, it sounds the same as everyone else’s answer.
Last look
A checklist before the interview
After the interview
Write down what they asked next
Straight after the call, write down the follow-up questions they asked about your story. They tell you what the team cares about, and which part of your answer to build out for the next round. If they kept asking about method, the next interviewer will too.
Expect the questions that usually follow a career change: a weakness, and a “Tell me about a time…” about work you haven’t done yet. Our guides to talking about a real weakness and answering “Tell me about a time…” without that job behind you use the same rule as this page: the closest true example, told plainly. If there’s a second round, turn your notes into questions to ask.
Questions
Questions people ask about “Tell me about yourself” in a career change
Should I say outright that I’m changing careers?
Yes, in a line, and then move on: “I work in support, and I want to move into testing.” They can see it on your CV. Saying it plainly shows you’ve thought about it; leaving it out makes them wonder why.
What if the work that crosses over is from outside my job?
Use it, and say where it happened: a volunteer role, a side project, something you did for a club. Be clear it wasn’t paid work if it wasn’t. A real example from outside work beats a vague one from inside it.
Should I mention courses I’m taking?
After the story, briefly, if they’re real and relevant: “I’m also partway through a course on test design.” Don’t lead with them. A course shows interest; the story shows you can already do part of the work.
How long should my answer be?
There’s no proven right length. Advice ranges from half a minute to about two, and people tend to lose the thread when one person talks for much longer. The three-part shape usually takes a minute or so. Stop when you’ve said why you applied.
What if they ask why I’m leaving my current field?
Answer with what you’re moving towards, using the same story: “The part of support I’m best at is the investigating, and I want that to be my whole job.” Leave out complaints about the old field.
What if I’m taking a step down in seniority or pay?
Don’t raise it in this answer. If they ask, say it plainly and say why the move is worth it to you. If the question is about pay, our guide to salary expectations covers what to say.
Do I give the same answer to every interviewer?
The same story, at a different depth. A recruiter wants the move and the reason. The hiring manager wants the method. A senior leader wants to know why it matters to the business. Keep the facts the same in every version.
Keep your story with the job.
Keep the interview, your prep notes and the CV you sent together, so every round tells the same story.