Chronological vs functional: parsers still want dates and employers

A chronological resume lists jobs from newest to oldest. Each block has employer, title, city, month–year dates, then bullets. Skills sit in their own heading. That is the document Workday, Greenhouse, Taleo, Lever, and iCIMS were built to file. It is also the document a hiring manager can skim at 07:15 without reconstructing your calendar.

A functional resume leads with skill clusters — “Leadership,” “Operations,” “Customer success” — and tucks employers into a thin list at the bottom, often without months, sometimes without years. Career-change blogs still recommend it as a way to “lead with transferables.” What it actually does is hide the employment graph. A Greenhouse extract may keep the nouns. A recruiter still asks why the dates are missing. Background checks still want the graph.

A hybrid (combination) resume keeps reverse chronology and adds a short Skills or Selected projects block near the top. That is the usual honest compromise for a career switch or a heavy stack. Hybrid is not “functional with a date somewhere.” If the reader cannot see employer plus dates without scrolling through a cloud, you wrote a functional file and called it hybrid. For the visual rules around any of the three, use resume format. This page stays on which graph you show.

If a coach sold functional as the only way to look senior, test that claim on the Apply page in front of you. Workday will still show empty employer rows after the parse. Greenhouse will still store a skills blob and leave a recruiter unable to defend your dates to a hiring manager. Rebuild the graph first. The cloud can wait until Skills is a heading, not a disguise. LinkedIn can stay broader; the file you upload cannot.

Who still sells functional — and why it fails the parse

• Bootcamp and career-coach templates that put “Core competencies” above empty date lines.
• People with a gap who think hiding months will hide the hole. It enlarges the hole. See employment gap resume.
• People switching fields who delete the last employer instead of compressing it. See career change resume.
• Two-column “modern” files that are chronological on the screen and functional in the extract because the sidebar shuffled first.

Workday’s application is a set of fields: employer, title, start date, end date, repeating. The upload parse tries to fill those fields from your file. A chronological block maps cleanly: “Acme, Account Manager, Mar 2022 – Present.” A functional cloud maps as a skills blob. The employment section of the form stays empty or duplicates badly. You then spend twenty minutes retyping what the chronological file would have filled. Taleo and iCIMS behave the same way with slightly different date tokenizers — “2022 to now” is weaker than “Mar 2022 – Present.”

Greenhouse search is a recruiter typing nouns and sometimes titles. They can find “Salesforce” in a functional cloud. They cannot answer “when?” without opening the file and guessing. When two candidates both have Salesforce, the one with dated employer blocks wins the first pass because the recruiter can defend the screen to a hiring manager. A skill cloud looks like you are hiding a gap, a short stint, or a title you do not want to explain. Sometimes you are. Sometimes you are following a template. The recruiter cannot tell the difference at speed.

Hybrid done right: Skills heading with posting nouns you can defend, then Experience in reverse chronology with full dates. Optional Selected projects with dates if the project is the proof (freelance, open source, a capstone). Hybrid done wrong: Skills for a page, then “Professional history” with years only. That is functional with extra steps. For field-by-field Workday behavior, see Workday resume format. For how to write the dated blocks, how to list experience.

Recruiters who work both Workday and Greenhouse will open the PDF when the parsed card looks odd. A chronological file buys that click. A skill cloud spends it. If you already filled the employment widget by hand, still keep dates in the file: the next requisition will parse again, and a sourcer who never opens the form will only see the attachment.

Date formats that sort

• Month and year beside each role: Mar 2022 – Present, or 03/2022 – 11/2024.
• Agency plus client in one block so the graph does not look like unemployment.
• Do not write “2022–24” in a thin sidebar. Do not replace dates with “recent” or “current role” as a heading.
• If a month would fill an unexplained hole, put the month. Years-only is how gaps look larger, not smaller.

The edit is usually not “add adjectives.” It is “put the same facts back on a timeline.” Below are three rewrites we use in edits — a career switcher, a gap, and a contractor. Steal the pattern, not the facts. Keep the nouns. Restore employer and dates.

If you are changing fields, keep the old job on the timeline and add a projects block for the new proof — do not delete the employer. Compress the old bullets; do not vaporize the dates. Pair this page with career change resume. For bullet patterns inside chronological blocks, resume bullet points and resume action verbs.

Block two hours. Have the posting, the functional file, and a notes app of real employers and months. If you want a layout parsers already map, start in the Enhance CV builder and paste the graph first, skills second. Write the summary last.

People invert the order. They pick a hybrid template, paste the old cloud into Skills, and leave Employment as years only. That file still fails the graph. Spend the first twenty minutes on paper: employer, title, months. Then type. Fonts are the last ten minutes, not the first.

1. List every employer, title, city, and month–year you actually have. Include agency and client. This list is the spine. The cloud is not.
2. New file. Name, city/region, phone, email in the body — not in a header text box.
3. Optional 3–4 line summary after the graph exists. Title, years, domain, one proof point — not a list of skill names already in Skills.
4. Experience in reverse chronology. One block per job. Dates beside the title. No “various employers” line.
5. Under the most relevant job, three to five bullets with verb + object + number or tool. Older jobs: one or two lines.
6. Move nouns from the old skill cloud into those bullets where they are true. Leftover nouns go under a Skills heading, grouped, no bars.
7. If you have a gap, date it in one line. Do not cover it with a functional section. See employment gap resume.
8. If you are switching fields, add Selected projects with dates under or above Experience — still a timeline. See career change resume.
9. Education: degree, school, year. Do not use Education to hide a work gap unless you were actually in school then.
10. Drop “References available,” hobbies, and a photo for US Workday pipelines.
11. Export selectable text. Open on a phone. Confirm you can see employer and dates without pinch-zoom.
12. Paste resume and posting into the ATS checker. Confirm employers and dates parsed, then upload to Workday or Greenhouse.

People invert step 1. They pick a hybrid template, paste the cloud into “Skills,” and leave Employment as years only. That file still fails the graph. The spine is dates and employers. Everything else hangs on it. Steal summary structure, not sentences, from professional summary examples.

Two very different targets still mean two files, both chronological. LinkedIn can be broader; Workday cannot. Do not ship one functional compromise that serves neither posting. Tailor the resume inside chronology, not by deleting the timeline.

Use this as a desk-side filter. If a case is not in the table, ask: can Workday fill employer and dates, and can a recruiter explain your graph to a hiring manager without guessing?

Length is a separate decision. Chronological files can be one page or two. Functional files are not “shorter”; they are less dated. See resume length and one-page resume. An ATS resume is a chronological or honest hybrid file that still contains contact after the parse — not a keyword cloud.

Military to civilian. Translate MOS into a civilian title in the same dated block — “Logistics Specialist (MOS 92A)” — do not explode the service years into a functional “Leadership” essay. Keep dates. Add a Skills heading for tools. Pair with career change resume.

Returning after caregiving or study. Chronology plus one named line. A functional file reads as if you are still out. Details in employment gap resume. If you studied full time, Education dates should match the hole.

Application forms with a skills questionnaire. Fill the form. Do not replace the resume graph with a second cloud. Workday will have both. Inconsistent dates between form and file are how duplicate jobs appear. See how to upload to Workday.

Creative portfolios. A site can be visual. The file you upload to Greenhouse should still be one column with dates. Hiring managers look at the portfolio after the parse, not instead of it.

What to do next today: write the employer–date spine on paper, rebuild in one column, then score the file. If the checker flags missing dates or a heading Workday will not map, fix the graph before you polish adjectives. Then build in Enhance CV if the layout is still a skill-cloud template.