Enhance CV guides
Resume and ATS guides
Practical writing and parse checks for Workday, Greenhouse, and the recruiter who opens the file next — with examples you can use today.
Writing a resume
How to write a resume that a parser and a recruiter both finish
A practical way to write a resume that a parser can map and a recruiter can finish: one job, one column, and bullets that prove the work.
Read the guide
Format and templates
Resume format: the layout ATS software actually maps
A resume format that parsers can map: one column, real headings, dates next to each job, and no decorative traps that hide contact data.
Read the guide
Format and templates
Resume templates that survive an ATS parse
How to choose a resume template that survives Workday and Greenhouse: one column, real headings, and no design that hides your email.
Read the guide
Writing a resume
Resume examples: copy the structure, keep your facts
Resume examples you can adapt: structure, before-and-after bullets, and the mistakes that happen when you paste someone else’s metrics.
Read the guide
ATS and parsers
ATS resume: what the software extracts before a human looks
What an ATS resume actually is: extraction, not a keyword pile. How Workday, Greenhouse, and Taleo drop email — and the layout that keeps it.
Read the guide
Comparisons
Resume vs CV: send the document the country actually reads
Resume vs CV is a country and purpose choice. Tables for US, UK, EU, and academic files — plus what ATS software can still extract.
Read the guide
Writing a resume
Cover letter: add proof the resume cannot hold
A cover letter that adds proof the resume cannot hold: length, structure, and what Workday and Greenhouse actually store.
Read the guide
Writing a resume
How to write a cover letter without rewriting your resume
A practical cover letter playbook: opening, proof paragraph, close, plus what paste fields in Workday actually keep.
Read the guide
Resume sections
Resume skills: list them where the parser looks
How to build a skills section that Workday can index and a recruiter can scan: grouped nouns, proof in bullets, and no skill bars.
Read the guide
Resume sections
Resume summary: four lines that tell the parser who you are
A resume summary that a parser can file and a hiring manager can repeat: role, scope, proof — written after the bullets exist.
Read the guide
Resume sections
Resume objective: use it only when a summary would lie
When a resume objective still earns the header: first jobs, pivots, and tiny ATS fields — plus the lines that waste a parse.
Read the guide
Career stage
Resume with no experience: prove work without inventing a title
A first resume from projects, shifts, and volunteer desks: honest proof that still parses in Greenhouse and Workday.
Read the guide
Format and templates
One-page resume: default for early career, not a forever rule
When a one-page resume is the right default, when two pages in Workday is honest, and how recruiters actually skim length.
Read the guide
Resume sections
Resume action verbs: start the line with the work, not the team
Action verbs that survive a parse: lists by function, plus the empty openers that make Greenhouse bullets look unfinished.
Read the guide
ATS and parsers
Resume keywords: mirror the ad for work you actually did
How to match resume keywords to a posting without lying: overlap Workday and Lever can score, and stuffing that backfires in a screen.
Read the guide
ATS and parsers
Tailor a resume to the job without rewriting your history
A 20-minute way to tailor a resume to one posting: map the ad, swap shared nouns, keep the history honest, then parse-check the file.
Read the guide
ATS and parsers
Workday resume format: headings the parser is built to find
Workday maps Experience, Education, and Skills from plain headings. Two-column PDFs, text boxes, and the fields it still makes you retype.
Read the guide
ATS and parsers
How to pass ATS: be readable first, then relevant
Passing ATS is parse plus keywords plus complete sections. A checklist for Workday, Taleo, and iCIMS — without adding skills you cannot defend.
Read the guide
Resume sections
Resume bullet points: one result per line, in the text layer
Turn duties into bullets a recruiter can scan and an ATS can store. Formula, examples, and the lines Greenhouse treats as noise.
Read the guide
Career stage
Career change resume: reframe the past, do not erase it
A career-change resume keeps true history and reframes transferable work. Hybrid layout, skills bridge, and ATS heading rules.
Read the guide
Career stage
Student resume: lead with proof you already have, not a fake job
A student resume ranks education and projects without padding. Campus jobs, labs, and the ATS headings Greenhouse still expects.
Read the guide
Career stage
Internship resume: treat each placement like a real job block
Internships are short. Make each block parse: dates, team, tools, and one number. What Workday does with Intern titles on the application.
Read the guide
Role resumes
Nursing resume: put the license and the unit where parsers look
A nursing resume that Workday can file and a nurse manager can finish: license, unit, ratios, and the EHR in the text layer.
Read the guide
Role resumes
Teacher resume: certification and grade band in the text layer
A teacher resume that a district ATS can file and a principal can finish: certification, grade band, and outcomes in the text layer.
Read the guide
Role resumes
Software engineer resume: stack in Skills, proof in Experience
A software engineer resume that Greenhouse can file and a hiring manager can finish: stack in Skills, proof in Experience.
Read the guide
Format and templates
Resume length: enough proof to parse, short enough to finish
How long a resume should be: enough proof to parse, short enough that a hiring manager finishes it on a phone.
Read the guide
Comparisons
Chronological vs functional: parsers still want dates and employers
Chronological vs functional: parsers still want dates and employers. Hybrid keeps both search and a human’s trust.
Read the guide
Career stage
Employment gaps: date them, name them, then return to results
Employment gaps: date them, name them in one line, then return to results. Parsers want the graph; humans want a plain sentence.
Read the guide
Comparisons
PDF vs Word: upload the file the ATS on that page can parse
PDF vs Word is not a brand choice. It is which extract Workday, Greenhouse, or an inbox will keep.
Read the guide
Format and templates
Resume fonts: pick a typeface the PDF still treats as text
Font choice is a parse problem first. Use a typeface the PDF still treats as text, size it so a phone can read it, and leave branding for the portfolio.
Read the guide
Resume sections
Resume headline: put the job title you want parsed
A resume headline is the job you want parsed, not a personal motto. One line, real title, still in the text layer.
Read the guide
Resume sections
Professional summary examples: edit the facts, keep the shape
Eight professional summary shapes by career stage. Keep the structure, change the facts, and leave slogans out of the Workday file.
Read the guide
Resume sections
Education on a resume: one heading, real dates, no icon diplomas
Education on a resume is one heading, honest dates, and no diploma icons. Move it below experience once the work is the stronger proof.
Read the guide
Resume sections
Work experience: one block per job, dates a parser can sort
Work experience is one block per job and dates a parser can sort. Title, employer, city, then bullets that prove this posting.
Read the guide
Resume sections
References: keep them off the resume unless the form demands names
Most ATS files should skip references. Keep a private list, and only add names when a form or a school process actually demands them.
Read the guide
Resume sections
Hobbies: keep them only if they evidence a skill in the ad
Hobbies help when they evidence work. One line that names a real skill beats a list of generic weekend sports that Workday ignores.
Read the guide
ATS and parsers
Two-column resumes: pretty to people, chaotic to parsers
Two-column resumes look finished and parse in the wrong order. How Workday, Greenhouse, and Taleo read sidebars — and the one-column layout that survives.
Read the guide
Resume sections
Achievements: change the line only where you have a real result
Achievements are rewritten bullets, not a separate section. How to swap duties for proof Workday can store — without fake percentages.
Read the guide
Role resumes
Customer service resume: name the tools and the numbers you have
Retail, BPO, and in-house support resumes that parsers keep: named tools, real ticket volume, and CSAT only when you saw the report.
Read the guide
Role resumes
Project manager resume: scope and tools in the text, not in icons
PM resumes that survive ATS search: scope as budget and headcount, stakeholders as dates plus deliverables, Jira in Skills — no slogan headlines.
Read the guide
Role resumes
Data analyst resume: tools in Skills, decisions in Experience
Analyst resumes that parse: SQL in Skills, dashboards and queries as proof in Experience, GitHub as a URL — not as a substitute for dates.
Read the guide
Comparisons
LinkedIn vs resume: same facts, different jobs for each document
LinkedIn is not an ATS. Align titles and dates with the Workday file, then use the extra profile space for proof the one-page resume cannot hold.
Read the guide
Writing a resume
How to write a CV: complete history, still in a parseable layout
How to write a CV for UK and EU hiring: two-page job CVs, academic CVs, personal statements, and what still breaks when you paste the file into Workday.
Read the guide
Resume sections
CV personal statement: five lines of proof, then standard headings
Write a UK personal statement as five lines of proof for one job, then keep standard headings so Workday and Greenhouse can still file you.
Read the guide
ATS and parsers
ATS resume checker: score the text layer, then the job match
What an ATS checker can and cannot score, how Enhance CV reports gaps without a fake pass mark, and why Workday still needs a human check.
Read the guide
Comparisons
Objective vs summary: pick the one that does not waste the header
Objective vs summary: pick the opener that does not waste the header, with side-by-side rewrites and Workday field limits.
Read the guide
Writing a resume
What to put on a resume: enough for a parse, nothing that burns space
A practical inventory of what belongs on a resume, what to skip, and what Workday already collects in the form so you do not burn the first page.
Read the guide
Format and templates
Google Docs resume: start simple, export a text-based file
Which Google Docs resume layouts still keep a text layer, why columns and text boxes flatten in Workday, and how to export before you apply.
Read the guide
Career stage
Mid-career resume: recent proof first, older jobs in one line
How to edit a mid-career resume down: recent proof first, older jobs in one line, and the dates Workday still needs.
Read the guide
ATS and parsers
Upload to Workday: parse, then read every autofilled field
How to upload a resume to Workday: parse, then audit every field. File type, old attachments, and the errors that duplicate jobs.
Read the guide