How Greenhouse Parses Your Resume: What's Documented vs. What's a Guess

A platform specific enough to actually research

Greenhouse runs the careers page behind a large share of tech companies and startups, which is probably why "Greenhouse resume parsing" gets searched often enough to support a small cottage industry of guides, checkers, and Chrome extensions promising to optimize your file for it specifically. A lot of what's written for that search term is the same recycled formatting advice you'd find for any ATS, with "Greenhouse" swapped into the title. That's not automatically wrong, but it's also not really about Greenhouse.

What makes Greenhouse worth a dedicated look is that it's one of the few platforms in this space that actually publishes something concrete about its own parsing behavior, in its own support documentation, instead of leaving job seekers to reverse-engineer a black box from forum complaints. That's rare enough in this niche that it's worth separating from the surrounding guesswork.

What Greenhouse's own documentation actually says

Greenhouse's support site has a published article on what it calls an "unsuccessful resume parse," aimed at the recruiters and admins using the platform, not at applicants. It's not written as job-seeker advice, which is part of why it's more trustworthy than most of what's out there: nobody's trying to sell you a template based on it.

A few specifics worth knowing:

There's a real file size limit. Greenhouse's documentation states that its parser can't process a resume larger than 2.5MB, even though the upload form itself accepts files up to 100MB. That gap matters: your file can upload successfully and still fail to parse, with no error message pointing you back at the actual cause. A 2.5MB resume is unusually large for a document that's mostly text, so this mostly affects files with an embedded photo, a background graphic, or a heavy design template behind the words.

A short, specific list of causes shows up for a failed parse. Beyond file size, Greenhouse names non-standard file types or characters that its text parser doesn't recognize, and resumes built mainly from graphics, photos, or decorative word art instead of real extractable text. It also notes that a garbled, incomplete, or clearly fake resume can produce a partial parse: some fields fill in correctly, others don't, without any single dramatic failure point.

A failed parse isn't a rejection. This is the part that doesn't match the more alarmist tone of a lot of advice built around this topic. When parsing doesn't work, Greenhouse's documentation describes the result as the resume file still being attached to the candidate's record, just without the fields getting automatically filled in. A recruiter opening that candidate's profile can still open and read the file directly. What you lose isn't your application, it's the convenience of your information showing up pre-sorted into searchable fields, which can matter if a recruiter is filtering a large pile by keyword rather than opening every attachment individually.

Why this is a useful contrast to the rest of the ATS conversation

Most of what circulates about applicant tracking systems is the opposite of what Greenhouse publishes here: specific-sounding, widely repeated, and sourced from nowhere. The "ATS rejects 75% of resumes" claim traces to no study anyone's been able to find. The complaints about Workday mangling resumes are often real experiences described with numbers (a "34% error rate," a specific accuracy percentage) that nobody's actually measured. Greenhouse's unsuccessful-parse article is a rare exception: a primary source, written for the platform's own customers rather than for search traffic, that names a real number and a real, short list of causes instead of a vague warning.

That doesn't make Greenhouse's parser better or worse than anyone else's. It makes this one specific question, what happens to a resume that fails to parse on this one platform, actually answerable instead of a guess dressed up as an answer. The plain-language walkthrough of what generally happens after you submit a resume online covers the broader pipeline; this is what the one documented piece of it looks like for a single, widely used vendor.

Where the rest of the advice stops being documented

A lot of the guides written around this exact search term go further than Greenhouse's own material does, adding specific-sounding tips about multi-column layouts, header and footer placement, or exact job-title phrasing as if Greenhouse had published a rulebook on them. Some of that advice is probably reasonable, since it matches the same general parsing mechanics that apply across most platforms (a structured, position-based layout is harder for any text parser to read cleanly than a single plain column, regardless of which company's software is doing the reading). But it isn't something Greenhouse has specifically confirmed about its own system, and treating a general industry pattern as a Greenhouse-specific fact is exactly the kind of blurring that makes this whole topic hard to trust.

The honest way to separate the two: the file-size limit and the named causes of a failed parse are things you can point to a real support article for. The layout-specific claims about this one platform are inference, often reasonable inference, but inference rather than something Greenhouse itself has stated.

What this actually means for your resume

If you're applying through a Greenhouse-powered careers page, the verifiable advice is narrower than most checklists suggest:

Keep your exported file size well under the 2.5MB ceiling. If your resume template includes a headshot, a decorative background, or a logo, check the exported file size directly rather than assuming a document that's mostly text is automatically small.
Export from a real document rather than a scan or a flattened image. A photographed or scanned resume has no text layer for Greenhouse, or any other parser, to extract from.
Avoid building core content, like your name, your skills, or your job titles, out of graphics, icons, or decorative text effects. That's the specific failure mode Greenhouse's own documentation names, not a general folklore rule.
Beyond that, the same structural habits that help on any platform (a real text layer, a layout that holds together outside of columns and tables, contact info in the body rather than a header) are still reasonable defaults. They're just general ATS practice, not something unique to this one company's software.

Where a parse-check fits in

None of this tells you what your specific resume file actually contains once it's exported, which is the part that matters regardless of which platform reads it. ResumeReadout runs your actual file through a parser and shows you the extraction directly: whether there's a real text layer, roughly how your layout holds up outside a single column, and whether your contact details and section headings would be recognized as the fields they're supposed to be. It won't simulate Greenhouse's specific 2.5MB threshold or guarantee anything about one company's configuration, since that's a detail only Greenhouse's own engineering team can speak to with certainty. What it can do is show you what's actually in your file before you submit it anywhere, which is a different and more concrete question than pasting your resume text into a chatbot and asking if it looks fine, since a chatbot never sees the file itself.

The bottom line

Greenhouse is an unusually good case study for this whole topic, not because its parsing is better or worse than any other platform's, but because it's one of the rare ATS vendors that tells you something specific and checkable about how its own parser fails: a real file size limit, a short list of named causes, and confirmation that a failed parse means manual data entry, not an automatic rejection. That's worth more than another recycled column-and-header checklist repeated under a new company name. Keep your file size reasonable, keep it built from real text rather than images, and the rest of the advice that actually matters is the same general, checkable practice that applies everywhere else.

FAQ

Does Greenhouse automatically reject a resume that fails to parse?

No. When Greenhouse can't extract structured data from a resume, its own support documentation describes the outcome as the file being attached to the candidate's profile without the fields getting auto-filled, not a rejection. A recruiter can still open and read the attached file directly. It's a worse experience, since your information doesn't show up pre-sorted, but it isn't the same thing as being screened out automatically.

What's the file size limit for Greenhouse to parse a resume?

Greenhouse's support documentation states that its parser can't process resumes larger than 2.5MB, even though candidates can upload files up to 100MB. A file under that parsing threshold is one of the few genuinely verifiable, platform-specific facts available here, rather than a guessed rule repeated from one SEO article to the next.

Why would a resume fail to parse in Greenhouse specifically?

Greenhouse's own support article names a short list: the file being too large (often because of embedded high-resolution images), non-standard file types or characters the text parser doesn't recognize, and resumes built mostly from graphics, photos, or word art rather than real text. A garbled or clearly fake resume can also result in a partial parse, where some fields fill in and others don't.

Should I use a different file format for a Greenhouse-powered application?

Not based on anything Greenhouse has published. The deciding factor isn't the extension, it's whether the file has a real, extractable text layer and stays under the size threshold. A reasonably sized, text-based PDF or Word file both work the same way a well-structured file works on any other ATS.

Keep reading

Or skip the reading and run the free parse-check →