Greenhouse ATS Resume Guide: Single-Column Parsing, Keyword Matching & Recruiter Scorecard Alignment

How a Greenhouse application works

Greenhouse job posts live on an employer's careers page or on Greenhouse-hosted job boards. The standard form asks for name, email and phone, a resume upload (PDF, Word, plain text and similar common formats are accepted), an optional cover letter, links such as LinkedIn or a portfolio, and any custom questions the employer adds. Many forms also include voluntary demographic questions that are kept separate from the hiring team's view.

Some Greenhouse forms offer to fill your contact details from the uploaded resume. Unlike platforms that rebuild your entire work history into fields, a Greenhouse application generally keeps your resume as a document. The recruiter opens a candidate profile and reads the file in a built-in viewer. That makes Greenhouse friendlier to well-designed resumes than some older systems, but it also means the document itself carries more weight: there is no structured profile to hide behind.

What parsing means on Greenhouse, and why one column still matters

Greenhouse extracts the text of your resume so recruiters can search across candidates. That extracted text is what keyword searches run against, both for the job you applied to and for later roles when a recruiter searches past applicants. If extraction scrambles your content, you can be invisible to search even though your file looks perfect in the viewer.

Multi-column layouts are the usual cause. Text extraction tends to read straight across the page, so a left sidebar of skills and a right column of experience can come out interleaved, with "Python" landing in the middle of a sentence about a product launch. Text boxes and tables add the same risk. A single-column layout keeps extracted text in the same order a human reads it. You can still use bold role titles, a clean rule under each heading and a short skills block; just keep everything in one reading line.

Two checks before you upload: open the PDF, select all, paste into a plain text editor and read it top to bottom. Then run the file through the ATS compatibility calculator. If the pasted text reads in order, Greenhouse search will see what you intended.

Keyword matching: how recruiters actually search

Recruiters using Greenhouse can search candidate profiles and resume text by keyword, and they filter by job, stage, source and tags. Recruiters report using this search heavily when a new role opens, because past applicants and referrals already in the system cost nothing to contact. Your resume may be searched months after you applied, for a job you never saw.

That changes how you should choose words:

• Use the posting's exact terms where they are true. If the requirement says "SQL" and "dbt", write both, not "data transformation tools".
• Include both forms of key terms. "Search engine optimization (SEO)" covers a recruiter who types either one.
• Keep job titles standard. If your internal title was "Member of Technical Staff III", add the market equivalent in plain words in the role line or first bullet, for example "senior backend engineer scope".
• Name the tools in context. A skills list helps search, but a bullet that shows the tool producing a result helps the human who reads the profile next.

Avoid repeating terms to game search. A recruiter who lands on your profile from a keyword hit reads the whole page, and a stuffed skills section reads as padding.

Scorecards: the part of Greenhouse most candidates never see

Greenhouse is built around structured hiring. Before interviews start, the hiring team defines the attributes the role requires, such as specific skills, qualifications and working traits, and assigns them to interview stages. Each interviewer then fills in a scorecard that rates the candidate on the attributes they were asked to assess and gives an overall recommendation. The hiring manager compares scorecards side by side when deciding who moves forward.

The scorecard is built from the same source you have: the job description and the hiring manager's priorities. That means you can usually predict most of its attributes. The requirements list, the "you will" section and any repeated phrase in the posting are strong hints. Interviewers often have your resume open while they fill in the scorecard, so a bullet that maps directly to an attribute gives them something specific to cite in their notes.

Mapping your resume to likely scorecard attributes

Here is how that mapping works for a product manager applying to a Series B software company. The posting asks for experience running discovery, working with engineering on trade-offs, and owning a metric.

