Timezone overlap is the constraint nobody puts in the job description
Why remote hires fail on hours rather than skills, how to calculate a workable overlap, and what to ask before you accept a role across eight zones.
Most advice about applicant tracking systems is written by people selling something. This is what the parsers actually do, what they do not do, and which changes are worth making.
An applicant tracking system is a database with a parser attached. When you upload a CV, the parser tries to split your document into fields — name, contact details, employers, dates, titles, education, skills — and writes them into rows. Recruiters then search and filter those rows.
The parser is the part that fails. It does not understand your career; it pattern-matches structure. A layout that looks organised to a human can be unreadable to it, and a plain document that looks unremarkable can parse perfectly.
The widely repeated claim that 75% of CVs are rejected by software before a human sees them is not supported by any published study, and most vendors deny their products auto-reject at all. The real damage is subtler: your CV parses badly, your fields land empty or scrambled, and you never surface in the recruiter search that would have found you.
Multiple columns are the most common failure. A parser reads in a single pass, and a two-column layout can interleave your job titles with your skills list, producing nonsense.
Text inside images is invisible. So are text boxes in some parsers, and headers and footers in others — which is where people most often put their phone number and email.
Tables are read inconsistently. Some parsers flatten them row-first, some column-first, and the result is different every time. Icons in place of labels remove the word the parser was looking for; a small envelope glyph instead of the word Email means the field may never be identified.
The summary is three lines at most. Name the role you want, your years in it, your specialisation, and one result. Skip the adjectives — "results-driven professional" tells a search index nothing and a recruiter less.
Experience bullets should open with a past-tense verb and end with a number. "Responsible for the checkout flow" is a duty. "Rebuilt the checkout flow, cutting drop-off 22%" is evidence. If you do not have a number, use a scale instead: how many users, how many engineers, how many markets.
The skills section is where keyword matching happens, so it should be dense and specific. List tools by name, not by category. "Cloud platforms" matches nothing; "AWS", "Terraform" and "Kubernetes" each match a search.
Parsers match vocabulary, not meaning. If the posting says "design system" and your CV says "component library", a keyword search will miss you even though you did the same work. The fix is to use their term once, in a sentence that is true.
Stuffing a list of unrelated keywords in white text at the bottom of the page is a trick from a decade ago. It is detected, it is embarrassing when the CV is opened, and it does not survive the first interview question.
A useful discipline: take the ten most repeated concrete nouns from the job description, and check that each one appears in your CV in a place where it is honest. If you cannot make it honest, that gap is real information about the fit.
A high parser score means your document is machine-readable. It does not mean you are the right candidate, and it will not rescue an application that is a poor match on substance.
Treat it the way you would treat spellcheck: an error you should not be losing to, rather than the thing that wins you the job.
Under ten years of experience, one page. Beyond that, two is normal and parsers have no length limit. What matters is that the first third of the first page carries your strongest evidence, because that is what a recruiter reads in the first few seconds.
Either works if the text is selectable. A PDF exported from a design tool as flattened artwork will not parse at all. If you are unsure, open the file and try to select a line of text — if you cannot, neither can the parser.
It depends on the country. In the US, UK, Ireland, Canada and Australia, leave it out; some employers discard CVs with photos to reduce bias exposure. In much of continental Europe it remains conventional. When applying internationally, the safer default is no photo.
The CV builder runs the nine parser checks described here automatically, and rewrites weak lines with you. Free, no card.
Why remote hires fail on hours rather than skills, how to calculate a workable overlap, and what to ask before you accept a role across eight zones.
The three ways to pay someone in a country where you have no company, what each costs, and the misclassification risk that catches small teams out.
Location-based pay bands, how to find the real range, and the arguments that actually move an offer for a distributed role.