Skip to content

Greenhouse AI screening: CV review, interviews or both?

Choose CV screening, AI interviews or both for Greenhouse. Compare three hiring examples to see which change would save work without adding duplicate stages.

· 8 min read

A candidate profile and conversation on a laptop representing application review and interviews.

Four hundred unread applications call for a different fix from sixty repetitive recruiter calls. The first problem is reviewing information you already have. The second is collecting answers you still need.

Start with CV screening when reading applications is the bottleneck. Test an AI interview when repeated first calls consume the time. Use both only when each improves a separate part of the process.

In Greenhouse, decide when CV review is enough, when an interview adds evidence and when to keep the human conversation unchanged.

Name the problem before choosing the pilot

Open a few applications for one vacancy and find the next piece of work each is waiting for. Is someone reading the CV, asking a question, reviewing a finished report or deciding whom to invite?

A manager who takes four days to read finished feedback has a review-schedule problem, not a shortage of screening reports. Resolve that before generating more.

Write the pilot objective around the work you found: “Reduce the effort needed to review the graduate applications” or “Collect the troubleshooting example we ask for in every support first call”. That makes it possible to judge whether the change helped.

Check what Greenhouse already does for you

Start with the tools and settings the team already uses. Greenhouse’s application rules can act on answers to job-post questions. Its Talent Matching FAQ describes an AI-assisted review feature available with the Real Talent add-on. A proposal for another tool should acknowledge that baseline rather than assume every Greenhouse team is starting from manual keyword searches.

Greenhouse also offers Voice AI, a two-way first interview using your team’s questions and scoring criteria. Include it when comparing interview options; do not assume that adding interviews necessarily means buying from another supplier. Greenhouse says Voice AI integration capabilities vary by ATS, so check which actions your setup supports. Greenhouse’s integration overview Confirm what your current agreement includes and price the proposed use.

That does not settle the purchase. A second tool may provide useful information or a better working process. Test the specific improvement you expect.

Do not compare one system reading a CV with another system reading the CV plus a new interview and call the difference “better CV screening”. The second route has additional information. Evaluate the value and cost of collecting it separately.

Also check the cases your current process sets aside. The Talent Matching FAQ also describes a manual-review route for applicants who cannot be scored, including unreadable CVs and opt-outs when the employer has enabled that option. Your pilot must handle unresolved applications too, not just the easiest completed results. An AI opt-out needs the appropriate non-AI review, not a workaround that sends the application to another AI supplier.

Three vacancies, three sensible starting points

These workloads are examples, not volume thresholds for buying a tool.

Graduate analyst: review the 400 applications already waiting

Test assisted CV review against the agreed graduate criteria. Keep source checking, unclear-case review and the later practical exercise. Relevant university projects must remain visible when the role accepts them.

Keep the tool if reviewers can complete a sound review with less work. A report that saves reading time by overlooking project experience has not solved the problem.

Support specialist: replace the repeated part of 60 first calls

Test an AI interview with applicants already selected for that stage. Keep report review, necessary clarification and the customer-writing exercise.

The test succeeds when those answers let the next interviewer move on. If recruiters still need the original call to collect the same history, find out whether the questions, report or access failed before expanding.

Specialist scientist: keep the research lead’s conversation

When a small applicant group needs expert discussion, an extra automated interview may only delay it. Improve the brief first: the relevant research, the applicant’s contribution and the technical question still open.

The lead may benefit from organised CV evidence without needing another interview stage. Buy that narrower improvement only if it is useful.

For a CV-only pilot, keep the assessment question fixed

For the graduate analyst, agree what the application must demonstrate before the practical exercise. A project can describe checking data and explaining a finding; the later task can test how the applicant does that work now. Do not ask a CV score to establish both.

Accept the routes in your brief, including relevant study or project work. A familiar university or employer name is not a substitute for the work described.

Use an authorised set of applications and keep the original documents available to reviewers. Compare the assisted review with the work the team would otherwise do. Ask whether the report identifies the relevant project, preserves the applicant’s contribution and makes missing information clear.

