Filters

Use filters to capture simple role requirements

In the first step of calibration, set filters on clear, factual attributes like title, location, companies, and skills. Aim to narrow your target pool to <5,000 candidates, which you can then further refine with AI evaluation criteria.

Add filters

There are two ways to add filters:

1️⃣ Use AI to auto-generate filters from the JD

Select Job description on your role setup page to provide a JD. When you first open calibration afterward, Tezi will auto‑configure filters that capture the JD’s requirements.

If you add a JD after you’ve started calibrating, our system won’t auto‑update filters to prevent overwriting your changes.

🔗

Users with 3rd-party ATS integration: Tezi Support will connect Tezi to your existing ATS pipeline and JD, so you do not need to set up a JD in Tezi.

2️⃣ Manually add filters

Select “Add criteria” to manually add basic filters:

Notion image

You can leverage AI to autocomplete filters through natural language instructions:

Notion image

If you add a filter that spans multiple filter types, Max will automatically convert it to a “Custom criteria” and build a Boolean expression across the relevant filter types to try to capture your intent.

Notion image

Read any custom criteria carefully to ensure it captures your intent. Refine the criteria as needed, or make it an AI evaluation criterion instead if it’s better expressed in natural language.

Edit filters

Use the built-in drop-downs and toggles on filters to quickly edit them:

Notion image

For custom filters, use natural language to make edits:

Notion image

Delete filters using the right-side button:

Notion image

Understand impact on pool size

The number on the right side of each row indicates candidates in Tezi’s sourcing database (750M+ profiles globally) who meet all criteria above and including that row. The circle icon visually indicates the percent drop-off from the prior row, similar to a pie chart.

Notion image

When adding or editing filters, watch how the pool size changes.

  • If a filter removes more candidates than expected, check that it’s set up correctly. For example, for a job title filter, are there any common relevant job titles missing?
  • If a filter drastically shrinks the pool, consider whether it is essential or a nice-to-have that can be removed.

Pool size matters most for sourcing because it’s the number of candidates who meet your criteria that Tezi can contact. Pool size doesn’t directly affect inbound screening since that evaluates your actual applicant pool. Even for inbound screening, though, pool size can be a useful signal for how common each criterion is and which filters are likely to disqualify the most applicants.

👉

Pool size estimates in the filters section do not include the impact of AI reasoning criteria. You can see how AI criteria affect the candidate pool after you retrieve matching profiles.

Inbound & sourcing vs. Sourcing only filters

You can set filters to apply for both inbound screening and sourcing, or for sourcing only:

Notion image

When a criterion is nice-to-have but rare, use it in sourcing only to prioritize who Max contacts without overly constraining inbound screening. Target company or university lists are common Sourcing only filters.

Filters only have an effect if you set up the related feature. For example, if you’re only using inbound screening, Inbound & sourcing filters will apply in inbound screening, and Sourcing only filters will have no effect.

Did this answer your question?
😞
😐
🤩