Greenhouse runs the hiring stack for most of the well-known startups you can name. Stripe, Airbnb, DoorDash, Notion, Vercel, Ramp, Brex. Roughly 4,000 companies use it as their primary applicant tracking system, concentrated heavily in venture-backed tech. If you have applied to a Series B through pre-IPO startup in the last few years, you almost certainly went through Greenhouse.
The system was designed around a specific belief: that hiring decisions should be structured, documented, and consistent across every interviewer. That belief shapes how Greenhouse handles your application in ways that do not match what most applicants assume an ATS does.
Applying through a Greenhouse portal? Check these first.
- - Treat the cover letter field as a real document, not optional.
- - Answer the custom application questions specifically. They feed the recruiter's first read, not the parser.
- - Use plain section labels. The parser is competent on standard formats and confused by everything else.
- - If the company asks for portfolio links or work samples, include them. Greenhouse scorecards often have a dedicated "work sample" line item.
Greenhouse is a recruiter tool, not a screening tool
This is the key distinction that changes everything about how to write a resume for Greenhouse jobs. Older ATS platforms were built to filter thousands of applicants down to a shortlist before a human ever looks. Greenhouse was built to give recruiters and interviewers a shared workspace once they decide a candidate is worth looking at.
Greenhouse does parse your resume into a candidate profile and does run keyword matches against the job posting. But the parser output sits next to the original resume file inside the recruiter's queue. Most Greenhouse recruiters open the actual PDF and skim it. They are not relying on the parsed profile to make a yes/no call.
The practical effect is that resume readability matters more than keyword density. A resume that scores 90% on automated keyword match but reads badly to a human will lose to a resume that scores 75% but tells a clear story.
Scorecards: the document that actually decides your fate
Every Greenhouse job has a scorecard. The scorecard lists the attributes the company has decided matter for this specific role: skills, experience areas, traits, qualifications. Each interviewer in the loop fills in a score and notes against each attribute after they meet with you. The final hiring decision is supposed to come from the aggregate of those scorecards, not from any one person's gut feel.
You never see the scorecard during the application, but the public job posting is built from it. The bullet points under "What we are looking for" or "Requirements" almost always map directly to scorecard line items. The implication is concrete: if a job posting lists "experience with distributed systems" and "comfort owning ambiguous problems," your resume should make it obvious that both apply to you. Not the keywords themselves, but evidence in the bullets under your job history.
How to read a Greenhouse job posting
Treat each "requirement" bullet as a scorecard line that an interviewer will rate you against. Your resume should give each interviewer enough evidence to score you on every one. If you cannot point to a specific accomplishment that maps to a given bullet, that line item is going to be filled in by the interviewer's best guess from limited information, which is rarely favorable.
The custom application questions are not optional
Most Greenhouse applications include custom questions specific to the role. "Why are you interested in this position?" "Describe a project where you owned the technical decisions." "What is your salary expectation?" These are not screening tools in the knockout sense. They are the recruiter's first read of how you think.
A short, generic answer signals low effort. A detailed, specific answer signals serious interest. Recruiters at Greenhouse-powered companies read these answers before they open the resume, because the answers tell them whether the resume is worth reading carefully.
Salary expectation questions deserve special care. Greenhouse stores your answer on your candidate profile, and it follows you through the interview process. If you anchor low, that anchor sticks. If you put "competitive" or "negotiable," the recruiter has to ask you anyway, and the conversation starts from scratch. Putting a specific range tied to market data for the role and level is the most common recruiter recommendation.
How parsing works and where it breaks
Greenhouse's resume parser handles standard formats well. A single-column resume in PDF or DOCX with conventional section headers parses cleanly almost every time. The parser populates a structured candidate profile with name, contact, work history (company, title, start date, end date, responsibilities), education, and a flat skills list.
Where the parser breaks down is similar to most ATS systems: multi-column layouts confuse reading order, tables and text boxes can be skipped, content in headers or footers may be treated as metadata and dropped, and creative section titles like "Where I have shipped" instead of "Experience" cause the parser to miscategorize entire blocks. None of these are catastrophic at Greenhouse the way they are at strict ATS systems, because recruiters open the actual file, but they do mean the structured profile is unreliable for keyword searches the recruiter might run later.
Greenhouse Source and the inbound vs outbound distinction
Greenhouse has a separate product called Greenhouse Source that recruiters use to find passive candidates. Sourced candidates enter the pipeline differently than inbound applicants. They typically skip the initial resume screen because the recruiter has already decided they are worth talking to.
If you have applied to a company and also had a recruiter from that same company reach out to you separately, the two paths can collide inside Greenhouse. The recruiter's outreach creates a sourced candidate record. Your inbound application creates a separate inbound record. Greenhouse can merge them, but only if the email matches. Use the same email address everywhere if you want the two paths to consolidate.
What recruiters actually see when your application lands
Inside Greenhouse, a recruiter looking at an open job sees a kanban-style view. Columns for "Application Review," "Recruiter Screen," "Hiring Manager Screen," "Onsite," "Offer," and so on. Your application starts in the leftmost column.
The recruiter's queue does not rank candidates by automated match score the way Workday's queue does. Greenhouse can sort by application date and can show a basic match indicator, but the queue does not push high-match candidates to the top. The recruiter works through the queue in date order, opening each application, reading the answers to custom questions, and scanning the resume.
The practical implication: applying early matters more at Greenhouse- powered companies than at companies running keyword-ranking systems. If a job has been live for a week and 200 applications are stacked up, your late-arriving application sits at the bottom of the queue regardless of how strong it is. Recruiters often stop reviewing once they have a shortlist, even if your application is still in the unread pile.
Greenhouse rewards specificity. The system itself does less filtering than recruiters at other ATS platforms do. The flip side is that the first 90 seconds a recruiter spends with your application is doing all the work. The resume has to read well, the custom answers have to be substantive, and your specific evidence has to map to the scorecard line items in the job posting.
How Ajusta accounts for Greenhouse-specific behavior
When Ajusta detects a Greenhouse job posting (the URL contains boards.greenhouse.io or job-boards.greenhouse.io, or the page metadata identifies Greenhouse), the optimization shifts from keyword density toward scorecard mapping. Ajusta extracts the requirements list from the posting, treats each bullet as a likely scorecard line, and checks that your resume has at least one specific accomplishment that maps to each line. The keyword check still runs, but a Greenhouse-tuned scan weighs readability and evidence-per-requirement higher than raw keyword matching.
Frequently asked questions
Is Greenhouse an ATS or something else?
Greenhouse is an applicant tracking system, but it is positioned as a structured-hiring platform rather than a screening tool. It handles applications, candidate profiles, interview scheduling, scorecards, and offer workflows. Other ATS platforms focus on filtering inbound volume; Greenhouse focuses on consistency once a candidate is in the pipeline.
Does Greenhouse automatically reject resumes?
Generally no. Greenhouse does not have aggressive automated knockout filtering by default. Most rejection in Greenhouse pipelines comes from a human recruiter reviewing the application. Some companies configure custom questions as auto-disqualifiers (work authorization is the most common), but the platform is not built around heavy automated screening the way Workday and iCIMS are.
Does the order of jobs on my resume matter for Greenhouse parsing?
Reverse chronological is the safest format. The parser expects to see your most recent position first and walks down through older entries. Functional resumes that group by skill rather than time can produce a structured profile with empty or malformed work history entries. The parser is not picky about exact date formats, but consistency helps.
How important is the cover letter in a Greenhouse application?
More important than at most other ATS platforms. Greenhouse-powered companies use the cover letter and custom application questions as the first signal of effort and fit. A blank cover letter or a generic one-line answer to a custom question is read as low interest. A specific, role-relevant cover letter is often the difference between getting a recruiter screen and getting passed over.
Do referrals work differently in Greenhouse?
Yes. Greenhouse has a built-in referral feature. When a current employee refers you, you typically apply through a special referral link that flags your application as referred inside the recruiter's queue. Referred candidates are reviewed faster and at a higher rate than cold inbound applications at most companies. Ask the referring employee to submit the referral through the formal Greenhouse flow rather than just emailing your resume to a recruiter.
Can I tell if a company uses Greenhouse?
Check the URL of the careers page. Greenhouse-powered postings live at subdomains like boards.greenhouse.io, job-boards.greenhouse.io, or the company's own domain proxying to one of these. The application interface has a distinctive layout: a simple form for resume upload, cover letter, and a small set of custom questions. There is no left-sidebar profile navigation like Workday has.
What happens if my resume parses badly in Greenhouse?
Less bad than in stricter ATS systems. Recruiters open the original file rather than relying on the parsed profile. However, the parsed profile drives any keyword searches the recruiter runs later, including pulling candidates from one job into the consideration set for a different open req. A badly parsed profile reduces those discoverability moments.
How fast do Greenhouse applications usually get reviewed?
Highly variable. Smaller companies with active recruiters often review within 48 hours. Larger companies with hundreds of applications per role may take one to three weeks. Greenhouse has no SLA enforcement. If a posting has been live for more than two weeks, you are competing with a stack of earlier applications that the recruiter may have already shortlisted from.
Should I submit my application late at night to skip the queue?
Submission time has no measurable effect on application order inside Greenhouse. Recruiters work through their queue during business hours regardless of when an application arrived. Applying within 48 hours of a posting going live is the meaningful timing factor; whether you submit at 9am or 2am makes no difference.