Every skill in the filter panel is in one of three states. Getting this right is the single biggest lever on result quality. Each skill card has two checkboxes: the first (shield icon) is Required, the second (crossed circle) is Exclude.
Required (first checkbox on)
A hard filter. Only candidates whose profile contains that skill, or one of its direct synonyms, pass.
"React" required still matches "React.js", "ReactJS", "React developer".
"Front end development" required does not match a candidate who lists React and Angular but never wrote "front end development".
Use required for precise things: Java, SAP FI, Salesforce, CPA, a specific language. Keep it to your top 1–3 real must-haves. In the example above, Java is required and Spring is optional.
Optional (both checkboxes off)
A ranking signal. The AI weighs it, along with the context, but nobody is removed for lacking it. It also lets the AI infer: several front-end technologies on a profile means front-end developer, even without the phrase.
Use optional for broad categories, nice-to-haves, and anything where wording on the resume varies a lot.
Excluded (second checkbox on)
A hard filter in reverse: candidates with this skill are removed. Synonyms are expanded too. Use it sparingly: "exclude PHP" also removes strong full-stack people who once touched PHP.
Experience level per skill
The Select experience dropdown on a skill card (Low 0–3 / Mid 4–6 / High 7+ years) adds depth: "Java, High" prefers people with 7+ years in Java specifically, not just 7+ years in total.
Short version
Required on = strict, for specific skills
Required off = soft signal, for broad concepts
Exclude = strict removal, use rarely
Too few results? The first thing to check is how many skills are required.
Remember to click Apply Changes at the bottom of the panel after editing.