What Does an ATS Resume Look Like? (With Real Examples and Parser Output)

Two Views of the Same Resume

Every ATS ingests your file and produces a structured record. Workday, Taleo, iCIMS, Greenhouse, and Lever all do essentially the same thing under different branding: they read your document and write a JSON-style candidate profile to their database. The recruiter never sees your original file first. They see the parsed profile, and then only click into the original if the profile looks promising. That makes the parsed output, not the visual layout, the thing that determines whether you advance.

Here is what the same resume section looks like to a human and to the parser, using a mid-career software engineer as the example. Both columns refer to the exact same 7 lines of text in the source file.

{
  "work_experience": [
    {
      "job_title": "Senior Software Engineer",
      "company": "Acme Logistics, Inc.",
      "location": "Austin, TX",
      "start_date": "2022-03",
      "end_date": "present",
      "bullets": [
        "Led migration of the order routing service...",
        "Owned the on-call rotation for 6 engineers...",
        "Mentored 3 junior engineers..."
      ],
      "extracted_skills": [
        "microservices",
        "on-call",
        "mentoring"
      ]
    }
  ]
}

The parser does not care about your font choice or margin widths. It cares whether "Senior Software Engineer" lands in the job_title field, whether "Acme Logistics, Inc." lands in company, and whether "2022-03" and "present" land in start_date and end_date. Every visual decision you make either helps those assignments happen or interferes with them.

The 6 Visual Traits of an ATS Resume

Strip away the variants and every ATS-safe resume shares six visual traits. These are not style preferences; they are direct consequences of how parsers tokenize a document. If the parser has to guess, it gets things wrong.

Role-Based Examples: What an ATS Resume Looks Like for Your Field

The six traits above are constants. What changes by role is the content inside the standard structure. Below are three realistic resume snippets, one each for a software engineer, a nurse, and a marketing manager. Each shows how the same ATS-safe format still leaves plenty of room for role-specific detail.

Each example uses the same skeleton: centered name, inline contact, standard section names in bold, bullet lists under each role, MM/YYYY dates, no graphics, no columns. The content inside is wildly different; the structural template is identical. That is what "ATS-safe formatting" looks like in practice across three very different fields.

What the Parser Actually Extracts (Field by Field)

Under the hood, every ATS maps your resume content to a fixed schema. The field names vary slightly between platforms, but the underlying data model is similar. Below is the consolidated schema used across Workday, Taleo, iCIMS, Greenhouse, and Lever, with the visual element in your resume that each field maps to.

In our 200-resume benchmark, a clean single-column DOCX populated 14 to 15 of these 15 core fields. A 2-column creative template populated 6 to 11 fields depending on which parser, with 4 to 5 fields garbled (merged, truncated, or misassigned). That is the real, measurable difference a resume layout makes.

For the full keyword side of the equation, see our companion guide on what ATS compliant means and how each of the three compliance gates is scored.

What an ATS Resume Does NOT Look Like

The inverse is just as important. Below is a DO/DON'T grid showing exactly what breaks, with the parse output each failure mode produces.

The typography and font side of this topic is covered in depth in our guide to ATS-friendly fonts and styles, including which fonts silently substitute at parse time.

Bad Example: What the Parser Sees When Formatting Breaks

Here is the same marketing manager resume from Example 3, redesigned as a "creative" 2-column Canva template with icons, a photo, and a sidebar skill bar chart. The human view looks polished. The parsed output is a mess.

{
  "full_name": "Demand Gen 90% ABM",
  "email": null,
  "phone": null,
  "city": null,
  "state": null,
  "work_experience": [
    {
      "job_title": "Senior Marketing Manager",
      "company": null,
      "start_date": null,
      "end_date": null,
      "bullets": []
    }
  ],
  "skills": [],
  "education": []
}

Out of 15 expected fields, 10 are null or garbled. The parser read the left sidebar first (skill bar labels) and assigned that text to full_name. Contact info was in icon table cells, which were skipped. The section heading rectangles were image elements, so section detection failed. The bullets never appeared because they lived inside a grouped shape that the parser did not descend into. On Workday, this candidate never made it to the recruiter's queue, regardless of actual qualifications.

Four Common Misconceptions About How ATS Resumes Look

Because "ATS-safe" gets conflated with "ugly," plenty of confident-sounding advice is wrong. Here are the four corrections we find ourselves making most often.

How to See What Your Resume Looks Like to the ATS

The fastest self-check: open your resume PDF in a viewer, press Ctrl+A to select all, then Ctrl+C to copy, then paste into a plain text editor (Notepad, TextEdit, any code editor). What you see in the text editor is roughly what the parser sees. If your name is missing, if sections appear out of order, if dates are attached to the wrong company, or if text is missing entirely, the ATS sees the same mess. For a full parsed-output view with field-level scoring, run your file through an ATS scanner. Our free ATS resume checker returns the extracted fields alongside the score so you can see exactly which pieces of data the system captured and which it missed.

If you want a deeper dive into format choice (chronological, combination, functional) and which one parses cleanest for your situation, see our guide to resume formats explained.