Greenhouse helps recruiters screen resumes through employer-defined application questions, searchable candidate records, hiring stages, job criteria, and structured scorecards. It does not apply one universal pass score. Your best strategy is to meet baseline requirements honestly, use the posting's exact terms where accurate, and provide clear evidence a recruiter can map to each criterion.
That distinction matters. Greenhouse is a recruiting platform configured by each employer, not a single robot making identical choices for every company. A recruiter may review applications in order, filter by a baseline answer, search for a required system, compare profiles with the job plan, or revisit a past applicant. The resume is one record inside that workflow.
This article focuses on recruiter behavior: scorecards, knockouts, keyword search, stages, and evidence. For file-specific guidance, read the Greenhouse tailoring guide. For broader ATS mechanics, see how to beat an ATS system without tricks.
Key Takeaways
- Greenhouse workflows reflect employer choices, not one global algorithm.
- Knockout questions usually test explicit baseline conditions.
- Recruiter search favors exact titles, tools, credentials, and domain nouns.
- Scorecards organize human evidence; they are not a public ATS percentage.
- Strong applications connect posting language to verifiable work.
- Simple files help both Greenhouse and Workday retain context.
What a Greenhouse resume screen actually looks like
The process begins before your application arrives. The hiring team creates a job, defines responsibilities, sets an interview plan, assigns reviewers, and may build a scorecard. Recruiters then receive candidate records containing the uploaded resume, application answers, source, contact information, activity history, and internal notes. A well-run team agrees on baseline criteria before opening the pool.
At first review, a recruiter often checks four categories. First is eligibility: location, work authorization, required license, schedule, travel, or another explicit condition. Second is role identity: whether recent titles and functions resemble the need. Third is evidence: named tools, methods, customers, projects, scale, and outcomes. Fourth is communication: whether the document lets a reviewer locate relevant facts quickly.
The reviewer may advance the candidate to a recruiter screen, reject with a reason, request another review, or leave the application for later. Greenhouse records stage movement and team activity, but it does not force every company to use the same order. Some organizations review every qualified applicant; others prioritize referrals, sourcing campaigns, or early applications while continuing to accept more.
Recruiters also work under legal and policy constraints. The U.S. Equal Employment Opportunity Commission explains federal protections against employment discrimination. The Society for Human Resource Management publishes practitioner material on structured hiring and selection. Neither source says a particular ATS guarantees fairness; employers remain responsible for job-related criteria and consistent processes.
Key Takeaway: Greenhouse stores and moves candidate evidence through an employer-designed process. Make the first screen easy by presenting baseline eligibility and role evidence in plain language.
Knockout questions: what can stop an application early
A knockout is not a hidden keyword puzzle. It is usually a direct application question connected to a condition the employer treats as mandatory. Examples include holding an active license, working a stated shift, residing in an approved location, meeting an age requirement where lawful, accepting travel, or possessing authorization that matches the role. An employer can configure follow-up actions based on an answer.
Read qualifiers carefully. “Are you legally authorized to work?” is not identical to “Will you now or later require sponsorship?” “Do you hold this license?” is not asking whether you plan to earn it. “Can you work three days in the office?” is not asking whether remote work is your preference. The accurate answer may remove you from consideration, but an inaccurate answer can cause a later withdrawal.
Voluntary demographic questions are generally separated from normal hiring review and should not be treated as resume criteria. Accommodation needs also should not be guessed from a resume. If a question appears unrelated to the work, save a copy and use the employer contact channel. The EEOC provides public information about applicant rights and prohibited discrimination.
Do not bend resume wording to evade an explicit baseline. If a role requires an active CPA and you are studying for the exam, write “CPA candidate” only if that status is accurate. You can still seek positions where the credential is preferred rather than required.
| Screen type | What it tests | Best response |
|---|---|---|
| License or certification | Current required qualification | Give the truthful status and date where requested |
| Work authorization | Legal employment and sponsorship need | Answer each exact question separately |
| Location or schedule | Ability to meet operating needs | Confirm only arrangements you can keep |
| Years or domain background | Employer-defined experience floor | Count relevant work accurately; explain adjacency in the resume |
Key Takeaway: Treat knockout questions as factual eligibility checks. Accurate answers protect your candidacy and make later recruiter conversations consistent.
How recruiters use keyword search in Greenhouse
Search helps a recruiter find a manageable group inside a large database. Useful search terms are usually nouns: job titles, product names, programming languages, clinical credentials, sales segments, regulations, methodologies, locations, and customer types. Recruiters may combine related terms because candidates use different labels. A search for “account executive” may include AE; a search for “Amazon Web Services” may include AWS.
Exact posting language is valuable when it is true. If the job asks for customer success in a B2B SaaS environment and your resume only says “supported accounts,” the recruiter has little searchable context. A truthful rewrite could say “Managed B2B SaaS customer onboarding and renewal support for a 42-account portfolio.” The terms now have evidence and a human-readable relationship.
Search is not proof of competence. A candidate can appear because a term exists in a skills list, an old role, or even an education section. The recruiter then opens the record and checks recency, depth, and relevance. Repeating a phrase twenty times does not create stronger experience. It can make the document harder to trust.
Context also prevents false matches. Put each tool near the role where you used it. Name the project, users, process, or outcome. If you have only coursework, label it as coursework. If you have production ownership, state the operating scope. Learn which terms matter in what keywords an ATS looks for.
Key Takeaway: Use the exact searchable noun once where it naturally belongs, then prove it with context. Retrieval gets a resume opened; evidence keeps it open.
Greenhouse scorecards and structured evidence
A scorecard translates the role into attributes interviewers can assess. Categories can include technical ability, functional experience, communication, management, operating judgment, customer knowledge, or company values. The hiring team decides what belongs on it. Greenhouse supports the structure, while people define and rate the criteria.
Before an interview, a recruiter may use the same criteria informally or through a documented screen. Suppose the scorecard asks for SQL analysis, cross-functional communication, and ownership of a weekly reporting process. A resume that lists “SQL” in Skills but offers no analysis example supports only a weak inference. A bullet describing a weekly reporting workflow, stakeholders, query work, and decision supported gives the reviewer something to map.
Scorecards are often misunderstood as a secret 0–100 ATS grade. They are not the same as a public resume checker score. Interviewers can submit ratings and notes against defined attributes, and hiring teams can compare evidence. Integrations may add assessments or recommendations, but the employer chooses those tools and remains responsible for its decisions.
Your practical task is to infer the likely criteria from repeated posting language. Look at responsibilities, minimum qualifications, preferred qualifications, and expected outcomes. Repetition across those areas usually signals a priority. Build one strong example for each priority rather than ten vague claims.
Key Takeaway: Reverse-engineer the scorecard from repeated job requirements. Give each likely criterion a compact, verifiable example instead of relying on a detached skills list.
Before-and-after evidence for a recruiter screen
The strongest rewrite does not merely insert a keyword. It clarifies what you did, where you did it, who or what was affected, and why the work mattered. Use real scope. If you do not have a reliable number, name frequency, ownership, complexity, audience, or decision instead.
Before: Responsible for onboarding customers.
After: Owned B2B SaaS onboarding from kickoff through adoption review, coordinating implementation, support, and customer stakeholders across a 35-account portfolio.
Before: Used SQL and made dashboards.
After: Wrote SQL queries for weekly product-usage reporting and maintained a dashboard used by product and customer success leaders to identify stalled accounts.
Before: Helped with hiring and interviews.
After: Coordinated structured interview loops in Greenhouse, prepared interviewer packets, monitored scorecard completion, and resolved scheduling changes across engineering roles.
Before: Managed projects across teams.
After: Led the operating cadence for a billing migration, tracking dependencies across finance, support, engineering, and legal through launch readiness.
Each “after” line contains searchable nouns and scorecard evidence. None claims a result the candidate cannot verify. For more patterns, use resume bullets that show outcomes.
Key Takeaway: A useful bullet lets a recruiter underline the criterion and the proof in one sentence. Add scope only when you can explain its source.
A numbered Greenhouse application checklist
Use this sequence after tailoring and before uploading. It covers both the record a recruiter will search and the evidence a scorecard-driven team will evaluate.
- Mark every explicit must-have in the posting. Separate factual eligibility from skills you can demonstrate.
- Write the exact target title in the summary when it accurately describes your direction and background.
- Choose six to ten role-specific nouns: tools, methods, credentials, customer types, regulations, and deliverables.
- Place each high-priority noun in the dated role or project where you used it. Do not leave all proof in Skills.
- Draft one evidence example for each likely scorecard attribute. Include scope, frequency, audience, or outcome.
- Check every knockout answer against the wording of the question. Do not infer that two authorization questions mean the same thing.
- Use conventional headings: Summary, Experience, Skills, Education, and Certifications where relevant.
- Paste the resume into plain text. Confirm that company, title, dates, and bullets remain in the intended order.
- Review the final uploaded application, including manually entered fields, attachments, portfolio links, and contact details.
- Save the job description and submitted resume so interview preparation matches the exact evidence the recruiter received.
See what a recruiter can find
Run your tailored resume through HireFlow, compare it with the posting, and fix evidence gaps before the Greenhouse application.
Check your resume with HireFlowIf the same employer sends you to Workday for another division, do not assume identical fields. Review the Workday resume format and verify the parsed profile there as well.
Key Takeaway: Control what you can: truthful answers, exact role language, visible evidence, clean parsing, and a saved copy of the submitted application.
What recruiters document after opening your application
Screening is not only a yes-or-no decision. Recruiters often need to leave a useful record for the hiring manager and for later stage decisions. A note may summarize the closest title match, years in a relevant function, required credentials, location, compensation context when lawfully collected, and the strongest evidence for the next conversation. Clear resume facts make that summary more accurate.
Ambiguity creates work. If three overlapping roles appear under one employer with no dates, the reviewer has to guess progression. If every technology lives in one skills block, the reviewer cannot tell whether SQL was used last month or ten years ago. If a summary claims team leadership but the experience section identifies no team, direct reports, project group, or decision authority, the claim is difficult to carry forward.
Build a resume that supports a short, accurate recruiter note. Use month-and-year dates, recognizable titles, and one-line company context when the employer is unfamiliar. Put required credentials in a dedicated section with status and issuer. For each priority, provide at least one bullet that names your action, operating setting, and scope. A recruiter should not need to combine clues from four pages to establish one qualification.
Stage decisions can also involve disposition reasons. Employers may categorize why an application did not move forward, such as missing a minimum requirement, stronger alignment elsewhere, role closure, location, or candidate withdrawal. Categories differ by employer and should not be interpreted as a universal Greenhouse taxonomy. A rejection therefore does not reveal a secret keyword score, and resubmitting the identical file rarely addresses the underlying question.
If you apply to another role at the same company, tailor the evidence again. Candidate history can help a recruiter see prior interest, but the new requisition has its own requirements and interview plan. Reuse accurate background facts while changing the top summary, priority skills, and bullet order to match the new work. Never alter dates, credentials, or outcomes between applications merely to look closer.
A referral also does not replace the record. It may draw attention to your application or provide additional context, but recruiters still need evidence that supports the role criteria and a process consistent with employer policy. Give the referrer the exact posting and final resume so their explanation matches what Greenhouse contains.
Key Takeaway: Write facts that a recruiter can summarize accurately for the hiring team. Clear chronology, current credentials, and criterion-level evidence reduce avoidable uncertainty.
Make the recruiter decision easier to support
A Greenhouse screen is not won by hiding text, repeating every noun, or guessing a secret threshold. Recruiters need defensible reasons to move someone forward. Give them those reasons in the order they need them: eligibility, relevant identity, searchable domain language, and concrete evidence against the role criteria.
Review your match with HireFlow, compare the result with what a good ATS score can and cannot tell you, and keep the final file readable for both Greenhouse and Workday.
Key Takeaway: The best Greenhouse resume is searchable, truthful, and easy to map to a structured hiring decision. Optimize for evidence, not folklore.
Frequently asked questions
Greenhouse gives employers configurable tools. A company can use application rules, knockout questions, stage requirements, and integrations, but each employer decides its workflow. A rejection may come from a stated eligibility answer, a recruiter decision, a filled role, or another configured process.
Yes. Authorized recruiting users can search candidate records and resumes, and many teams use job titles, skills, tools, credentials, locations, and Boolean combinations to narrow a pool. Search is only one input; the recruiter still evaluates evidence and role requirements.
A scorecard is a structured set of attributes used to evaluate candidates consistently. Teams may define skills, experience, values, and role outcomes, then collect interviewer ratings and notes. Resume screeners often use the same job criteria before interviews begin.
Not in the generic checker sense. Employer-defined scorecards support human evaluation against selected attributes. Greenhouse can also connect to assessment or matching tools, but there is no universal Greenhouse resume score shared across companies.
They are employer-written application questions tied to baseline conditions such as work authorization, location, required licensure, schedule, or willingness to travel. Some answers can trigger an automated action. Answer accurately because later verification can expose a false response.
No. Copying language without evidence creates a weak and potentially misleading application. Use exact terms only when they describe your real work, then connect each important term to a project, responsibility, credential, scope, or result.
A text-based PDF usually works, but a simple DOCX can be safer when a posting allows it. Avoid scanned images, text boxes, decorative columns, and header-only contact details. Copy the file into plain text to inspect reading order before uploading.
Both can store applications, parse resumes, and support recruiter search, but employer configuration matters more than the brand name. Workday often asks candidates to verify parsed profile fields. Greenhouse commonly centers the application, recruiter stages, scorecards, and interview plan.