12 min read
You're not stuck because you lack years. You're stuck because the req asks for Terraform and on-call ownership and your CV still opens with "responsible for ticket resolution" while AWS lives in a sidebar the import skipped.
You don't need a brand-new CV for every advert. You do need a master file and a saved variant per stack family so you're not editing from scratch at midnight.
Mid-level IT in the UK means you've got enough roles that generic files look lazy. Recruiters compare you to contractors who mirror the posting title in line one. Before you rewrite tonight, check your resume for free with the job text pasted in. You're checking whether must-have terms appear inside dated Experience, not whether your master CV still reads well on PDF.
Targeted customization sounds like busywork. It's not. It's moving real delivery proof into the lines Greenhouse and Workday read before a human opens the attachment. Job hunting while you're still billing on a contract is exhausting. This page is a short procedure, not a motivational poster.
After bullets align, generate a cover letter that names one production outcome from bullet one. The letter won't rescue a CV that never matched the stack list.
Quick Wins
- Highlight must-have stack terms before you touch fonts.
- Mirror the posting job title when it's honest for your level.
- Put each tool in a bullet under the employer that used it.
- Save one tailored PDF per req with a clear filename.
What job match means on a UK mid-level IT CV
Job match means every required tool in the posting has a dated bullet that names how you used it, not a repeat in Skills alone. Mid-level candidates already own delivery, incident response, and cross-team work. The filter is whether your file says that in vocabulary the req already uses.
UK employers run Greenhouse, Workday, Teamtailor, and local boards with similar imports. The preview pane shows employer, title, dates, and the first lines of each block. If Kubernetes only appears in a logo row, the recruiter search for "Kubernetes" may miss you even when you run clusters daily.
Targeted customization is not copying the job description into your summary. It's choosing which three bullets prove the must-haves and demoting unrelated wins. A platform req doesn't need your oldest PHP maintenance story unless the posting asks for legacy support.
Contract and permanent CVs follow the same match rules. IR35 labels and agency names stay truthful on the timeline. Tailoring adjusts language and bullet order, not employer history.
Brevity helps when it removes noise. UK CVs can run two pages at mid-level if every line carries stack or scope. Cut duplicate certifications and old university modules before you cut the bullet that proves the cloud vendor in the ad.
For how parsers tie keywords to sections after layout is clean, read how ATS matches resumes to job descriptions . Match work fails when the file never imported your Experience block intact.
Job match tailoring tips for UK mid-level IT CVs: five steps
Step 1: Build a must-have list from the posting
Open the req and copy required languages, platforms, and practices into a scratch column: tool, your proof, one-line outcome. Empty cells mean you skip the apply or you lead with adjacent proof and address the gap honestly in a cover note, not a fabricated project.
Ignore vague "passion for technology" lines until hard requirements are covered. Nice-to-have tools get one mention only when you used them in the last three years.
Step 2: Audit import order on your master CV
Upload your current PDF to a checker and read what order sections land. If Skills import before Experience, your sidebar layout is fighting match work. Rebuild single column before you swap synonyms.
Before: Two-column CV with Azure icons in the right rail; top bullet says "Supported application teams."
After: Single column; first bullet under current employer: "Owned Azure App Service deploys for three .NET APIs, cut release rollback time from 40 to 18 minutes using GitHub Actions gates."
Step 3: Rewrite headline and summary for this req
Your headline can mirror Platform Engineer when the posting says Platform Engineer and your last two roles support that scope. Don't claim Principal. Summary gets two sentences: target role plus one metric tied to a must-have tool.
Before: IT professional with broad technical experience seeking new challenges.
After: Platform engineer with five years of AWS and Terraform delivery for regulated SaaS. Last role cut P1 incidents 22% by adding Datadog SLO dashboards and runbook links in PagerDuty.
Step 4: Tailor the top two role bullets
Under your current employer, lead with the stack the posting repeats. Add one scope number inside the bullet as illustration of your delivery, not as a claim about hiring odds.
Before: Worked on microservices in an agile team.
After: Migrated four Java services to Kubernetes on EKS with Helm, pairing with security on pod policy templates that passed SOC 2 evidence reviews in Q1 2025.
Second bullet can carry soft must-haves: on-call, code review, stakeholder updates. Name the audience: product, support, or compliance.
Step 5: Export, score, save a role file
Export PDF from Word or Google Docs without text boxes. Filename: Firstname-Lastname-Company-Platform-Engineer.pdf. Run match score against the posting, fix gaps in bullet one, store that version for one application only.
I've screened UK mid-level platform files in Greenhouse where the summary listed every AWS service but no bullet showed ownership. The match win is always the first Experience line that repeats the posting stack in plain text.
Copy-paste block: tailored bullet skeleton
Current Employer | City
Job Title (contract label if true) | Month Year to Present
- [Posting tool] + [scope verb] + [system count or user count] + [outcome phrase with Month Year if relevant]
- [Second must-have] + [stakeholder] + [evidence type: runbook, dashboard, pipeline]
Skills (plain comma list, only tools defended above)
AWS, Terraform, Kubernetes, Python, Datadog, GitHub Actions
Edge case: you're strong in .NET but the req leads with Go. Lead with the closest production proof, add a small Go repo or internal tool line if true, and don't rename your stack history.
Edge case: hybrid role mixing hands-on and line management. Keep one bullet on people scope and two on technical delivery when the posting weights both. Don't drop incidents entirely for meeting counts.
If imports scramble after tailoring, read can ATS read PDF resumes before you spend another hour on synonyms.
Where UK mid-level IT tailoring goes wrong
Keyword stuffing in Skills without bullets. Fifteen tools with zero proof reads hollow in human review and misleads match tools.
One master PDF for every stack. Backend, data, and SRE reqs need different top bullets even when the employer list stays fixed.
Renaming job titles. Translate scope in the summary; keep honest titles on the employer row for background checks and LinkedIn.
Chasing senior reqs with mid-level proof. Tailoring won't add staff-level architecture scope you haven't shipped. It stops qualified mid-level files from dying on vocabulary mismatch.
Before: Summary pastes three sentences from the job ad; Experience bullets still describe 2019 desktop support.
After: Summary names target role and one metric; top bullets show cloud and on-call work from the last two roles.
Before: GitHub link hidden in a footer image; parser never stores it.
After: Plain URL on its own line under Projects or Contact when the posting asks for portfolio review.
Applying to ten reqs with one export and blaming the market is a process problem. Ten tailored top folds take less time than ten silent rejections you can't debug.
Don't hide contract gaps with fake freelance blocks. Recruiters and compliance teams compare timelines. Condense old roles; don't invent employers.
Certifications belong under a clear heading with Month Year completion. Three acronyms with no delivery story belong lower on the page than a bullet that names how you used the skill in production.
And if you're tailoring for a public-sector req, spell frameworks exactly as the ad does when you truly used them. Don't swap GDS language for private-sector buzzwords when the posting is explicit.
Soft skills still matter when the posting names them. If the ad asks for stakeholder updates, write one bullet that names the forum: weekly ops review, CAB, or product trio. That's match language too, not only Terraform and Python.
Keep a short log of which tailored file went to which company. When a recruiter calls back six weeks later, you'll know which bullet set they read and won't accidentally send a backend variant for a data platform follow-up.
When you're between contracts, lead with the most recent delivery role even if it was shorter. Mid-level screens care about recency of stack more than a long gap between jobs you already explain honestly.
If the posting lists security clearance or nationality constraints you can't meet, don't burn tailoring time on match work. Save the hour for reqs where your timeline and stack already fit.
Score the tailored CV before upload
Upload your tailored export and paste the job text into HireFlow's free ATS resume checker . Confirm Experience imported in order and must-have terms sit in body text.
Then score your job match on the same posting. Close gaps in bullet one before you tweak font size. Match score shows missing terms; it doesn't replace honest proof.
Do this now: Highlight five must-haves, rewrite two bullets, export PDF, run checker plus match score, apply to one req with the saved filename.
What to do now
Pick one UK mid-level req you want this week. Run the five steps on your master CV, save a tailored PDF, and submit with a filename that tells you which stack you matched.
- Highlight must-haves before design tweaks.
- Mirror the job title when it's accurate.
- Prove each tool in dated bullets.
- Export single-column PDF and re-scan imports.
- Score match, then apply once with the saved file.
Open the posting. Run a free ATS check on the export you plan to upload, fix missing must-haves, and send one clean application.
Read more
Frequently asked questions
Keep one master CV with honest employers and Month Year dates. Per application, swap the headline line, reorder two bullets under your current role, and mirror three must-have tools from the posting in those bullets. You are not inventing projects. You are moving proof the parser can read in the first screen.
Put each must-have tool in a bullet tied to the employer where you used it, ideally in the first eight words of bullet one under your current job. A Skills comma list is backup only. Sidebars and icon rows often import empty in Greenhouse and Workday, so body text carries the match.
Two pages is fine when every line proves scope. Tailoring means cutting old club lines and duplicate tool lists before you cut the project that matches the posting. A dense two-page file with single-column layout beats a one-page Canva template with tables hiding dates.
Reuse structure, not keywords. Two reqs both asking for Python still differ on cloud vendor, observability stack, or domain words like fintech or health. Re-read must-haves, swap three terms in the top bullets, export a new PDF, and run a fresh match check before the next upload.
Label contract work honestly on the employer row: Platform Engineer (via Bright Contracting Ltd, inside IR35) with Month Year dates. Match language still lives in bullets about delivery, on-call, and stack. Do not hide agency names that will appear on compliance checks. Tailor proof, not history.