> the honest answer, not the myth

Will Your Resume Pass Greenhouse?

You found the role, applied through a Greenhouse form, and heard nothing. It's natural to assume a robot read your resume and binned it. Here's the honest answer: Greenhouse doesn't score, rank, or auto-reject resumes — humans do the rejecting. But parsing errors and knockout questions can still sink your application before anyone looks closely. This page explains exactly what Greenhouse does with your resume, and our free checker shows what its parser sees — without your resume ever leaving your browser.

Scan my resume free →

no account · no email · 100% private — runs in your browser

Paste your resume

🔒 100% private: analysis runs entirely in your browser. Your resume is never uploaded to any server.

// what actually happens

What Greenhouse actually does with your resume

When you hit submit on a Greenhouse job board, two things happen. Your resume file is stored exactly as you sent it, and a parser extracts your contact details, work history, and education into a searchable candidate profile. That profile lands in a recruiter's queue. The parser has documented limits: per Greenhouse's own support docs, it can't process files over 2.5MB and struggles with tables, columns, graphics, word art, and contact information placed in headers or footers. When parsing fails, your searchable profile is incomplete — even though your original file looks fine.

Here's what Greenhouse does not do, in the vendor's own words: "Greenhouse never uses AI to rate candidates or auto-reject applications." There is no resume score, no ranking algorithm, and no keyword-match threshold deciding whether a human sees you. Candidate evaluation happens through scorecards — structured ratings (Strong No to Strong Yes) that recruiters and interviewers fill in by hand.

One genuine automation does exist: application rules, often called knockout questions. An employer can configure a job so that a specific answer to a custom question — Yes/No, single-select, or multi-select — triggers automatic rejection. "Are you authorized to work in this country?" is the classic example. This keys off your answers, never your resume content, and each employer configures it per job. Whether a given role uses knockout rules varies and isn't visible to you as a candidate.

// myth vs reality

What candidates believe — and what's documented

mythA Greenhouse algorithm scored my resume and rejected it.
realityGreenhouse states flatly that it never uses AI to rate candidates or auto-reject applications. Rejections are dispositioned by humans — or triggered by your answer to an employer-configured knockout question. Resume content alone never triggers an automatic rejection in Greenhouse.
mythIf my resume doesn't hit a keyword threshold, no human ever sees it.
realityThere is no match score in Greenhouse. Every application lands in a recruiter's queue. On high-volume roles recruiters do use keyword search and filters to decide who to look at first — so keywords affect whether you're found, but there's no automatic cutoff.
mythI was rejected within minutes, so a bot must have read my resume.
realityA near-instant rejection almost always traces to a knockout question — answering 'no' to work authorization or a required license the employer flagged as disqualifying. That's a rule the employer set on a question answer, not software analyzing your resume.
mythGreenhouse can't read PDFs — you have to submit a Word file.
realityGreenhouse parses both PDF and DOCX. What actually breaks parsing, per its support docs: files over 2.5MB, image-based files, letter-spacing effects, tables and columns, and contact details tucked into headers or footers.

// the real rejection mechanism

How recruiters use Greenhouse on their side

Greenhouse describes the reality plainly: your application goes "straight into a queue on a recruiter's dashboard," and recruiters typically work through it in order, viewing your resume exactly as you submitted it alongside your form answers. On high-volume roles, they narrow the pile first — filtering by custom question answers, prioritizing referrals and internal candidates, and running keyword searches across parsed resume text. If your parsed profile is missing data, you're invisible to those searches even though your file is sitting right there.

The real rejection mechanism is a human moving fast, not an algorithm. Eye-tracking research from Ladders puts the average first resume screen at 7.4 seconds — so your resume has to survive a skim, then a scorecard. And silence usually isn't rejection-by-robot either: candidates filtered out on a busy role often simply never get reviewed, and the closure email comes late or not at all, depending on the employer.

// before you apply

Resume tips specific to Greenhouse

Keep your file under 2.5MB
Greenhouse documents this as a hard parsing limit — larger files simply don't get parsed. High-resolution headshots, logos, and design graphics are the usual culprits. Export a lean PDF and you'll clear it easily.
Move contact info out of the header and footer
Greenhouse's support docs list contact information in headers or footers as a known parse failure. Put your name, email, phone, and location in the body of the document, at the top.
Skip tables, columns, and word art
Complex layouts with tables, multi-column designs, letter-spacing effects, and decorative text are all documented parse-breakers in Greenhouse. A single-column layout with standard section headings parses cleanly.
Remember a human sees your original file too
Unlike some ATSs, Greenhouse shows recruiters your resume exactly as submitted, not just the parsed version. So clean visual design still pays off for the human skim — it just can't come at the cost of the searchable parsed layer.
Treat knockout questions as seriously as the resume
The only automatic rejection in Greenhouse keys off your answers to custom application questions — work authorization, required licenses, location. Read each dropdown carefully; a rushed misclick on one of these can end an otherwise strong application.

Check your resume before you submit →

Frequently asked questions

Does Greenhouse auto-reject resumes?

Not based on resume content. Greenhouse states it never uses AI to rate candidates or auto-reject applications. The only automation is employer-configured rules tied to application question answers (knockout questions) — for example, answering 'no' to a work-authorization question on a job that requires it.

Why was I rejected minutes after applying through Greenhouse?

Almost certainly a knockout question. Employers can set a rule that a specific answer — usually about work authorization, a required license, or location — triggers automatic rejection with a templated email. It's a rule on your answer, not software reading your resume.

Does Greenhouse score or rank my resume against the job description?

No. There is no match score or ranking algorithm in Greenhouse — its CEO has publicly argued against automated resume scoring. Recruiters search parsed resume text by keyword and rate candidates manually on scorecards, so the job description's language still matters — for being found by a human, not for passing a machine.

Why do Greenhouse applications go silent for weeks?

Your application sits in a recruiter's queue until a human reviews it. On high-volume roles, recruiters filter by referrals, sources, and question answers first — candidates outside those filters may not be reviewed for a long time, and per Greenhouse, not every rejection (including auto-rejections) comes with an email. Silence usually means 'not reviewed yet,' not 'rejected by a robot.'

// sources

Our scoring is rule-based and documented — see how ATSGrader scores resumes. We are not affiliated with Greenhouse; employer configurations vary.