Setting Up Skills-Based Routing

Skills-based routing is a powerful automation feature in ForceHQ that dramatically reduces the time recruiters spend manually reviewing initial applications and assigning technical tests. This guide explains how to set it up.

What is Skills-Based Routing?

Instead of a linear process where every candidate for a "Software Engineer" role gets the exact same generic test, skills-based routing uses initial data (like a resume parse or a brief preliminary AI screen) to route the candidate to an assessment specifically tailored to their strongest skills.

For example, if Candidate A has extensive Python experience and Candidate B is a Node.js expert, routing ensures they are each tested deeply on their respective strengths, rather than a generic logic test.

Step-by-Step Setup

Step 1: Navigate to the Workflow Builder

Go to Workflows > Automation Builders and click Create New Route.

Step 2: Define the Trigger Event

Every route needs a trigger. This is the event that initiates the logic evaluation. Common triggers include:

• Candidate Applied (Triggers immediately upon application submission).
• Resume Parsed (Triggers after the AI finishes extracting skills from the CV).
• Screening Completed (Triggers after a preliminary AI voice interview).

Step 3: Create the Routing Conditions

This is where you build the logic using a simple IF/THEN interface.

Let's build a route for a Full Stack Developer role:

• Condition 1: IF Candidate Skills CONTAINS "React" AND Candidate Skills DOES NOT CONTAIN "Angular" THEN assign "React Frontend Architecture Assessment".
• Condition 2: IF Candidate Skills CONTAINS "Angular" THEN assign "Angular Framework Assessment".
• Condition 3 (Fallback): IF neither condition is met, THEN assign "General Web Fundamentals Assessment".

Step 4: Configure the Actions

Once a condition is met, what happens next? The most common action is Send Assessment Invitation. You can configure the email template that goes out to the candidate directly within the workflow builder.

You can also add secondary actions, such as Update ATS Status to move the candidate to an "Assessment Sent" stage in your integrated tracking system.

Testing Your Workflows

Routing logic can get complex quickly. Use the Test Workflow feature before activating it. You can input mock candidate data (e.g., type in "Java, Spring Boot") and the system will output exactly which path the candidate would take, ensuring your logic is sound and no candidates fall through the cracks.

By implementing intelligent routing, you provide a more personalized candidate experience while ensuring your engineering team only reviews highly relevant, deep technical data.