For most U.S. applications with a fairly steady work history, reverse-chronological is still the CV format that applicant tracking systems and hiring managers both know how to read. Hybrid is the backup when skills have to show before the job list. Functional is the layout that keeps causing trouble.
To be honest, a plain timeline beats a decorated template for this. Trying to pick a layout, or trying to guess what an ATS will do with your dates and titles? That's one problem. If the software can't map employers, titles, and dates into fields, a recruiter's keyword search never sees the rest.
Default to a single-column reverse-chronological file. Switch only when your story truly doesn't fit a timeline.
Reverse-chronological vs functional vs hybrid
ATS software expects a work history it can read from the top. Recruiters do too. The three classic formats are not equal on that test.
| Format | What it puts first | Main risk | Usually fits |
|---|---|---|---|
| Reverse-chronological | Recent jobs and dates | Gaps sit in plain view | Same-field experience |
| Functional | Skill categories | Parsing errors; looks evasive | Almost never |
| Hybrid | Short skills list, then dated jobs | A bloated skills wall | Career changes, mixed work |
A 2024 Jobscan survey of recruiters is often quoted for a harsh view of functional resumes: 62% associated them with hidden gaps or thin experience. That's vendor research on a sample, not a vote of every hiring team. It still matches how parsers behave. They look for jobs and dates in ordinary places.
Reverse-chronological is the default for a reason
Contact details, a short summary, jobs newest first, then skills and education. That's the skeleton.
Each role needs a title, employer, location, and dates. Add three to five bullets that show results, not chores. "Led campaigns that lifted qualified leads 40% after A/B tests and SEO work" carries more than "responsible for marketing."
Thing is, this format only backfires when the timeline itself is the problem. A long gap, a hard pivot, or a string of tiny contracts can look chaotic. Then you change the emphasis. You still keep the dates.
Functional CVs hide the timeline, and parsers notice
Skill headers on top. A thin job list. Sometimes no dates at all. That's the functional bet.
People grab it for gaps, pivots, or almost no paid work. The bet usually fails. Titles land in the wrong field. Years of work drop out of filters. A recruiter who opens the file may assume you're covering something up.
No experience is not a reason to go functional. Lead with education, projects, internships, and volunteer work in chronological order. Keep every real job dated.
Hybrid when you must lead with skills
A workable hybrid is a combination resume: a small skills section, then a full reverse-chronological history. Parsers can follow that. Humans can too.
Cap the skills block. A few lines. Then jobs. If the top third of the page is a cloud of tools, you've rebuilt a functional CV and given it a friendlier name.
Sample shape for a move from retail operations into marketing analytics. Summary: "Store operations supervisor applying three years of sales reporting and inventory forecasting to digital marketing analysis." Skills: Excel, forecasting, customer research. Keep the store job on the page with real dates. Rewrite one bullet around the weekly sales analysis you already did. That's the bridge. The old employer stays.
You take the retail job and you keep the retail job on the page, you just stop writing it like a store handbook and start pulling the pieces that match the posting, the inventory numbers, the customer patterns, the weekly report you already made even if nobody called it analytics at the time. Dates matter. The dates have to stay.
Layout rules that help an ATS read the file
Large employers commonly route applications through an ATS. Fortune 500 usage numbers get repeated a lot, including a widely cited MIT Career Advising note that about 99% of those companies use some form of system. Write as if your target company does.
Use one column, top to bottom. Sidebars and two-column templates are a frequent break. Stick to Arial, Calibri, Helvetica, Georgia, or Times New Roman at 10-12pt. Don't trap text in images, shapes, or tables.
Name sections the boring way: Work Experience, Education, Skills. Cute labels often don't map. Export .docx or a simple PDF where you can still highlight the words. Icon-heavy graphics files are a common miss.
Recruiters still filter. Pull real terms from the posting: tools, licenses, and job-title phrasing you honestly match. Scanners such as Jobscan estimate overlap with the description. Treat that score as a proofreading pass. It is not a callback promise. No scanner covers every ATS variant.
Which format to try first
Entry-level seekers should stay chronological and move education up if that's the strongest proof. Classes, projects, and internships are still a timeline. Don't dump skills into a functional cloud.
Career changers should use hybrid. Translate the old work. Don't delete it. Tech applications often need a short tools line plus jobs that name that stack in context. "Excel" in a list is weaker than a bullet that says pivot tables cut reporting from two days to four hours.
Mid-career and executive files can stay reverse-chronological. Progression is the story. Two pages is enough if early roles shrink to a line and every remaining bullet is an outcome. Creative applicants can keep the ATS file dull and put the personality in a portfolio URL. Freelancers fit hybrid: clients, dates, and tools on one page.
Federal applications are the exception on length, not on chronology. USAJOBS wants a dated history. It also caps the file.
A working order for building the page
- Choose reverse-chronological, or hybrid if you're changing fields.
- Draft a 2-4 line summary: target job title, years, two posting skills, one numbered win.
- Highlight repeated tools and duties in the job description that you actually have.
- For every role, list title, employer, city, and month-year dates, then 3-5 result bullets.
- Use 0.5-1 inch margins, 10-12pt body text, and 1.0-1.15 line spacing.
- Export PDF or .docx and confirm you can highlight the words.
- Run the file against that posting in an ATS-style scanner and add missing true keywords.
Under about ten years of relevant work, one page is enough. Two pages is the private-sector ceiling for most executive CVs. Empty space is not a reason to ramble. Cut the old stuff.
Write bullets as verb, task, tool, number. "Cut month-end reporting from two days to four hours with Excel pivot tables" survives a fast skim. "Duties included reporting" does not.
USAJOBS is not a corporate CV with extra adjectives
Federal hiring uses a different document. USAJOBS instructions for federal resumes set a hard length rule: you cannot upload or build a resume longer than two pages, and it must be 5 MB or less.
0.5-inch margins are their suggestion for fitting required detail. Each relevant job should carry the facts the announcement asks for. Their own example header looks like Program Analyst, GS-343-11, January 2009-present, 40 hours/week, then duties tied to the posting.
Turns out the long federal resume habit, the four-to-six-page packet people used to assemble, is exactly what the current portal rejects. You still need hours, grades, and announcement language. You just have to pack it.
Read the vacancy before you paste a private-sector CV. Some announcements want extra contact or supervisor fields you'd never put on a company resume. Follow USAJOBS on what to omit. If a specialist can't see your core credentials in about 10 to 15 seconds, the two-page limit will hurt.
Skills, length, and design that actually get read
Put skills in two spots. A short keyword list near the top. Proof under the jobs. Forty tools in a blob is not equal to one line that says you ran lifecycle email in HubSpot and moved MQL-to-SQL conversion 22%.
First-pass reading is brutal. A Ladders eye-tracking study is often cited at 7.4 seconds. You won't slow that down. You can make the first screen show a current title, clear dates, and one hard number.
Skip infographic templates for the application itself. Multi-column files that look sharp in a design tool break in common ATS products. Keep the attached CV boring. Link a portfolio if the work is visual.
Drop the empty slogans. "Results-driven professional" wastes the line. Put the number there instead.
Common follow-ups
Is reverse-chronological the best CV format for most applications? Yes, if your work history is continuous and in-field. It's the layout parsers are built around.
What about tech jobs? Use a hybrid: a short tools line, then chronological roles that name those tools in context.
Best format for a career change in the U.S.? Hybrid. Skills up front, old jobs still dated and rewritten toward the new target.
Will a functional resume pass ATS? It's the weakest of the three for parsing. Prefer hybrid, or education-first chronological if you're entry-level.
One page or two? One page for under a decade of relevant work. Two pages for most senior private-sector files. Federal is two pages because USAJOBS requires it.
Open the posting you're actually applying to. Pick chronological or hybrid. Rewrite your current job with three numbered bullets, export a plain file, and check that every heading is still regular text before you hit submit.