Greenhouse is one of the most common career portals behind mid-size and large tech employers, and it's also one of the most misunderstood. The popular assumption is that it runs an automated keyword-matching score that ranks or rejects resumes the moment they're uploaded, the same story told about ATS software generally. That's not what Greenhouse does. Understanding the actual mechanism changes what's worth optimizing for.
What Greenhouse actually is
Greenhouse is fundamentally a workflow and pipeline tool for recruiters and hiring teams — it stores applications, structures the interview stages, and lets a team leave scorecards and notes against each candidate. It does parse your resume into structured fields (name, contact info, work history, education) so a recruiter doesn't have to retype them, and it does support keyword search across the stored resume text for a recruiter actively searching the pipeline. But there's no default automated score that ranks or auto-rejects you purely from resume text the way the "ATS robot" narrative implies. A human — usually a recruiter or coordinator — is the one deciding who advances, using the parsed fields and the resume itself as their input.
Where the parsing step still bites
Even without an automated score, bad parsing still costs you, just differently: if Greenhouse's parser mis-reads your work history dates, garbles a job title pulled from a multi-column layout, or drops a section entirely because of unusual formatting (tables, text boxes, graphics-heavy templates), the recruiter's first view of you is already wrong before they've read a word you wrote. A single-column, standard-heading resume — the same guidance that holds for parsing generally — avoids this failure mode entirely, and it costs nothing to follow since it doesn't change what the resume says, only how reliably it's read.
The parts of a Greenhouse application worth real attention
- Custom questions per posting — Greenhouse lets each job posting define its own screening questions, and these vary far more than the standard fields do. A generic answer reused across postings is more visible here than on portals with fixed field sets, because the question itself was written specifically for this role. In our analysis of 9,401 live Greenhouse application forms, the median form asked 10 questions beyond name, email and phone, and 32.1% of employers included an open-ended written question.
- Cover letter, when requested — Greenhouse makes the cover letter field optional on most postings, which means submitting one at all is already a small signal of effort, and a generic one undercuts that signal rather than adding to it. The field is almost always there but rarely mandatory: 83.5% of those forms include a cover-letter field, yet only 3.0% require one.
- Consistency between resume and structured fields — because Greenhouse surfaces both the parsed fields and the original resume file to the recruiter side by side, a mismatch (a job title that doesn't match, a date range that doesn't line up) reads as a parsing error at best and a red flag at worst, even when it's genuinely just the parser's mistake.
How this compares to Workday and iCIMS
Workday and iCIMS both lean harder on structured, multi-step forms with more required fields per application, which is where deterministic autofill saves the most time relative to Greenhouse's comparatively lighter default form. Greenhouse's real cost center is different: it's the custom per-posting questions, which are exactly the fields that reward genuine tailoring rather than fast, repeated field-filling. Knowing which portal you're on changes where your own effort is best spent — fast and accurate on Workday's longer forms, thoughtful on Greenhouse's per-posting questions.
What this means practically
Don't over-optimize a Greenhouse application for a keyword-matching algorithm that mostly isn't there. Optimize instead for a parser reading your resume correctly, and for a human recruiter who's going to read the custom question answers specifically because Greenhouse's design invites more of them per posting than most other portals do.
Fast on the standard fields, sharp on the rest.
ApplyCandid fills Greenhouse's structured fields accurately and drafts custom-question answers grounded in your real resume, so tailoring effort goes where it actually counts.