When you open your old resume before changing careers, it is tempting to start deleting. The industry is different, the job titles do not line up, and even familiar terms from your old work seem out of place.
But deleting the whole section feels wrong, too. You really did do that work, one task at a time.
For a career change resume, first explain what you worked on, what you actually did, and what you delivered. Then compare those facts with the target role to decide what deserves detail and what can be brief. You can preserve useful experience while giving HR less to guess about.
There is no need to start by calling yourself a “strong communicator” or a “fast learner.” One specific piece of work gives you more to build on.
Familiar industry terms may need an explanation
Suppose you used to track orders at a home furnishings store and now want to apply for a project assistant role at a software company. Your old resume says:
Responsible for order checking, kit completeness tracking, and delivery and installation coordination.
Those terms may have been useful shorthand in your old team. But HR in another industry may not know what you checked, how far you tracked each order, or which decisions belonged to you.
Replacing the line with “Excellent coordination skills” hides the concrete work that was there.
The following hypothetical conversation unpacks it.
Think of one order you actually tracked. What did “order checking” and “kit completeness tracking” involve?
I checked that the order included the model, dimensions, and all required fittings. Then I asked the manufacturer whether the products and fittings were all ready. I recorded anything missing and its expected availability date in a tracking sheet.
The shorthand now points to specific actions: checking information, confirming readiness, and recording missing items and dates.
If missing fittings affected the planned delivery and installation date, which part did you handle?
I asked the manufacturer when the missing items were expected, shared the update with sales and the installers, and followed up until they confirmed new arrangements. Sales was responsible for promising dates to customers; the installers decided how the installation would be carried out.
This separates your contribution from other people’s responsibilities. You confirm information, share updates, and follow up. That does not make you responsible for the entire delivery.
How was your tracking sheet used afterward?
Sales and the installers checked it for product readiness and items awaiting confirmation. Once new delivery and installation arrangements were confirmed, I kept updating it. When the installers reported completion, I recorded that status.
There is now a clear picture of the work, the steps you took, and how the information was used. You could first write:
Checked home furnishings orders for model, dimension, and fittings information; confirmed product readiness with manufacturers and recorded missing items, expected availability dates, and pending confirmations in a tracking sheet. Shared changes with sales and installers, followed up on delivery and installation arrangements, and updated completion status based on installer feedback.
HR can understand your work without first learning what “kit completeness” means. The industry context remains, and your responsibilities have not been inflated.
Once the work is clear, check its relevance to the target role
Helping HR understand is the first step. Next comes a different question: what does this experience tell them that is useful for this application?
Continuing the hypothetical example, suppose the target job description includes this task:
Organize project materials, track action items, and share progress with the people involved.
This is an illustrative requirement, not a claim about how all software companies hire. When working on your own resume, use the actual description of the job you plan to apply for.
Compare the two sides:
| Task in the target role | Supporting facts from your previous work |
|---|---|
| Organize materials | Checked order information and recorded missing items and pending confirmations. |
| Track action items | Followed up on availability dates and confirmation of delivery and installation arrangements. |
| Share progress | Shared status changes with sales and installers and updated the record. |
This experience provides evidence of organizing information and following up on tasks. If those are important parts of the target role, the experience deserves space.
It does not yet show that you understand software development processes. Nor can you rename home furnishings order tracking as “software project delivery experience.” Industry knowledge and specialist skills required by the target role need evidence of their own.
Finding tasks in common helps you choose what to include. It does not mean you have already done the target job.
Put the relevant work first without giving it a new identity
For that hypothetical requirement, you could shift the emphasis:
Maintained a home furnishings order tracker covering missing items, expected availability dates, and pending confirmations. Shared status changes with sales and installers, followed up on delivery and installation arrangements, and updated completion status based on installer feedback.
This version puts recording, sharing updates, and following up first, while keeping the real context: home furnishings orders. It adds no new facts. It simply makes the work relevant to the target task easier to see.
Keep your actual job title, industry, and employment dates. You do not need to adopt a title you never held to sound closer to the job description.
If an experience has little relevance to the target role, keep it brief. If it demonstrates related work, describe the facts. Not every previous role needs to produce a list of “transferable skills.”
You do not have to remove every technical term, either. Keep terms the target role uses when they accurately describe your work, adding a short explanation where needed.
Try it with one job requirement
Choose a role you plan to apply for and pick just one specific task from its description. Write three notes beside it:
- What does this task involve, and what needs to be delivered?
- Have I done anything similar? Which specific piece of work can I describe?
- Which facts support the connection, and which requirements do I not yet have evidence for?
Use your actual experience to rewrite one line. Explain jargon that would otherwise leave HR guessing, move the relevant actions forward, and leave out experience you do not have.
Do not rush to clear out your old work history. Explain what you did first, then decide what deserves a place in the next version of your resume.
This is the approach ResumeMeow is developing: ask follow-up questions to clarify your experience, let you confirm the facts, and then decide how to write them. The product is still in development. You can learn about ResumeMeow’s approach and start with one job requirement and one specific piece of work.