Whether to list every job, and what leaving one off actually creates
Leaving a job off a résumé is normal practice. Leaving one off a form that asks for your employment history is a different act, and the distinction is the whole answer.
— the résumé selects. the form declares.
This question is asked as though there were a rule, and the honest answer is that there are two documents with two different obligations. A résumé is a selection. A form that asks for your employment history is a declaration. The résumé builder makes the first one, and everything below is about that.
What the checker cares about
Not this. The ATS résumé checker has no rule about the number of employers, the length of a role or the presence of a gap. It grades whether the text comes out in a readable order, whether the seven completeness essentials are present with real content under them, and whether the achievement lines carry action, figures, depth and volume. The arithmetic is printed on every report and taken apart in how the ATS score is calculated.
What omission actually creates
A date range with nothing in it. That is the real cost, and it is a cost the reader pays attention to rather than the parser. Two months missing between two jobs is invisible; a year missing is a question somebody will ask. Where the answer to that question is fine, keeping the job on the page is usually less work than explaining its absence later.
The room argument
A page is finite. A Saturday job from 2009 on a senior page is taking the space of an achievement line from 2023, and the evidence-depth rule pays for lines under recent roles rather than for completeness of record. How far back a résumé should go and how long it should be work through the cut.
The compression that keeps the dates honest
Early roles can be collapsed into one line: earlier roles in retail and hospitality, 2009 to 2014, with the employers named and no achievement lines under them. The dates stay continuous, the page keeps its room, and nothing has been hidden. That shape also avoids the situation where the parser finds an experience section full of one-line entries, which is measured in seasonal work on a résumé.
Where the page can lose points by reorganising
The version that costs something is relocation rather than omission. Work written up under projects or skills, with no experience section carrying roles and dates, That loses the completeness rule's experience check, worth thirty of that dimension's hundred points, and can bring a ceiling down on the published score. Evidence ceilings explained has the measurement.
The one place the answer changes
A form, a vetting questionnaire or an application system that asks for your full employment history is asking a different question from a résumé, and what it requires comes from whoever is asking. This page is not legal advice and does not tell you what any such form requires. It says only that the two documents are not the same document and should not be reasoned about together.
The two-month job, in practice
A role that lasted two months and ended badly is the case everybody actually means when they ask this question. Where it sits between two longer roles with no visible gap, leaving it off costs nothing and explains nothing. Where removing it leaves a year unaccounted for, keeping it with a plain one-line description is usually less trouble than the question its absence creates.
What the page should never do is disguise it. Stretching the dates of the roles either side to close a gap is a statement about dates that a reference check will contradict, and it converts an ordinary short role into a credibility problem. The résumé is a selection, and a selection is honest; an altered date is not.
The letter takes the explanation
Where a period needs a sentence, the sentence belongs in the letter rather than on the page. The cover letter builder selects its proof paragraphs from your own résumé lines and has an optional field for what only you know, in your own words. It will not invent an explanation for you, which is the subject of why a cover letter only claims what the résumé shows. How to explain a career gap and what not to put on a résumé cover the rest.
Decide what goes on the page
Import the whole history, then keep what argues for this job. Free, no account, and the file stays in this browser.
Open the résumé builderRead how far back to goQuestions
- Does the checker count how many jobs are on the page
- No. There is no rule about the number of employers or the length of a role. It grades parseability, seven completeness essentials and four content rules.
- Does a gap lower the score
- No. There is no gap rule anywhere in the scoring, so an unaccounted year does not appear in any check.
- What is the difference between a résumé and an employment history form
- A résumé is a selection you write. A form that asks for your full employment history is a declaration, and the obligation on it comes from whoever is asking rather than from any convention.
- What about a job I was only in for two months
- Where it adds nothing and creates no gap worth explaining, leaving it off is ordinary. Where the dates around it would leave an unexplained year, it is usually easier to keep it.
- Where does an explanation belong
- In the letter rather than the document. The cover letter builder has an optional field for what only you know, in your own words, and will not invent a reason for you.
Conxfolio is a free set of four career tools: a résumé builder with 37 rendered layouts, an ATS résumé checker that prints its own arithmetic, a cover letter builder that traces every proof paragraph back to the line it came from, and a portfolio builder with 20 authored designs. There is no account to create, nothing is held back for a paid plan, and no language model is used anywhere in the product, so the readers, the score and the letter are deterministic code you can check.