Job search
Greenhouse Talent Matching Opt-Out: Change the Setting for the Correct Application
Manage Greenhouse Talent Matching opt-out for the correct application and email, retain confirmation, and understand the limits of the setting.
To opt out of Greenhouse Talent Matching, use the employer-enabled control for the specific application, verify the email used for that role, and retain the confirmation. Selecting an option without completing verification is not the same as a saved preference. Check each eligible application separately. This setting concerns Talent Matching review; it does not submit or withdraw your application, delete all your records, or guarantee an interview.
LandOffer publishes this guide and offers job-search tools. Official Greenhouse documentation was reviewed on October 13, 2026, including the current candidate FAQ. The examples below are fictional; we did not request a security code, change a candidate's settings or submit an application. As you find recent tech roles on LandOffer.ai, keep review preferences with the correct employer, role and application email rather than treating them as a search-wide setting.

Check what the employer has enabled
Talent Matching is a Greenhouse recruiting feature that helps employers compare candidates with their job criteria. It is not a name for every automated step in an application. Read the employer's disclosure and identify the feature before deciding which setting you want to change.
The Talent Matching setup guide describes employer configuration by office, department and job, along with optional candidate opt-out controls. This means a control available for one role may not appear for another. It does not follow that every employer using Greenhouse has activated the same configuration.
The Talent Matching FAQ says opted-out applications are flagged for manual review and are not evaluated by Talent Matching. It also says Talent Matching does not automatically advance or reject candidates. Keep that feature-specific description separate from other application questions, employer screening procedures or hiring decisions.
Identify the application before changing a preference
Start with the employer's actual job page and your application record. Note the role title, job ID if supplied, page URL and email used or intended for the application. If the same company has several similar roles, compare the identifier rather than relying on the company name alone.
An email visible in a reusable profile may not be the email associated with a particular application. Access to an inbox does not mean its address matches this application. Check your retained application details before requesting a code, especially if you use different addresses for separate searches.
Keep the record simple. A useful entry identifies the role and email, the review preference you want, the date you checked the control, and the evidence of completion. Those are recordkeeping choices; they are not additional fields that Greenhouse necessarily asks you to fill in.
If you have not yet submitted, make sure the email you plan to verify is the one you will use for the role. If you already applied, compare against the submitted record. Changing the review preference does not establish that an incorrect submitted application address was repaired. Resolve the address issue through the employer's accepted process rather than assuming a new preference request will rewrite it.
Follow the current candidate flow to completion
The MyGreenhouse candidate FAQ gives this process when the employer enables it:
- Open the AI policy at the bottom of the application and choose Learn more.
- Select Change your match score settings, then Opt out.
- Verify the email used, or to be used, for that role with the one-time code.
- Enter the code to finalize the request; keep the resulting confirmation email.
Complete the process for each eligible application. Use the role’s own flow rather than a link copied from another job.
Use the verification request you initiated for that role and email. Keep the code private and enter it in the corresponding flow. You do not need to place the code in a job-search spreadsheet, send it to a recruiter or include it in a screenshot shared for help. Record the completed preference evidence and its date. Leave the verification code out of that record.
A worked review across three applications
Leah Cole is a fictional candidate with three separate application records. Two are at fictional HavenStack: backend role HS-204 uses leah.jobs@example.com, while data role HS-209 uses leah@example.com. A third, MS-314 at fictional MapleSignal, has no visible opt-out control in this constructed scenario. These are invented examples, not observed employer settings.
Leah begins from HS-204 and selects the opt-out option, but initially stops before entering the code. Her record should say Verification pending. The option she clicked expresses an intention; it does not establish a completed request.
Before continuing, she notices that her generic saved contact record contains leah@example.com. She compares it with the retained HS-204 application and uses leah.jobs@example.com for that request. She does not assume a confirmation associated with HS-209 will cover HS-204 simply because both jobs are at HavenStack.
In the constructed continuation, Leah completes verification for HS-204 and retains its confirmation on October 13. The completed record is:
| Application | Email associated with this role | Preference evidence and next action |
|---|---|---|
| HavenStack HS-204, Backend Engineer | leah.jobs@example.com | Opt-out confirmation retained for this role; keep with its application record |
| HavenStack HS-209, Data Engineer | leah@example.com | Not checked; inspect this role's own control before recording a choice |
| MapleSignal MS-314, Platform Engineer | leah.jobs@example.com | Control not visible in the example; ask about the available review process if needed |
Only HS-204 has a completed preference in this example. The leah@example.com address is valid for the separate HS-209 record; Leah does not replace it merely because HS-204 uses leah.jobs@example.com. HS-209 does not inherit the first role’s confirmation, and MS-314 is not marked Opted out without one. All addresses use the reserved example.com domain. We did not access those inboxes, request a code or create a real confirmation.
Leah also keeps the application-submission state in a separate field. A preference confirmation does not establish that a resume was attached, all required questions were answered or the job application itself was submitted. She checks those through the actual application process and its own evidence. For example, a retained submission confirmation from October 12 would document that earlier submission; it would not establish that an October 13 preference request finished. The two events need separate entries.
Retain confirmation without expanding its meaning
Keep the confirmation with the role record rather than in a general folder labelled Greenhouse settings. Record the date and enough context to distinguish the employer and job. If your evidence does not identify the intended application clearly, resolve that ambiguity before marking several applications complete.
A screenshot of a selected option is weaker than evidence that the request finished. In Leah's example, her first screenshot would show a choice in progress. Her later confirmation supports recording the HS-204 preference as completed. Neither proves that a hiring manager has read her resume or scheduled an interview.
If unsure, the candidate FAQ directs you to check for confirmation and repeat the opt-out process if it is missing. Retain the new evidence without submitting another application or inventing the outcome of the earlier request.
For a later opt-in, use the role’s corresponding flow and retain confirmation. Update the current preference while preserving the earlier event.
Handle a missing link or code carefully
The candidate FAQ says a missing Learn more control means the employer has not enabled that feature for the job. Its AI-review troubleshooting also recommends checking the entered address and spam or junk folders, requesting another security code through the displayed control, and contacting the employer if delivery still fails.
Keep login-code guidance separate from this request. MyGreenhouse account sign-in and Talent Matching preference verification are different flows. The FAQ’s ten-minute resend guidance appears in the login section. Its AI-review code section instead describes the displayed resend control; this guide does not apply the login interval to that separate request.
If a code is not arriving, record which role and email the request concerns and where the process stopped. Avoid switching to an unrelated address just because you can receive mail there. That can leave you with a different identity from the application you intended to manage.
For a custom company careers page, the Talent Matching FAQ describes support for displaying the disclosure and its Greenhouse-hosted preference link. Use the employer's actual page rather than assuming every application must have the same visual layout. If the relevant control is unavailable, ask the employer about its process; do not infer that every other AI feature is absent.
Ask a specific question when the control is unavailable
For the fictional MS-314 record, suppose the employer provides a recruiting contact for application questions. Leah can prepare a short inquiry identifying the role and the missing control. She does not need to send a security code, a full application packet or unrelated personal information to explain the problem.
Her complete unsent draft is:
Subject: MS-314 — Talent Matching review preference question
Dear MapleSignal recruiting team,
I am applying for Platform Engineer MS-314. I checked the application's AI disclosure but could not find a control for managing Talent Matching review preferences.
Does this role offer a way to request review without Talent Matching, and which process should I use if so? I intend to use leah.jobs@example.com for this application.
Thank you, Leah Cole
This is an unsent fictional inquiry about an available process. It does not claim the employer is required to offer a particular interface or that an alternative has been approved. Leah's record remains Control not visible; inquiry prepared. She changes it only when she has evidence of the employer's response or a completed preference request.
Understand the data and hiring limits of opt-out
The setup guide says that, when opt-out is enabled and the application is still active, existing AI-generated match results and reasoning for that application are deleted and it is flagged for manual review. This is narrower than deleting the application, its resume or every record the employer holds.
The Talent Matching Data Processing FAQ separately addresses already-rejected applications: an earlier AI result may remain under the customer's retention policy and applicable law. Do not assume a later preference change erases historical results or reopens a closed application. Questions about a particular retained record need a separate, specific discussion with the employer.
The documented manual-review label describes the employer workflow; this guide has not inspected any candidate’s internal label. Even a verified label would not prove that review had happened, set a response deadline, waive qualifications or promise a positive result. Keep your experience accurate and complete the required application steps. The preference also does not establish that all parsing, scheduling, assessment or other automated systems are disabled.

Leah ends with one role-specific preference confirmation, one role not yet checked and one question about an unavailable control. She has a concrete next action for each, without marking all three applications as reviewed by a person. As you review more recent LandOffer.ai roles, keep preference completion, application submission and employer review as separate events supported by their own evidence.


