11 min read
Your old job title isn't the problem. The CV shape is. UK tech career changers get filtered out when transferable work sits in a Skills list while Workday scores the Experience section you left in retail vocabulary. The fix isn't stuffing twenty posting keywords into a sidebar. It's a hybrid layout: short profile, dated proof bullets under a Relevant Projects block, then trimmed chronological history with honest titles.
Before you rewrite bullet one, check your resume for free against a UK tech posting you actually want. You'll see whether the importer reads your current role first or drops your bootcamp block into a footer field Greenhouse never shows recruiters.
Switching industries is already draining. You don't need a lecture on passion. The career change CV examples UK tech hiring teams pass around internally all use the same hybrid shape, and the pairs below show why. Steal structure from your previous industry, not wording from a template factory.
And if you're wondering whether a two-page CV's even allowed in the UK market, yes for most career changers with ten-plus years elsewhere. One page only works when every line on it points at the target stack.
Quick Wins
- Move bootcamp or side-project proof into a dated block above unrelated job history.
- Rewrite bullet one under each role so the first eight words name a tool from the posting.
- Keep official old titles; change bullet verbs, not employer records.
- Export single-column DOCX before PDF; tables and icons break UK Workday imports.
What UK tech recruiters compare your career-change CV against on a first scan
Recruiters are not grading your career story. They're checking whether bullet one proves the stack in the Greenhouse req and whether the file imports without scrambling dates. Career changers lose on structure before they lose on experience.
The bar is boring on purpose. Four-line profile naming target role and core stack. Relevant Projects or Selected Experience with month-year ranges. Last two non-tech roles cut to three bullets each, rewritten with tools. Education and certs at the bottom, not the top. No photo, no national insurance number, no decorative columns.
Generic template CVs online push a keyword cloud in a Skills section. That reads fine to humans skimming PDFs. Parsers often score keyword hits inside Experience first. When Python only appears in a Skills grid and your bullets still say "handled customer queries," the file sorts below a weaker candidate who wrote one Django line under a dated project.
Edge case one: you're returning after parental leave and your last tech-adjacent work is three years old. Pull the strongest project forward with dates, trim the gap explanation to one profile line. Edge case two: you're on a skilled worker visa and the posting asks for right-to-work. Answer in the application form, not a half-page CV footnote that pushes page two off screen. Edge case three: you're targeting fully remote UK roles from Scotland or Wales. Keep city on the header; remote does not mean location-blank.
When the parser keeps mangling your file before you edit content, read how ATS matches resumes to job descriptions first. Structure only helps after Experience imports in the right order.
Career change CV examples UK tech: before/after pairs by previous role
Each pair fixes one shape mistake. Copy the layout, swap in your tools, employers, and month-year dates. UK format: March 2022 to Present, not 03/2022.
Secondary teacher to junior software developer
Posting wants Python, Git, and teamwork on a junior dev squad in Manchester. You've completed a part-time bootcamp while teaching.
Before: Headline Teacher. Skills list says Python, JavaScript, problem solving. Bootcamp mentioned in a paragraph under Personal Statement. Experience bullets describe lesson planning and parent evenings.
After: Profile: Junior developer candidate with Python and Git project work; former teacher with curriculum documentation habits. Relevant Projects: Attendance Tracker, Python Flask, January 2024 to June 2024. Built REST API for form submissions; deployed on Render with GitHub Actions test runs. Experience: Secondary Teacher, Oakwood Academy, Leeds, September 2018 to July 2024. Documented scheme-of-work changes in shared Google Docs used by six departments; reduced duplicate planning prep across terms.
Retail supervisor to IT support analyst
Posting lists Active Directory, ticket queues, and SLA targets for a Bristol fintech helpdesk on Workday.
Before: Retail Supervisor title with bullets about sales targets and stock counts. IT interest mentioned in hobbies. Skills column lists Windows and customer service.
After: Profile: IT support candidate with ticket-queue experience from retail systems escalation. Relevant Experience: IT Support Volunteer, Community Hub Leeds, October 2023 to March 2024. Reset passwords and mapped printer faults in Active Directory for 40 users; logged cases in Zendesk with same-day closure on 88% of tier-one tickets. Retail Supervisor, CityMart, Leeds, June 2019 to September 2023. Escalated POS outages to head-office IT with ticket IDs; cut average downtime per incident from 45 to 20 minutes across FY 2023.
Chartered accountant to data analyst
Posting wants SQL, Power BI, and stakeholder reporting for a London insurtech team on Greenhouse.
Before: Audit Senior bullets list client portfolios and compliance deadlines. Skills section repeats SQL and Power BI with no project line. Two-page CV with every audit client named.
After: Profile: Data analyst candidate with SQL modelling from audit analytics work. Selected Experience: Management Accountant, Northbridge LLP, London, April 2020 to Present. Built Power BI churn view on SQL warehouse extracts for three product lines; flagged £1.4M renewal risk before Q3 board pack. Earlier audit roles trimmed to two bullets each focusing on Excel automation and SQL reconciliations, not client logos.
Marketing executive to product analyst
Posting stresses SQL, experiment readouts, and roadmap input for a SaaS scale-up in Edinburgh.
Before: Marketing Executive with campaign reach metrics only. Product interest in a cover letter, not the CV. Skills list says analytics without tool names in bullets.
After: Profile: Product analyst candidate with funnel experiment ownership from B2B marketing. Marketing Executive, BrightLayer, Edinburgh, May 2021 to Present. Ran A/B tests on trial signup flow in Mixpanel; lifted activation 12% after copy change shipped with engineering in Jira. Built weekly SQL pull for pipeline stages used in product standups; replaced manual spreadsheet with one Looker view the PM team still opens Mondays.
NHS healthcare assistant to healthtech implementation specialist
Posting wants EHR workflows, training delivery, and clinical stakeholder management for a Leeds vendor parsed in iCIMS.
Before: Healthcare Assistant bullets list ward tasks only. Healthtech goal in personal statement. No software named except generic IT literacy.
After: Profile: Healthtech implementation candidate with ward workflow and trainer experience. Healthcare Assistant, St. Mary's Trust, Leeds, March 2019 to Present. Trained four new starters on electronic observations charting each quarter; cut documentation errors on handover sheets. Completed vendor super-user sessions for patient tracking module; wrote quick-reference steps nurses used during go-live week.
Civil engineer to technical business analyst
Posting wants requirements workshops, process maps, and SQL for a infrastructure software firm in Birmingham.
Before: Civil Engineer CV with CAD and site supervision only. BA interest shown by online course list with no dated outcomes.
After: Profile: Business analyst candidate with requirements capture from multidisciplinary builds. Civil Engineer, Meridian Structures, Birmingham, June 2017 to Present. Ran client workshops for scope changes on £8M bridge package; logged decisions in Confluence for legal and finance sign-off. Mapped as-built inspection steps into swimlanes the PMO reused on two later tenders; reduced rework RFIs in Q2 2024.
Edge case: career break then bootcamp graduate
You stepped out in 2022, finished a full-stack bootcamp in 2024, and you're targeting junior roles in London.
Before: Career break explained in a half-page paragraph at the top. Bootcamp projects listed without dates. Pre-2022 marketing job with five bullets.
After: Profile one line on return-to-work and stack. Relevant Projects block first with month-year spans. Pre-break marketing role cut to two bullets with transferable tooling only. Break mentioned once in profile, not repeated in every section header.
Copy-paste block: hybrid career-change CV skeleton
[Full name] · [City], UK · [Phone] · [Email] · [LinkedIn URL]
PROFILE (4 lines max)
Target role from posting + core stack + one honest bridge line from last industry.
RELEVANT PROJECTS or SELECTED EXPERIENCE
[Project or bridge role] · [Stack] · [Month Year] to [Month Year]
• Bullet 1: verb + tool from posting + outcome with number.
• Bullet 2: deployment, users, or time saved.
PROFESSIONAL EXPERIENCE (trim older roles)
[Official title] · [Employer] · [City] · [Month Year] to [Month Year]
• Bullet rewritten: same work, tool vocabulary from target posting.
• Max 3 bullets per non-target role.
EDUCATION & CERTIFICATIONS
Bootcamp, degree, or cert with month-year completion.
RULE: Every posting keyword you care about must appear in a dated bullet, not only in Skills.
Fill the skeleton before you polish adjectives. I've screened career-change files in Workday where the Skills column matched the posting and Experience still read like hospitality, and the parser scored the wrong section.
For how far back to keep pre-change roles before they bury your projects block, see how far back your resume should go in 2026 . Trim ancient part-time jobs before you add bootcamp proof, or parsers drop your current project dates.
What weak UK career-change CVs share across every previous industry
Keyword stuffing in Skills without Experience proof. Twenty posting terms in a grid and zero in dated bullets reads as copy-paste. Fix: move three must-haves into project or role bullets with tools attached.
Renaming old titles into tech labels. Software Engineer for a shop floor role fails background checks. Fix: official title plus clarifier in parentheses only when accurate.
Bootcamp projects buried below unrelated jobs. Chronological purity hides your best proof on page two. Fix: hybrid block above history with real dates.
Two-column Canva layouts. UK employers on Workday often parse left-to-right across columns. Fix: single-column DOCX, 11-point Calibri or Arial, standard margins.
Personal statements that repeat the profile. Two narrative blocks at the top push Experience off the first screen. Fix: one profile, then proof.
Applying to three title families with one file. Developer, analyst, and support reqs need different bullet one lines. Fix: one master file, separate exports per family, not one keyword soup for all.
Exception: when a UK posting asks for a cover letter separately, keep the CV factual and put the narrative bridge there. Another edge case: contract roles through agencies often want a shorter one-page CV. Cut pre-2015 jobs entirely instead of shrinking font to fit ten roles.
Checker-test the hybrid shape before the next Workday upload
Paste a UK tech posting and your DOCX into HireFlow's free ATS resume checker . Confirm Experience imports with projects or bridge roles above older titles and must-have skills sitting in bullets, not only in Skills.
When the CV shape is fixed but you need a short employer-facing bridge, use the cover letter generator with the same posting. Name the target role in sentence one so the letter matches the profile line recruiters already saw.
Do this now: Rewrite bullet one on your bridge project, run the checker against one UK posting, export single-column DOCX, then upload once to the title family that scored highest.
What to fix tonight
Career change CV examples UK tech recruiters act on share one shape: profile, dated proof block, trimmed honest history. Keyword stuffing a Skills grid without moving tools into Experience is the fastest way to stay invisible in Greenhouse.
- Copy the hybrid skeleton and fill in one real project with month-year dates.
- Rewrite bullet one on your last non-tech role with a tool from the target posting.
- Cut duplicate personal statements and hobby sections that push proof to page two.
- Export single-column DOCX before PDF.
- Run the checker against one UK posting in your target title family.
Open the posting that fits your bridge project best. Run a free ATS check , confirm Experience imports with proof above unrelated titles, and send one focused file instead of a keyword cloud.
Read more
Frequently asked questions
Use a hybrid shape: a four-line profile, a Relevant Projects or Selected Experience block with dated bullets, then a shorter chronological history for older roles. Pure skills-based CVs dump keywords into a grid Workday often reads separately from Experience. Chronological-only CVs bury bootcamp proof under unrelated job titles. The hybrid keeps honest titles while letting transferable bullets sit where parsers score them.
Two pages is the ceiling for most mid-career changers. Page one carries profile, core stack, and the last two roles rewritten for the target family. Page two holds older employment trimmed to three bullets each, education, and certs. If you're under five years total experience, one page with a projects section beats padding. Recruiters in Greenhouse scroll less than you think; bullet one under your current role must name a tool from the posting.
Keep one master hybrid file and swap the profile line, reorder three bullets, and mirror posting vocabulary inside Experience. Do not maintain five unrelated CV versions with conflicting headlines. Workday stores one PDF per application; sending a developer CV to a data analyst req because you tweaked only the Skills list splits your proof. Tailor inside the target title family, then checker-test before upload.
Under a dated Relevant Projects or Selected Experience heading placed above unrelated job history, formatted like employment: project name, stack, month-year span, two bullets with outcomes. Never list projects only in a summary paragraph. Parsers import Experience blocks first; a paragraph at the top often gets skipped or parsed as contact noise. Link GitHub once in the header, not six times in prose.
Keep the employer's official title for honesty, then add a clarifier in the same line if the work maps to tech: Customer Service Advisor (CRM & ticketing). Do not invent Software Engineer for a retail job. Recruiters verify titles on background checks and LinkedIn. The fix is bullet language that names SQL, Zendesk, or Python with scope, not a cosmetic title swap that reads as mislabeling on the HR screen.