Resume Builder

One page or two — and how recruiters actually read

The page-count debate has a practical answer: one page for early-to-mid careers (roughly under ten years, or any new graduate), two pages once you have enough genuinely relevant senior experience that cutting it would hurt you. Three pages is almost never right outside academia and senior research, where a CV with full publication lists is the expected format. The deeper truth behind the rule is that recruiters do not read resumes on the first pass — multiple eye-tracking studies put the initial screen at a few seconds per resume. In those seconds they scan, in a rough F-shape, for your most recent title, your current company, and dates. Everything else is read only if that scan earns it.

That changes how you should write. Front-load each role with the outcome, not the duty: 'Cut checkout drop-off 18% by rebuilding the payment flow' survives a scan in a way that 'Responsible for the payment flow' never will. Lead bullets with numbers, put the strongest role first, and make your current title visually prominent, because that's the first thing the human eye lands on.

ATS-friendly formatting that doesn't get mangled

• Standard section headings — use 'Work Experience', 'Education', 'Skills'. Applicant Tracking Systems parse by recognising these labels; a clever heading like 'Where I've Made Magic' can cause the parser to drop the section entirely.
• Single-column, linear layout — many ATS parsers read top-to-bottom and scramble multi-column designs, interleaving your skills sidebar into your job descriptions. The beautiful two-column template is often the one that parses worst.
• No text in images, headers or footers — anything rendered as an image is invisible to a parser, and some systems ignore header/footer regions, so never put your name or phone number only there.
• Real text, selectable — if you can't highlight the words with your cursor, neither can the ATS. Export so the text stays text, not a flattened picture.
• Plain bullets and standard fonts — skip decorative glyphs and exotic typefaces that can import as garbled characters. Keywords from the job description, used honestly, help you clear keyword-matching filters.

What recruiters scan for, and the self-inflicted rejections

Beyond the title and dates, the fast scan looks for relevance to this job specifically (a resume tailored to the posting beats a generic one every time), evidence of impact (numbers, scale, results), and a clean, calm layout that signals you can communicate. The candidates who get filtered early usually do it to themselves: unexplained employment gaps with no context, a wall of responsibilities with no outcomes, an objective statement that says nothing ('seeking a challenging role'), and typos — which read not as carelessness about the resume but as carelessness in general.

A resume builder is a formatter, not a ghostwriter. It will lay your experience out cleanly and export a crisp one-page PDF that holds its formatting in any inbox — but it can't decide which of your achievements matter for the role, quantify your impact for you, or tailor the language to the posting. That judgement is the actual work, and it's yours. Export to PDF unless the application portal explicitly asks for .docx, since PDF preserves your layout exactly where a Word file may reflow on the recruiter's machine; if a posting demands an editable document, our Word editor can take a PDF the other direction.