How to plan a career change

Make a career change more concrete by choosing a direction to investigate, finding evidence of what already transfers, and testing the gaps with small actions.

All worked examples are fictional. Use your own facts when adapting them.

Define a direction you can investigate

Choose one target role to research first. Write down why it interests you, the work you want more of, and any constraints such as location, schedule, training cost, or income needs. A target is a research question you can revise, not a permanent commitment.

Read several current job descriptions for that role. Note responsibilities that recur, tools that appear often, and qualifications described as required or preferred. Separate the recurring work from a single employer’s wish list. Job titles can cover different responsibilities, so compare the actual work.

Fictional starting question

Alex coordinates customer onboarding and is considering product operations. The first question is whether the role’s process and customer-feedback work fits Alex’s interests. The initial constraints are three hours per week for preparation and no paid course commitment until the skill gap is clearer.

Map transferable skills to evidence

Create three columns: a responsibility in the target role, relevant work you have done, and the gap that remains. A transferable skill is strongest when you can explain the existing example and how it applies in the new setting.

Do not relabel your previous job as the target job. Show the connection while being clear about what you have not done yet. This gives you material for a truthful resume and a more useful learning plan.

Fictional evidence map

Target responsibility: coordinate feedback across teams. Existing evidence: Alex organized onboarding requests and agreed ownership with two team leads. Remaining gap: no experience maintaining a product feedback taxonomy.

Target responsibility: document repeatable workflows. Existing evidence: Alex wrote intake checklists and troubleshooting guides. Remaining gap: learn how a product team uses those documents during releases.

Target responsibility: report recurring issues. Existing evidence: Alex maintained a weekly request summary. Remaining gap: practice categorizing a sample dataset and explaining the limitations of the analysis.

Test a gap with a small work sample

Choose one recurring requirement and design a project that demonstrates it. Define a deliverable before choosing a course: a short analysis, a documented workflow, a prototype, or a written recommendation may be enough for an initial test.

Use public information you are allowed to use or clearly labeled fictional data. Explain your assumptions and limitations. A personal project can show learning and judgment, but it should not be presented as paid employment or a client result.

Fictional project brief

Alex creates 30 fictional support requests, groups them into five feedback themes, and writes a two-page recommendation showing how each theme could be routed to an owner. The sample includes the raw fictional data, category definitions, and a note explaining that no real customer information was used.

Completion check: another person can follow the categories, understand the ownership rules, and see where the sample is too small to support a broader conclusion.

Build a manageable 30/60/90-day plan

Plan actions you control instead of promising yourself an offer by a particular date. Give each phase a small deliverable and a review point. Fit the plan around the time and money you can actually commit.

Fictional transition plan

Days 1–30: compare five relevant postings, complete the evidence map, and choose one project. Ask two people doing similar work about the responsibilities you do not understand.

Days 31–60: complete the fictional feedback project and request feedback on whether its categories and recommendations are understandable. Record changes made after the feedback.

Days 61–90: update the resume and profile with accurate transferable examples and the clearly labeled project. Apply selectively to roles that fit the evidence, and use responses to refine the plan.

Weekly time budget: 90 minutes on the project, 60 minutes on focused learning, and 30 minutes on outreach or review. Total: three hours. If that is not sustainable, reduce the scope before adding more tasks.

Review the direction before spending more

At each review point, ask what you learned about the role and whether the remaining gaps are worth addressing. Track completed work, useful feedback, and unresolved questions. A change of direction can be a sensible result of research.

Verify a course, credential, or resource with its provider and current role requirements before spending time or money. Suggested resources are research leads. Planning milestones do not predict how long a transition will take or guarantee employment.

  • My target is based on the work in actual role descriptions.
  • Each claimed transferable skill has an example.
  • Learning goals and demonstrated skills are clearly separated.
  • The next action has a deliverable and fits my available time.
  • I have checked costs and requirements before committing to a resource.

Plan a transition from your background

Create an account to try your first resume preview without a card, subject to generation limits. Resume export is $5.99 for one application, or optional Boost at $2.99/month for five resume-and-cover-letter packets per subscription billing period. Other tools show their own paid options before checkout.

More career guides

Questions & answers