• Likely attribute: customer discovery. Weak bullet: "Conducted user research." Mapped bullet: "Ran 30 customer interviews across two buyer segments; findings cut the onboarding flow from seven steps to four and became the Q3 roadmap."
• Likely attribute: technical trade-offs. Weak bullet: "Worked closely with engineering." Mapped bullet: "Chose to ship role-based permissions without SSO to hit a renewal deadline; scoped SSO as a follow-on release with the engineering lead and delivered it eight weeks later."
• Likely attribute: metric ownership. Weak bullet: "Responsible for activation." Mapped bullet: "Owned trial-to-paid conversion for the self-serve plan; moved it from 9% to 13% over two quarters through pricing-page and onboarding tests."

Each rewrite gives an interviewer a scope, a decision and a result they can probe. That is what turns a "Yes" on a scorecard into a "Strong Yes": evidence specific enough to discuss. Our software engineer and data scientist pages show the same approach for technical roles.

Preparing for scorecard-driven interviews

Structured interviews change what a resume has to do after it gets you in the door. In a Greenhouse interview loop, each interviewer is usually assigned a few attributes and a set of questions for them. One person might test system design, another stakeholder management, another a specific domain. They read your resume beforehand looking for the bullets that relate to their assigned attributes, and they often open with "Walk me through this project."

That gives you a practical way to check your resume before you apply:

• Every major requirement should have at least one bullet you can talk about for five minutes. If a requirement has no matching line, an interviewer assigned to it has nothing to start from and has to rate you on general impressions.
• Every number should be one you can explain. Interviewers ask how a figure was measured, what the baseline was and what you personally did. A metric you cannot unpack costs more than it earns.
• Your most recent two roles carry the most weight. Interviewers spend most of their prep time there, so put your strongest evidence for each attribute in recent work where it is true.

Hiring managers compare scorecards side by side, and consistent evidence across several interviewers is what makes a decision easy. A resume that gives each interviewer a clear starting point helps produce that consistency.

Format rules for Greenhouse applications

• One column, standard headings. Experience, Education, Skills, Projects. Keep contact details in the body of the page.
• Text-selectable PDF is fine. Greenhouse displays PDFs well, and a PDF exported from Word or Google Docs keeps your formatting. Avoid image-based PDFs and scanned pages.
• Working links. The form has fields for LinkedIn, GitHub or a portfolio. Fill them, and keep the same links on the resume as plain, readable URLs.
• Clear file name. Firstname-Lastname-Resume.pdf. Recruiters download files and a name like "final_v7.pdf" gets lost.
• Two pages at most for most candidates. One page is common for early-career tech applicants. Senior candidates can use two if the second page carries real evidence.
• No photos, icons for contact details, or skill bars. Skill bars mean nothing to a scorecard and their text, if any, extracts as noise.

Custom questions and cover letters

Employers can add required custom questions to a Greenhouse form, from work authorization and location to short written answers about a specific project. Treat written answers as part of the application, not an afterthought. Hiring managers often read them before the resume, and a sharp three-sentence answer with a concrete example can do more than a generic cover letter.

When the cover letter is optional, a short one helps most when it explains something the resume cannot: a relocation, a career change, or why this company's product matters to you. Keep it under 250 words and make every claim match a line on your resume. If you are changing fields, our Career Change service builds the resume and letter as one argument.

Putting it together

Greenhouse rewards resumes that read cleanly as text and convince a person who is filling in a structured form about you. Build one column, use the posting's real terms, and write bullets that give interviewers evidence to cite. Our writers build every Professional resume against the posting's requirements so each likely scorecard attribute has a matching line. For startups that run Lever or SmartRecruiters instead, see our Lever and SmartRecruiters guide.

Key takeaways

• Greenhouse keeps your resume as a document that people read, and extracts its text for keyword search across past and current applicants.
• A single-column layout keeps extracted text in reading order, so search finds the terms you actually wrote.
• Interviewers rate you on a scorecard built from the job description, so most attributes can be predicted from the posting.
• Write bullets with scope, a decision and a result, giving interviewers evidence to cite on the scorecard.

Frequently asked questions