Count time spent checking errors and opening source material. Inspect applicants the tool did not recommend as well as those at the top of the list. An attractive shortlist does not reveal whether strong applicants were omitted.

Keep the later human assessment unchanged initially where it still serves a valid purpose. That helps you understand the effect of the CV-review change. Do not preserve a faulty requirement merely for the sake of a tidy comparison; correct it and record the change.

Screened’s Greenhouse results guide, available to signed-in users, describes written assessments, fields, tags and notes. Test whether those outputs help the actual reviewer, not just whether they appear somewhere on a profile.

For an interview pilot, identify the call you will no longer repeat

Start with a group the employer has already chosen for an appropriate first-screen stage. Define the missing information and the later handover before sending invitations.

For the support vacancy, the first interview might ask about a customer issue the applicant investigated, what they checked and when another team became involved. The next human stage can use a supplied customer scenario to assess how they respond now. It does not need to begin with the entire work history again unless there is a specific reason.

A useful handover could say:

The applicant described checking the order and dispatch record before contacting fulfilment. They did not say what update they gave the customer while waiting. In the customer exercise, ask them to draft an update for the supplied case and explain the next action. There is no need to retell the whole earlier incident.

The first interview records what the applicant says they did; the exercise shows the response they can produce for a supplied problem. The US Office of Personnel Management’s work-sample guidance describes tasks that mirror work needed on entry. Neither step should receive credit for evidence it did not collect.

Be explicit about calls you retain. A shorter conversation about salary, expectations and the opportunity may still be valuable. Count it alongside report review and candidate support rather than assuming that every minute of the old call disappears.

Combined screening should remove duplication, not hide it

A combined route can make sense when both the application queue and first-call workload are genuine problems. Design the sequence rather than switching on two features independently.

Decide which applications the CV review helps assess, who chooses the next stage and what the interview adds. Identify cases needing clarification or an alternative route. Do not assume that a missing CV or an incomplete interview means the applicant failed the job requirements.

Record the proposed change in a few sentences:

We will keep human decisions after application review. For selected support applicants, the AI interview will ask how they investigated a customer problem. The recruiter will review that report and handle unresolved questions. The later customer exercise remains. We will remove the separate call that only repeats the same experience questions.

That is a process to test, not a saving already achieved. A retained step may become shorter: a recruiter could still call candidates about the role while spending less time collecting their work history. Compare the complete workload, including both reports and those calls. If the total grows, explain what better information justifies the extra work.

Configure the pilot without changing every job

Screened’s Stage Mapping guide, available to signed-in users, separates intake, result updates and stage movement. Interview stage mapping does not enable invitations on its own, and shared settings can affect other connected jobs.

Have the administrator check the scope before adding the pilot job. Review applications already in the intake stage, keep unnecessary automatic movement off and inspect existing Greenhouse message rules. A pilot intended for a small current group should not accidentally include an old backlog.

Follow the actual candidate journey once with a controlled test application. Screened’s interview guide distinguishes scheduled phone interviews from browser interviews without booking. Either route still needs clear instructions, support and an agreed way to handle candidates who cannot use the standard format.

Measure the whole process, not just report speed

Review four things together: staff work, the information collected, candidate effort and the delay before a useful next conversation. A fast report is not a faster process if it sits unread or adds another waiting period.

Keep technical interruptions and pending appointments separate from completed assessments. Name the reviewer and agree when to pause the affected process. A report for the wrong applicant or a material invented claim needs immediate review; do not wait for it to recur before containing the problem.

Bring the pilot back to a decision for this vacancy. For support, a proposal might read:

Our CV review already works, so we are not changing it. We will test whether AI interviews collect the troubleshooting examples from our first calls. A recruiter will review the reports; the customer-writing exercise and conversation about the opportunity stay. We will compare the complete workload before expanding.

That is specific enough to test and to stop. For the graduate role, make the equivalent proposal about CV-review effort. For the scientist, check whether a better brief is sufficient.

A CV-only rollout is a complete choice when it solves the problem. An interview-only change to the hiring process can be enough when application review already works. Combined screening is worthwhile when the two stages complement one another. The product’s feature list does not need to become the candidate’s to-do list.