Write a UK Tech CV for Career Changers (ATS-Friendly)

11 min read

You're not starting from zero. You've got years of stakeholder work, spreadsheets, or ticket queues. What you don't have yet is a CV that reads like tech in the first eight words of each bullet. That's the gap these pairs fix.

Before you paste another template, check your resume for free against one live posting. You'll see fast whether your target title and SQL or Python land in Experience or only in a Skills cloud the parser drops.

Job hunting while you're still in your old role is draining. This page won't promise a bootcamp miracle. It shows the CV shape UK tech recruiters skim after Workday or Greenhouse parses your upload.

You can act in ten minutes: pick one posting, change the header title, and rewrite a single bullet using the After pattern in pair two. Save the file before you touch fonts or margins.

Below you'll see the weak lines we judge against, five before/after pairs across common pivots, what those weak versions share, and a copy-paste profile you can adapt tonight. If the form asks for a letter, use the cover letter generator with the same target title you put in the CV header.

What a UK CV for career changers in tech must prove first

Recruiters ctrl-f for three things: target role title, evidence you can learn the stack, and continuity you won't quit after month three. ATS adds a fourth: a file it can read top to bottom without columns scrambling employer names.

Target title in the header beats a clever personal statement. Write Junior Data Analyst or IT Support Analyst under your name, not Dynamic professional seeking opportunities.

Transfer proof lives in bullets, not adjectives. Taught Excel to staff is weak. Built Excel macros that cut month-end close from six days to four for a 40-person finance team is strong when the req mentions automation.

Projects fill gaps; paid work still leads. Bootcamp capstones belong on page one only until a paid tech title exists. After that, shrink Projects and expand the job block.

UK CVs often run two pages for career changers. US one-page rules do not apply when you're carrying fifteen years of relevant transfer work. Page one still has to sell the pivot in ten seconds.

I've screened career-change CVs in Greenhouse where the parser pulled Skills into a jumbled list while Experience still said retail manager with no mention of SQL the candidate actually used for stock reports.

For how employer software sorts after upload, read why your resume never reaches a human so you separate parser failure from keyword mismatch.

Edge case: part-time bootcamp while employed full-time. List bootcamp dates honestly and keep the paid job as the primary employer block. Do not label yourself graduate developer while your header still shows head teacher unless the posting accepts that combo.

Edge case: career break for caregiving. One line in Profile is enough. Use Month Year on the gap if you were not employed. Do not hide the gap with a functional format that strips dates.

Spelling matters on public-sector and regulated tech roles. Set Word to UK English if you target UK employers exclusively. Mixing US spellings in a Manchester posting is a small tell that the CV is copy-pasted.

References upon request is optional in 2026. Drop the line to save space for a project link or certification with expiry date.

Certifications belong near Profile when the posting names them. AWS Cloud Practitioner or ITIL Foundation gets one line each with month and year passed. Do not list every Udemy course unless the req asks for continuous learning proof.

Before and after pairs for UK tech pivots

Each pair keeps the same facts. Only the framing changes. Paste the After shape, then swap tools and numbers you can defend on a call.

Pair 1: Teacher to junior developer

Before: Dedicated educator with passion for technology.
After: Junior Developer (target title) · Built a React attendance tracker used by 12 form groups; reduced manual registers 3 hours per week · GitHub link on its own line under Projects.

Pair 2: Retail manager to IT support

Before: Managed staff and handled customer complaints.
After: Resolved 40 plus daily POS and Wi-Fi tickets across 8 stores using Zendesk; escalated 6% to vendor Tier 2 with average first response under 15 minutes.

Pair 3: NHS admin to data analyst

Before: Responsible for clinic spreadsheets and reporting.
After: Built weekly clinic wait-time dashboards in Excel and Power Query, flagging 11% over-capacity slots before Friday board packs went out.

Pair 4: Military logistics to cloud support

Before: Led teams in high-pressure environments.
After: Coordinated kit readiness for 120 personnel; migrated inventory logs from shared drives to SharePoint with role-based access for 4 unit leads.

Pair 5: Finance analyst to business analyst

Before: Prepared management accounts and variance analysis.
After: Mapped order-to-cash steps with 5 ops stakeholders; documented 14 handoffs in Confluence that cut duplicate data entry on month-end invoices.

Copy-paste block: profile and header

[Target Title from posting] · [City], UK · [email] · [phone] · [LinkedIn URL plain text]

Profile
[Target Title] moving from [old sector] with [X years] using [tool from posting] on [real project or job duty]. Seeking [exact title] roles where [one skill from posting paragraph one] matters.

Core stack: [3 tools from posting, comma separated]

Experience
[Employer] · [City] · [Month Year] to Present
• [Transfer bullet with tool + outcome + scope number]
• [Second bullet tying old role duty to tech verb: documented, automated, triaged]
              

