10 min read · phased Workday prep for UK IT CVs
Your CV can look sharp on a MacBook and still arrive in Workday as an empty experience grid. UK IT candidates love tidy two-column layouts with a skills rail, and that's exactly where parsing breaks. Workday reads top to bottom like a typewriter, not like a portfolio site, so don't trust the on-screen preview alone.
Check your resume for free on the exact file you'll attach. Guessing from how Word looks on screen wastes applications to banks, scale-ups, and consultancies that all run the same stack.
Below is a phased timeline you can run in one evening: audit, strip layout traps, normalize UK IT sections, tune keywords, then verify the parsed preview. Job searching is draining enough without sending a fifth upload of the same broken export.
Quick Wins
- Paste the PDF into Notepad. If skills appear before your current employer, reorder sections.
- Write dates as Sep 2019 – Aug 2022 on one line per role, not DD/MM/YY slashes.
- Move Kubernetes and Terraform from a sidebar into bullets under the job where you used them.
- Export from Word or Google Docs, not from a flattened design PDF.
What Workday pulls from a UK IT CV upload
Symptom one: blank employer list. You uploaded a PDF with a coloured header and a GitHub icon row. The parser treated the band as one line and skipped job blocks sitting in a right-hand column.
Symptom two: jumbled dates. Contract roles listed as "Q3 2023" or "2023/24" often land in title fields while end dates stay empty, which makes tenure look like a typo to a coordinator scanning grids.
Symptom three: tools without roles. You listed AWS, Python, and React in a table under Technical skills. Keyword search still works, but the recruiter view shows stacks disconnected from the platform job where you shipped them.
Workday is filling database columns so hiring teams can filter on employer, title, and years. UK CV customs like Profile instead of Summary are fine when the word is plain text, not a logo saved as an image.
I've opened Workday next to a candidate's PDF and watched a senior backend role show as Unknown company because the employer name sat inside a text box beside a logo. The human CV was fine. The parsed row was empty.
Right-to-work and sponsorship answers live in the form, not in your CV file. A clean parse does not override a hard knockout on visa status. It does stop qualified UK and EU-settled engineers from disappearing before anyone reads bullet one.
Remote UK roles use the same parser. City in a footer text box can vanish from the location column hiring managers skim before they open the attachment.
Workday ATS resume optimization UK IT CVs: phased timeline
Run these phases in order. Don't skip to keywords while columns are still shuffling your timeline.
Phase 1: Plain-text audit (about 15 minutes)
Export or copy your current CV. Paste all text into a plain notes app. Read top to bottom without formatting. If your university name appears before your current employer, your file order is wrong even if the PDF looks elegant.
Note missing employers, duplicated phone lines, and bullets that merged into one paragraph. That list is your fix sheet for tonight.
Phase 2: Strip layout killers
Before: Name and contact left, skills and certifications right, jobs in the centre column.
After: Single column top to bottom: contact, profile, experience, education, skills as a short list or woven into bullets.
Remove tables used only for alignment, text boxes, skill bars, and employer logos typed as images. Replace four-column employment tables with repeated blocks: employer line, title, dates, bullets.
Phase 3: UK IT labels and dates
Use Experience or Work history, Education, and Skills as plain headings. Write Sep 2019 – Aug 2022 instead of 09/19–08/22. Slashes invite misreads across US and UK tenant settings.
For contract work, spell it in the title line: Backend Engineer (Contract) so humans and keyword rows align. Degree classification belongs once under Education, not in a nested module table that chokes parsers.
Phase 4: Match the posting without renaming yourself
Mirror title words from the req in your top role line when they're accurate. Put must-have stacks in Skills and in one dated bullet under the job where you used them. Keyword stuffing in a footer still parses as footer junk.
Pair this with how ATS interprets role names so you don't invent a senior title you haven't held.
Phase 5: Export once and preview in Workday
Rebuild in Word or Google Docs with styles, not absolute positioning. Export .docx or text PDF per the careers page. Upload, then open any parsed preview the site offers. If experience fields are empty, fix structure and re-export before you submit.
Before: Phone number inside a header shape on a designed PDF.
After: Name, phone, email, and city on the first lines of the body; header area cleared.
Copy-paste block: UK IT experience entry
Copy-paste CV block (edit brackets)
[Employer name], London, UK
[Job title] | Sep 2021 – Present
• Built payment APIs in Java 17 and Spring Boot on AWS EKS
• Cut p99 latency 18% after tracing bottlenecks in Datadog
Skills
Java, Kotlin, AWS, Kubernetes, PostgreSQL, Terraform
Phase 6: Log the version you sent
Name the file with date and role: FirstLast_PlatformEngineer_Workday_2026-10-08.pdf. One line in a spreadsheet beats guessing which export cleared the checker when a recruiter emails six months later.
This will not fix applying to principal roles with two years of experience. It stops your real timeline from vanishing before anyone judges fit.
UK IT layout habits that parse badly in Workday
GitHub and portfolio links as icons only. Type the URL on its own line. Parsers skip icon fonts that humans recognize instantly.
Competency bars for languages. They're shapes, not text. Replace with one line: "Python, Go, TypeScript, SQL."
Before: "Curriculum Vitae" as giant WordArt.
After: Your name as the only large line, plain text.
Listing every cloud cert in a nested table. Put cert name and year on one line under Education or Certifications. Tables inside tables are a common failure mode for platform engineers coming from contractor templates.
Do not password-protect PDFs. Do not upload phone photos of signed paper CVs. And don't reintroduce columns because Word "looks empty" after you flatten the design.
For broader parser behaviour, read why Workday resumes look different after upload and compare with the UK IT symptoms above.
Test the file you'll attach before Workday stores it
Layout work stays guesswork until you run the same bytes through a checker. You want missing headings and garbled order flagged on your machine, not by a coordinator closing the req.
Paste the job description into score your job match after you tune bullets for the stack in the posting. Parsing gets you into the grid; match language gets you read.
Run the free ATS checker on the PDF or .docx you plan to upload. Fix structure first, then tweak keywords.
Do this now: Export a single-column version, paste it into Notepad, and confirm your current employer appears before your university name. If it doesn't, reorder sections before you apply again.
Store two files if you must: a visual PDF for networking and a Workday export for applications. Never upload the pretty one by muscle memory at midnight.
Upload-night checklist for UK IT Workday applies
Workday ATS resume optimization UK IT CVs is mostly subtraction across a short timeline. Remove columns, tables, and icons until a plain-text read still tells your career story.
- Single column, experience before education unless you're a current student.
- Month-year dates on their own line under each title.
- Stacks spelled out in bullets tied to employers, not only in a rail.
- Checker pass on the exact upload file, then Workday preview read.
Generate a cover letter when the role asks for one, then run a parser-friendly rebuild if your template keeps failing the Notepad test.
When silence continues after a clean parse, the issue may be level, clearance, or visa filters, not formatting. At least you'll know recruiters saw the same employer line you see on paper.
Read more
Frequently asked questions
Use the format the careers page lists. When both are allowed, start with a .docx export from Word or Google Docs with a single column and no text boxes. If only PDF is accepted, export a text PDF from the same plain source, not from a design tool. Re-open the Workday preview after upload and confirm employer names populated before you submit.
Page count is fine. Column count is not. A two-page CV with a left skills rail can dump your current role into a skills bucket while dates stay empty. Keep experience in one vertical column across both pages and put tools inside bullets under each job.
No. Sidebars parse early and break reading order. List core stacks once under Skills or weave them into dated bullets. A parser that reads Python before your employer name still stores both, but recruiters sorting by company see a jumbled timeline.
Contact strips built with tables, icons, or header text boxes confuse field detection. Put name, city, phone, email, and LinkedIn URL on separate plain lines at the top of the body. UK numbers with a leading zero stay on one line, not split across columns.