How to recognize Greenhouse
boards.greenhouse.io/[company] or job-boards.greenhouse.io/[company] — e.g. job-boards.greenhouse.io/airbnb
Greenhouse-hosted job boards live on the greenhouse.io domain; many employers embed the same form on their own careers pages, so check where the Apply form actually submits.
What Greenhouse is, and who uses it
Greenhouse is a hiring platform built by Greenhouse Software, Inc., used — per the company's own materials — by over 7,500 companies, with a customer base that skews toward technology and mid-market employers (HubSpot, Duolingo and Gong appear in its own boilerplate; Airbnb and Stripe run live Greenhouse boards at the time of writing). If a startup or scale-up is hiring, there's a good chance the form you're filling in is Greenhouse.
Compared with enterprise systems like Workday or Taleo, the candidate experience is deliberately lighter: typically one form, no mandatory account, and employer-chosen custom questions.
The application flow: one form, no required account
A Greenhouse application is submitted through the job post's form: your resume, contact details, and whatever custom questions the employer configured. There's no account requirement to apply. An optional candidate portal, MyGreenhouse, lets you prefill applications and track the ones you've submitted — with two honest caveats from Greenhouse's own FAQ: you'll only see a status if the employer chose to share it, and the portal "can't change an application, make hiring decisions, or contact recruiters for you."
The custom questions deserve more attention than most candidates give them. As covered below, they're the only part of a Greenhouse application that can trigger an automatic outcome.
Resume parsing: the failure modes Greenhouse itself documents
Greenhouse publishes an explicit support article on unsuccessful resume parses, which is rare candor for an ATS vendor and worth reading in its own right. Per that article, parsing struggles or fails on: files over 2.5MB; image files instead of documents (Greenhouse recommends .docx or .pdf); graphics, photos and word art; spaced-out lettering ("J O H N S M I T H"); complex layouts with tables, headers, footers or columns; and contact details placed in headers, footers or text boxes.
Just as important is what a failed parse means: per the same documentation, the resume is still attached to your candidate record, and details get entered manually — a parse failure does not reject you. Co-founder Jon Stross has said the same on the record: Greenhouse can't parse an image, and Word or PDF is the format to use. The cost of a bad parse isn't rejection; it's that your information is harder to search and slower to review, which matters when a recruiter is prioritizing a large pipeline.
What recruiters see: application review and scorecards
Greenhouse's documentation describes an Application Review stage as the automatic first stage of every job's pipeline: a recruiter views your resume, cover letter, custom-question answers and source, and chooses Advance or Reject — a manual action. From there, structured interviews run on scorecards: predetermined criteria each interviewer rates, with an overall recommendation (the documented scale runs Definitely Not / No / Yes / Strong Yes), reviewed together at a candidate roundup.
For preparation, the scorecard model has one practical implication: employers using Greenhouse are typically evaluating against defined criteria drawn from the role. The posting's stated requirements are your best public view of those criteria — which is an argument for tailoring your resume and your interview examples to them, and it's the same logic our interview prep pages are built on.
The truth about auto-rejection in Greenhouse
Greenhouse does have a documented Auto-reject feature — and being precise about what triggers it is exactly the kind of honesty this page exists for. Per Greenhouse's own support documentation, application rules (Auto-Tag, Auto-Advance, Auto-Reject) fire based on an applicant's answers to custom application questions — yes/no, single-select or multi-select. Not resume content. Not keyword density. Employers can attach an automatic rejection email to the rule.
On resumes, the company's position is stated plainly across its documentation and its founders' public interviews: rejection is a human action, and Greenhouse's published AI principles say AI "can inform, summarize, and surface insights," but is "never the final decision-maker." So the practical guidance splits cleanly in two: treat the application questions as the real screening step and answer them exactly and truthfully, and treat the resume as the document a human will read after software has parsed and organized it.
Preparing your resume for Greenhouse: the checklist
Every item below follows from the documented behavior described above — nothing here is folklore.
- Upload a text-based .docx or .pdf under 2.5MB — both the format recommendation and the size limit come from Greenhouse's own parsing documentation.
- Skip decorative formatting: tables, columns, graphics, photos, word art and spaced-out lettering are all on Greenhouse's documented list of parse-breakers.
- Keep your name and contact details in the document body, not in a header, footer or text box — another documented failure mode.
- Answer the employer's custom application questions precisely and truthfully — they're the only documented trigger for automatic rejection in Greenhouse.
- Don't count on the application status updating: Greenhouse's own FAQ says you only see a status if the employer chose to share it. Silence usually means nothing either way.
- Write for the human at Application Review: one recruiter will look at your resume and choose Advance or Reject, so the top third of page one should make your fit obvious.