Run one posting through the block. Do not keep a generic profile and duplicate five times across applications. UK recruiters notice when the header says data analyst but bullet one still describes classroom behaviour policies.

When you need format context for hybrid roles, compare chronological vs functional resume choices and pick chronological with a strong profile, not a skills-only first page.

Before: Skills section listed Python, Java, C++, HTML, CSS, teamwork, communication.
After: Skills held five tools from the posting; Python and SQL appeared in two dated bullets under the current job with outcomes attached.

Pair 6: Hospitality supervisor to service desk

Before: Ensured guest satisfaction and managed rota.
After: Triaged 25 plus daily staff laptop and till issues; documented fixes in a shared OneNote runbook used by 3 shift leads during peak weekend service.

Date format: March 2022 to Present, not 03/22. Slashes confuse some parsers and look US-heavy on UK CVs.

Font: 10.5 to 11 pt Calibri or Arial. Fancy serif headers break when exported to PDF on Mac versus Windows.

Volunteer tech work counts when it is recent and scoped. Charity website rebuild for a local hospice belongs in Projects with hours per week noted. Vague volunteer work without outcomes does not replace paid transfer bullets.

Internal transfers inside a big employer still need a CV for external applications. Use the external target title even if your email signature still shows operations manager.

Contract and inside-outside IR35 roles: mirror the posting language on employment type in Profile if you accept both. Do not list every short contract on page one; group three similar contracts under one consultancy header if the work was continuous.

LinkedIn headline and CV header should match during a pivot month. Recruiters who find you on social then open your upload should see the same target title, not two different role names.

Degree title lines can stay even when the field is unrelated. Put the bootcamp or conversion course directly under Education with dates, not buried in Interests.

When the posting asks for right to work, answer in the application form only. Do not paste passport details into the CV body.

What weak career-change CVs share

Old job title still in the header. The parser and the human both assume you're staying in that lane. Change the header before you tweak fonts.

Skills cloud with no Experience proof. Listing Kubernetes in Skills while every bullet mentions lesson planning trains neither ATS nor recruiter to believe the pivot.

Two-column Canva exports. Workday reads columns out of order. Employer names land under the wrong dates. Use Word or Google Docs single column, then PDF.

Personal statements that repeat the job ad. Three lines on agile mindset without a ticket count or repo link waste page one space.

Before: Uploaded the same PDF to forty roles with only the cover letter changed.
After: Changed header title and first bullet per posting family; kept a master file with tracked variants.

This will not make you qualified for staff engineer roles on six months of coursework. It stops a credible pivot CV from dying because the file still reads like your last industry.

Listing every soft skill in caps. COMMUNICATION and TEAMWORK in Skills without tickets or stakeholders attached reads like filler. Move proof into bullets or delete the skill.

QR codes and icon rows. Parsers skip graphics. Plain URLs for GitHub, portfolio, or LinkedIn on their own lines under the header.

Objective statements about growth. Replace with Profile lines that state target title and one measured outcome from your last role.

Before: Attached a Europass CV with checkboxes for language levels.
After: Used a UK-style chronological layout with English listed as native and one line for conversational Spanish if the req mentions multilingual support.

Check parse before the UK portal upload

Tailoring beats volume. Open one UK tech posting, highlight three must-have tools, then adjust header and two bullets before you export.

Keep the job description visible while you edit. Highlight nouns in the first paragraph of the req. Those nouns belong in bullet one or two, not only in a cover letter you write later.

Paste the posting into score your job match when the title is a stretch. Skip roles that need five years in a stack you have not touched yet. Save the sprint for adjacent pivots.

After edits, run the free ATS checker on the DOCX or PDF you will upload. Fix scrambled sections before you attach the same broken file to three companies.

Ship one tailored UK tech CV tonight

A UK CV for career changers in tech is not a longer version of your old CV. It is the same work history with a new title, tool-first bullets, and a file format parsers can read.

• Header matches the posting title string.
• Two transfer bullets carry stack keywords with outcomes.
• Single column, Month Year dates, no photo block.
• Checker pass on the exact upload file.

Run a free ATS check after you rewrite bullet one. Small wording changes can move a keyword from an invisible Skills blob into Experience where recruiters look.

Keep one master CV and save a new file per posting family so you do not lose the version that finally parsed cleanly in Workday.

And when a recruiter replies, note which bullet they asked about. That line becomes the template for your next pivot CV, not the generic profile you started with.

If you are also targeting US remote roles from the UK, keep a separate file with US spelling and one-page discipline. Mixing formats on one CV satisfies neither market.

Save the posting PDF or screenshot when you tailor. When HR calls six weeks later, you will remember which variant you sent.

Night owls and shift workers: block thirty minutes after one posting review, not a four-hour rewrite marathon. One solid tailored CV beats four half-finished exports sitting in Downloads.