By default every skill you add is connected with AND. Click the AND pill between two skills to switch it to OR. Click again to switch back.
AND
The candidate must satisfy each required skill in the list. Skills that are not required are still just ranking signals.
OR
At least one of the skills in the list must be present. When you switch the main skill list to OR, Candidately ticks required on every skill in it and shows a note: "All skills in the OR group have been set to required to maintain consistent group behavior". That is expected: an OR list only makes sense as "must have one of these".
After the switch, every connector reads OR and every skill is required:
If you don't want a strict filter at all, leave the list on AND and keep the skills optional. The AI will still prefer candidates who have any of them.
Groups and sub-groups
Add Group creates a bracket. Inside it you get your own skill list, your own AND/OR connector, and Add Sub-Group for another level. Remove a group with the x on its header.
Example: a Java or Kotlin developer who also knows Spring.
Another example: cloud experience on any platform, plus Terraform.
Group (OR): AWS, Azure, GCP
AND
Terraform (required)
Tips
One level of grouping is enough for almost every search. If you find yourself building three levels, put the nuance in the Ideal Candidate Brief instead.
Don't rebuild Boolean strings. Titles, industries and "something like this" belong in the brief. Groups are for real alternatives: this language OR that language.
Click Apply Changes at the bottom of the panel after editing groups.



