Tell me about yourself when you are changing careers

Name the move in the first sentence. Then translate one result from the old work into a skill the new job actually uses.

Build your answer

Target role The job you are interviewing for. Years of experience Years in this kind of work. Use 0 for a first role or a career change. Current role or background A field, a path, or a short phrase.

Win 1 Include a number. Win 2 Optional. Win 3 Used in the long version.

Key strength One habit, not five adjectives. Why this company or role A reason that would be wrong for a different employer.

Runs in your browser. Nothing you type is uploaded.

30-second version

About 37 seconds · 92 words

A short cut for a recruiter screen.

Stop after one result. A short screen does not need the second story.

60-second version

About 58 seconds · 144 words

The default. Present, then past, then future.

If they lean in, drop the second result and spend the time on how the first one happened. Leave duties from the job description out.

90-second version

About 88 seconds · 219 words

A longer cut when they ask you to walk through it.

I'm looking for a product manager role. For the past 1 year I've worked as an elementary teacher who spent the last year on curriculum software. Before that, this is the work that got me here. I raised class reading growth 1.4 grade levels with a weekly plan. I also shipped a lesson-planning pilot that 18 teachers kept using. I then cut parent-email back-and-forth by writing one Friday update. None of that is a title. It is the work I can walk through. The through-line is turning a fuzzy goal into a weekly plan people actually follow. The future I'm aiming at is a product manager role, because this product team writes for teachers, and I want the planning habit on a product they use. The first thing I'd measure is the constraint the team already feels. The numbers in those results are ones I can defend, including what I owned. The product manager role is the move, and the results are how I know I can do the work. I can say any of those results more slowly, with the owner and the number intact. I would use the same judgment on the next product manager problem. The work I want next is still product manager work: a clear owner, a number, and a decision I can explain.

They can interrupt. Go present, then proof, then why this role. When they ask, go from the headline number to the decision you made.

When you can say the minute without the page, practice it live with Luna. It hears the question and helps you keep a line. 24 hours free.

How to answer it for this role

Career-change answers fail when they apologize, and they fail when they pretend the old career did not happen. "I taught for eight years and I am moving into customer education" is clear. The listener can place you. "I have always been passionate about your industry" forces them to guess.

Translate, do not dump. A teacher who says "I managed a classroom" has not helped a hiring manager. A teacher who says "I raised reading growth 1.4 grade levels by replacing a vague goal with a weekly plan" has shown a skill product, enablement, and operations roles use. Pick the bridge skill on purpose. Leave the rest of the old job for later questions.

Put years of the old career in the background, not in the years field, if those years were not in the new work. The builder should not call you a product manager of eight years because you taught for eight years. Your future beat is why this role is the right use of the bridge, not a request for a chance.

What to emphasize

The move, stated in sentence one.
One transferred result with a number.
A reason that uses the old skill on their problem.

What to leave out

"I know I don't have the background, but…"
A resume of the old career with the new title glued on.

Sample 60-second answer

This is the sample loaded into the builder above. About 58 seconds, 144 words. Replace every fact with yours before you practice it.

I'm looking for a product manager role. For the past 1 year I've worked as an elementary teacher who spent the last year on curriculum software. Before that, this is the work that got me here. I raised class reading growth 1.4 grade levels with a weekly plan. I also shipped a lesson-planning pilot that 18 teachers kept using. The through-line is turning a fuzzy goal into a weekly plan people actually follow. The future I'm aiming at is a product manager role, because this product team writes for teachers, and I want the planning habit on a product they use. In the job I'd bring that strength to the team's current goal, and I'd report what moved. I have the detail under each number, including what I would measure again. That is the minute: the product manager work, the proof, and the reason.

The 30-second cut is about 37 seconds. The longer cut is about 88 seconds. Both use the same facts in the same order. Read the longer structure guide if you want the timing rules in full: how long the answer should be.

Tips before you say it

Say the 60-second version out loud before you edit it. A sentence that looks fine on the page often runs long or sounds like a memo.
One number per win. “Improved the process” is a claim. “Cut hold time from 6 minutes to 2” is a result you can be questioned on.
Stay in order: present, past, future. If you start with where you grew up, the interviewer is waiting for you to arrive.
Leave a door open and then stop talking. The extra story you add in the silence is usually the one you did not prepare.
Keep your part separate from the team’s. “We launched” collapses the first follow-up. “I cut the scope, engineering shipped it” survives.

Other roles

Questions people ask

Do I apologize for switching?

No. State the direction and the proof. An apology makes the interviewer manage your confidence instead of evaluating the work.

How much of the old career belongs in the minute?

One result and the name of the old work. The second and third stories can stay in your pocket for "tell me about a time."

Should I mention a bootcamp or certificate?

Yes, briefly, if it is how you learned the new skill. It is context, not the result. Follow it with something you built or shipped.