Who uses Greenhouse — and why it matters
Greenhouse is the ATS of choice for most high-growth tech companies: Airbnb, Figma, Notion, DoorDash, Robinhood, Duolingo, and thousands of Series B–D startups. If you're targeting the tech startup tier, there's a high chance your application is going into Greenhouse.
The good news: Greenhouse has a significantly better parser than Workday or Taleo. It handles PDFs reliably, supports two-column layouts better than most legacy systems, and its keyword matching is more semantically aware. The bad news: "better than Workday" doesn't mean forgiving — there are still formatting and keyword patterns that hurt your score.
What Greenhouse actually does with your resume
Step 1: Parse into a candidate profile
Greenhouse extracts your resume into structured fields: name, contact, current company, current title, experience list, education, and skills. This profile is what recruiters see first — not your resume. If the parser misreads your current title or miscategorizes a skill, that's what's in the recruiter's view.
Step 2: Score against the job's scorecards
Greenhouse uses "scorecards" — structured evaluation criteria that hiring managers define per role. These include required skills, experience level, and specific attributes. Your resume is matched against these scorecards. How closely your extracted profile matches the scorecard criteria determines how you're ranked against other applicants.
Step 3: Surface to recruiters by score
Recruiters filter by score, status (new, reviewed, interview), and tags. Candidates ranked in the top tier appear first. Everyone else requires the recruiter to scroll past the fold.
Formatting tips specific to Greenhouse
Single-column is still safest, but two-column is workable
Unlike Workday and Taleo, Greenhouse's parser handles two-column layouts better — it typically identifies columns and reads each independently. That said, single-column is still the most reliable. If you use a two-column layout, test it: copy-paste your resume text into a plain text document and see if it reads in the right order.
Put your current title exactly as it appears in the JD
Greenhouse's parser puts heavy weight on your most recent job title. If you're applying for a "Senior Software Engineer" role and your title is "Software Engineer II," that gap will score lower than if the title matches. Where honest, use the most standard version of your title: "Software Engineer II" → "Senior Software Engineer" if that's the industry-standard equivalent at your seniority.
Skills section should mirror the JD's language exactly
Greenhouse's scorecard matching is keyword-sensitive. "Node.js" and "NodeJS" are not the same to every version of the parser. Match the exact capitalisation and punctuation from the job description for each technology you list.
Keep your PDF text-selectable
Greenhouse accepts both PDF and Word docs. If you submit a PDF, make sure the text is selectable (not a scanned image). Test: open the PDF, click your name. If you can highlight it, you're good.
Keyword strategy for Greenhouse-heavy companies
The companies that use Greenhouse — Airbnb, Figma, Notion — tend to write more specific, technical JDs. They're not looking for "5 years of JavaScript experience." They're looking for "experience with real-time collaborative editing," "designed systems serving 10M+ users," or "worked in a product-led growth environment."
These aren't keywords — they're outcome phrases. To score well, your resume needs to speak their language: results and context, not technology lists.
- Bad: "React, TypeScript, GraphQL"
- Better: "Built collaborative document editor in React + TypeScript, serving 200K daily active users"
Check your score before applying
Before submitting to any Greenhouse-powered application, paste your resume and the JD into Applyr's free ATS checker. You'll see your match percentage, the specific keywords missing from your resume, and a breakdown by section. Target 75%+ before clicking Apply.
For Greenhouse companies specifically — Figma, Notion, and their peers — look for outcome-based phrases in the JD (not just tech keywords) and make sure your bullets reflect them.