Maintenance
Part of Resumes and cover letters for people who want the details
Resumes and cover letters employers: why they read a resume three times
Employers read a resume three times, for different reasons. Writing for the parser, the preparation pass and the archive, and what may not be asked of you.
Employers do not read a resume once. They read it quickly to make a shortlist, then again in detail before an interview, then a third time when someone asks whether the file is still in the system a year later. Writing for one of those readings and not the others is why documents that feel strong get no response.
What to take away
- The first reading is a filter and takes seconds. The second is a source of questions. The third happens without you and depends entirely on what was recorded.
- An application usually goes into a system that keeps it, which means a bad version outlives the moment it was sent.
- What employers can and cannot ask for is defined, and knowing the boundary is more useful than guessing at what they want.
The three readings
| Reading | Who does it | What survives it |
|---|---|---|
| The shortlist pass | A recruiter or a parser, in seconds | Clear structure, obvious relevance, no work required from the reader |
| The preparation pass | The hiring manager, before the interview | Specific claims that generate questions |
| The archive pass | Someone months later, searching a system | Whatever fields were captured, and the notes attached |
Most advice addresses only the first. The second is where a document earns an interview that goes well rather than an interview that happens, and it rewards concrete detail rather than polish.
Three resume readings
Shortlist pass
- Who
- Recruiter or parser
- When
- In seconds
- What survives
- Clear structure
- What it rewards
- Obvious relevance
Preparation pass
- Who
- Hiring manager
- When
- Before interview
- What survives
- Specific claims
- What it rewards
- Concrete detail
Archive pass
- Who
- Someone months later
- When
- When similar role opens
- What survives
- Captured fields and notes
- What it rewards
- Searchable substance
Here is the same achievement written two ways.
- BeforeResults-driven professional with a proven record of improving processes.
- AfterCut order picking time from 14 to 11 minutes by rebuilding the pick route for eight pickers across two shifts.
The second line gives the manager something to question. That is what the preparation pass rewards.
Writing for the parser: what it extracts and how to test it
An applicant tracking system reads the file into fields before a person sees it. Systems such as Workday, Greenhouse, Taleo and iCIMS pull out your name, phone and email, the employer names, the job titles, the dates and the education entries.
Four formatting rules follow from that.
- Columnsdo not run two columns with dates in one and duties in the other. Use a single column, with dates at the left of each line.
- Headersuse standard headings such as Experience, Education and Skills. A heading like Where I have made a difference gives the parser no field to fill.
- Tablesdo not put your contact details or a job history inside a table. Parsers read cells in an order you did not intend.
- Graphicsdo not put a phone number or an email address inside an image, a text box or a header graphic. Text that is not text cannot be read.
To test the file, copy the whole document, paste it into a plain text editor and read the order. If a job title lands next to the wrong date there, a parser will make the same mistake.
None of this argues for stuffing keywords. The parser produces fields; a person reads them. What helps is using the posting's own vocabulary where your substance is the same, which is the same discipline described in the page on the resume inside a search.
The strictest version of this exists in public sector hiring, where the required contents are published. The federal guidance on what a resume must include asks for dates, hours and specific duties rather than a summary, and writing to that standard produces material that any system can capture correctly.
Cover letters: one reading, if that
Most applications are judged on the resume alone. A cover letter gets at most one reading, by a person, and often none at all. Where it is read, three short paragraphs do the work.
- Name the role and where you saw it, in one sentence.
- Name one requirement from the posting and one thing you did that meets it, with a number or a scope.
- Say one line about why this employer rather than the other places you applied to.
A middle paragraph that works: your posting names carrier scheduling as the main problem, and last year I rebuilt the route plan for 14 drivers and cut late deliveries. That sentence is checkable, and a letter built from three lines like it stays short.
Use the hiring manager's name only when the posting gives it. Otherwise use the job title. Keep the letter to one page.
What the employer is allowed to ask
Employers are constrained in what they may ask and how they use it. The Equal Employment Opportunity Commission's guidance on employment tests and selection procedures sets the standard for anything used as a selection device: it must relate to the job and be applied consistently.
That standard is a useful lens for a candidate. It shows what a well-run employer is trying to do, and what your document should make easy.
It also tells you what not to volunteer. Personal details that are not job-related create a problem for a careful employer rather than an advantage for you. A date of birth, a photograph, a marital status: in the United States these are usually better left off, and a good employer would rather not have them.
Judging an employer by its own documents
The posting is evidence: a description written from a real job analysis reads differently from one assembled out of stock phrases. It names what the role decides, who it works with, and what it is expected to change.
A posting made entirely of requirements and adjectives usually means a process is running the hiring, not a person.
The same reading applied to the structure behind a role is in the page on decoding a business development posting.
What to do with the archive reading
Two practical habits follow. Keep the exact file you sent, so that a conversation months later is about a document you can see. And keep the substance true, because the version in the system is the one a reference check is eventually compared against.
The wider craft of building the document out of scope rather than adjectives is covered in the resumes and cover letters guide, and what to do when the panel asks about a line on it is in the interviews guide.
Common questions
Should I use a designed template with columns and color?
Only if your field expects it and you also have a plain version. Multi-column layouts are the most common cause of a document being parsed into nonsense.
Do employers really keep applications?
Many do, typically for six months to two years, though the period varies by employer and by state record rules. It is one reason to apply properly even to a role you are unsure about.
Is a PDF or a document file better?
Send whatever the system asks for. Where there is a choice, a PDF preserves the layout and is usually parsed adequately. Where the system offers a form instead, fill in the form properly rather than uploading and hoping.
Should I include a photograph?
In the United States, no. In some other countries it is conventional. Follow the local convention rather than a general rule.
How do I know whether an employer reads cover letters?
Ask the recruiter. Many will tell you plainly, and the answer changes where you should spend your effort.
