Career change into tech: how to write a resume with no tech title

If you are moving into tech from teaching, logistics, finance, hospitality or anywhere else, your resume has a specific problem: every line is true, and almost none of it is legible to the person screening it. A recruiter spends a few seconds deciding whether your history connects to the role. If your job titles say "Operations Coordinator" and the posting says "Junior Data Analyst", the connection has to be made for them, on the page, in their vocabulary.

This post is a method for doing that honestly. No invented titles, no padded skills, just translation.

Step 1: Stop leading with the job title, start leading with the target

The top of a career-change resume should say what you are going for, in one line:

Operations professional moving into data analysis. SQL, Python (pandas), Tableau.
Five years of reporting on fulfilment KPIs for a 200-person warehouse.

Compare that with a generic "Motivated professional seeking new challenges". The first gives a screener a reason to keep reading. It also contains the nouns that a search or filter would look for: SQL, Python, Tableau, reporting.

Keep it to two lines. If you cannot write it, you have not decided on a target role yet, and that matters more than any formatting choice.

Step 2: Mine your old job for transferable evidence

Take the job description for the role you want and list its recurring requirements. Typically they cluster into a handful of things:

• Working with data or systems (querying, reporting, automating)
• Owning a problem end to end
• Communicating with non-technical stakeholders
• Working in a team with deadlines, reviews and handovers
• Learning new tools quickly

Now go through your past roles and find real episodes that match each cluster. Not duties, episodes. "Responsible for scheduling" is a duty. "Replaced a shared spreadsheet with a script that generated the weekly rota, cutting the Friday prep from three hours to twenty minutes" is an episode, and it is directly relevant to a developer or analyst role even though you were never called either.

A useful prompt for each old role: what did I automate, measure, fix, or teach? Those four verbs produce most of the strong bullets.

Step 3: Rewrite bullets in the target field's vocabulary

The same accomplishment can be described in the language of your old industry or the language of your new one. Use the new one wherever it is accurate.

Old-industry phrasing	Translated phrasing
Kept track of stock levels in Excel	Maintained an inventory dataset of 4,000 SKUs; built pivot reports used in weekly planning
Trained new staff	Onboarded 12 new team members with written documentation and a walkthrough process
Fixed problems with the booking system	Triaged and reproduced booking-system bugs, wrote clear reports for the vendor's support team
Sorted out scheduling conflicts	Resolved resource conflicts across 3 teams using a shared priority rubric

The rule: change the framing, never the facts. If you did not write code, do not say you did. If you reported bugs rather than fixed them, say "reported". Interviewers will probe, and a claim you cannot defend costs more than a gap you openly have.

Step 4: Give projects the space a job title would have had

When you have no tech employer, projects carry the proof. Put a "Projects" section above "Experience" if the target role is technical. For each project:

1. One line on what it does and for whom
2. The stack
3. One measurable or observable outcome
4. A link

Rota Generator (Python, SQLite)
Generates weekly staff schedules from availability constraints; used by a team of 14.
github.com/you/rota-generator

Two or three finished, linked projects beat ten abandoned tutorials. Finished means it runs, has a README, and someone other than you has used it.

Step 5: Order and trim by relevance, not chronology

Reverse-chronological order is a convention, not a rule. For a career changer it is fine to:

• Keep the old roles but cut each to three or four bullets, all relevant
• Merge unrelated early jobs into one line ("Earlier roles: retail, hospitality")
• Move education, bootcamp or certifications up if they are the most recent relevant signal

Do not hide dates or leave unexplained gaps; applicant tracking systems and humans both handle an honest timeline better than a confusing one. If you are not sure how your file is being read by automated parsing, run it through a checker such as NextCV's CV check and look at what text actually comes out. Multi-column layouts and text inside graphics are the usual culprits for a career changer who has used a fancy template to compensate for a thin history.

Step 6: Tailor per application, but only the top third

You do not need to rewrite the whole resume for every job. Rewrite three things:

1. The headline line (swap "data analysis" for "business intelligence" if that is the posting's term)
2. The skills list order, so the tools they name come first
3. Two or three bullets, choosing the episodes that best match this posting

Tailoring is mostly selection and ordering from a pool of true statements you already wrote. Keep a master document with all your bullets, and assemble each application from it. If you want help comparing a resume against one specific posting to see which requirements are missing, tools like the job match checker do that comparison, but the same thing can be done by hand with a highlighter and a posting.

Step 7: Prepare to explain the move

Your resume will raise exactly one question in every interview: why the change? Have a short, specific answer ready and make sure the resume supports it. "I started automating parts of my job, found I liked it more than the job itself, and built these projects to test that" is credible because the document backs it up.

A quick checklist

• [ ] Top line names the target role and three relevant tools
• [ ] Every old-role bullet is an episode with a verb and an outcome
• [ ] Vocabulary matches the posting where it is accurate
• [ ] Projects section with links, above experience
• [ ] Old unrelated roles compressed
• [ ] Nothing claimed that you could not demonstrate live
• [ ] Plain single-column layout that survives copy-paste into a text editor

A career-change resume succeeds when a stranger can finish reading it and think "this person has already been doing a version of this work." You are not hiding your past; you are doing the translation work so the reader does not have to.