How do we apply different client requirements when rediscovering candidates for different job orders?

You can apply different client requirements by scoring each job order against that specific client's stated criteria, rather than applying one generic search across your entire bench. Every job order carries its own requirements, so the matching process needs to treat each one independently even when candidates come from the same shared database.

This works by keeping the candidate bench centralized while scoping each search to the job order in front of you. A candidate's core profile, skills, resume, and placement history stay the same across every search, but the specific requirements you score against change with each client's job order, whether that means a different notice period, salary range, location radius, or required certification.

A practical constraint to include in this process is to check if a candidate is already under a placement fee restriction or exclusivity arrangement with another client before submitting them elsewhere. This step is crucial in staffing, where a candidate may be fully qualified for a role but still unavailable due to a prior client relationship.

Software like Skima AI supports this by using per-job matching criteria along with filters for experience level, location, notice period, and salary range. These are applied fresh to each job order instead of being reused from a previous search.

When a new job order comes in from any client, Skima AI scans the entire segmented bench and provides a ranked, scored list of matches. Each match includes reasons tied to the candidate's resume and placement history, tailored to that specific client's requirements rather than a generic profile match.