Over the past four years I have sat on the hiring side of the table for three different tech companies. I have personally reviewed somewhere north of 500 resumes for roles ranging from junior frontend developer to senior platform engineer. And the pattern that emerged was so consistent it almost felt like cheating once I noticed it.
The three best resumes I ever received were all one page.
Not because there is something magical about a single sheet of paper. But because the constraint forces a kind of clarity that most candidates never achieve. When you only have one page, every line has to earn its place. That discipline shows up immediately, and it signals something about how you think.
Let me walk through what I learned sitting on that side of the desk, and what actually moves a resume from the rejection pile to the interview pile.
The 7.4-Second Reality
There is an eye-tracking study from Ladders that gets cited a lot, and for good reason. They found that recruiters spend an average of 7.4 seconds on an initial resume scan. That number sounds brutal, and it is. But understanding it changes how you approach the whole document.
In those 7.4 seconds, the eye follows what researchers call an F-pattern. It sweeps across the top of the page, drops down the left side, and makes one or two horizontal passes. That means your name, your current role, and your top two or three skills need to live in the upper-left quadrant of the page. If those elements are buried below a block of text, or hidden in a sidebar, or tucked under an objective statement, they might as well not exist.
I cannot overstate this. The spatial layout of your resume matters more than almost anything else on it. A perfectly written accomplishment in the wrong position on the page is a perfectly written accomplishment that nobody reads.
Accomplishments, Not Descriptions
The single biggest mistake I saw across those 500 resumes was confusing job descriptions with accomplishments. There is a fundamental difference between "Responsible for API development" and "Reduced API response time by 40% through query optimization and caching layer implementation."
The first tells me what you were assigned. The second tells me what you actually did and what happened because of it. Every hiring manager I have worked with responds to the second version. Every single one.
The formula is straightforward: action verb, specific thing you did, quantified result. "Led migration of 3 microservices to Kubernetes, reducing deployment time from 45 minutes to 8 minutes." "Built internal dashboard used by 40-person sales team, cutting weekly reporting time by 6 hours." Numbers make you real. Vague descriptions make you forgettable.
If you do not have exact numbers, estimate conservatively and use qualifiers. "Approximately" and "roughly" are fine. A rough number beats no number every time.
The ATS Keyword Game
Here is something that surprised me when I first moved into a role that involved hiring. A significant percentage of resumes never reach a human at all. Applicant Tracking Systems filter them first, and they are essentially running keyword matching against the job posting.
This means your skills section is not really for humans. It is a keyword filter. And the most effective strategy is almost embarrassingly simple: read the job posting, identify the specific technical terms and phrases it uses, and mirror that language exactly in your resume. If the posting says "React.js," do not write "React" or "ReactJS." Match it precisely.
I have seen qualified candidates get filtered out because they wrote "JavaScript" when the ATS was looking for "JS" as a separate keyword, or vice versa. The system is dumb. Work with its limitations instead of against them.
What to Remove Immediately
Objective statements. These became obsolete around 2010. A recruiter knows your objective is to get the job you applied for. That space at the top of your resume is the most valuable real estate on the page. Do not waste it restating the obvious.
"References available upon request." This is assumed. It has been assumed for decades. Those four words take up a line that could hold a quantified accomplishment.
Hobby sections, unless the hobby is directly relevant to the role. Your marathon running does not help your candidacy for a backend engineering position. Your open-source contributions to a database project absolutely do.
Fancy designs. This one hurts because some of these resumes were genuinely beautiful. Two-column layouts, custom graphics, color-coded skill bars, infographic-style timelines. They look great on screen, and they get destroyed by ATS parsing. Research suggests that two-column layouts fail approximately 30% of ATS systems. The parser reads left-to-right, top-to-bottom, and a two-column layout turns your carefully organized sections into scrambled nonsense.
The File Format Question
PDF preserves your formatting perfectly and is the right choice when you are emailing a resume directly to a person, submitting through a portal that specifically requests PDF, or when you know a human will be the first reader.
DOCX is what most ATS systems parse most reliably. When you are applying through a company's online application system and they do not specify a format, DOCX is the safer bet. It feels less polished, but polish is meaningless if the system cannot read your content.
If the job posting specifies a format, use that format. If it does not, and you are going through an ATS, default to DOCX.
Small Details That Matter
Font choice is one of those things that seems trivial until you realize that some fonts cause ATS parsing errors. Calibri, Arial, and Garamond are safe across virtually every system. Avoid anything decorative, anything with unusual kerning, and anything you downloaded from a free font site.
Here is a header trick I started recommending after seeing it work consistently: put your LinkedIn URL directly under your name, on the same line as your email and phone number. Recruiters check LinkedIn almost reflexively. Making it easy for them to find your profile means they see a more complete picture of you before they have even finished reading your resume. It is a small thing that creates a disproportionate advantage.
White space matters more than you think. Dense, wall-of-text resumes trigger a kind of visual fatigue during those first 7.4 seconds. Comfortable margins, clear section breaks, and consistent spacing between entries make the F-pattern scan feel effortless instead of exhausting.
Putting It Together
The resumes that made it to my interview pile shared a few traits. They were one page. They led with quantified accomplishments. They were formatted simply enough for any system to parse. And they felt like they were written by someone who understood that a resume is not a biography. It is a marketing document with a specific audience and a specific goal.
If you want a starting point, I built a resume builder that enforces a lot of these principles by default. ATS-friendly formatting, clean single-column layout, and the structure to guide you toward accomplishments instead of descriptions.
The best resume advice I can give is also the simplest. Pretend you have 7.4 seconds to convince someone you are worth a conversation. Then build your page around that constraint.
I'm Michael Lip. I build free tools at zovo.one. 350+ tools, all private, all free.
Top comments (0)