Internal Mobility Matching Agent
An internal mobility matching agent is an AI agent for talent acquisition that matches open roles to current employees' opt-in skills and career-interest profiles, tells employees about roles worth a look, and surfaces internal candidates to recruiters before external sourcing starts.
How does the internal mobility matching agent work?
What flows in, what the agent does with it, where a person decides, and what comes out.
Reads from
Opt-in skill and career-interest profiles · Open roles and success profiles · Job architecture · Internal mobility and visibility policy
AI agent · runs when an internal role opens or a profile is updated
Internal Mobility Matching Agent
A person sets the rules and can override
HR sets the mobility rules; the employee chooses to apply
Produces
Role suggestions to the employee · Opted-in internal candidates for the recruiter · Skills behind each match · Visibility record (manager blind until apply)
What does the internal mobility matching agent do?
Matches open roles to current employees' opt-in skills and career-interest profiles, tells employees about roles worth a look, and surfaces internal candidates to recruiters before external sourcing starts.
What does it produce?
Match suggestions to the employee and an internal-candidate list to the recruiter, with the skills behind each match
Who decides?
The employee decides whether to apply and the hiring manager decides whom to hire; the agent suggests, and current managers see nothing until the employee chooses to apply.
What systems does the internal mobility matching agent connect to?
Examples of the kind of systems this agent would read from or write to, so you can picture it in your own stack. The actual set is whatever you run.
-
HRIS / talent
job architecture and profiles
-
Talent marketplace
opt-in interests and matching
-
ATS
internal reqs and applications
-
Chat
role nudges to employees
What data does it need?
- opt-in employee skill and interest profiles
- open roles and success profiles
- job architecture
- internal-mobility policy
How would you measure it?
opt-in rate, monthly, by function; internal-fill rate and time-to-fill for internal hires, quarterly; regretted attrition among opted-in employees, annually
What does a first proof look like?
Pilot in one function with employees who opt in and one quarter's internal reqs. In a sandbox the agent suggests roles to each employee and shows recruiters the opted-in internal list before external sourcing.
You'd call it working when
Employees say the suggestions are relevant, some apply who wouldn't have seen the role, and no manager reports hearing about an application before the employee told them.
What usually goes wrong?
- If a current manager can see who is 'looking', nobody opts in; the visibility rule is the product
- Profiles go stale within months; prompt employees to update, don't infer silently
- Recruiters skip internal candidates when the external pipeline is faster; policy must give internals a head start
What are the guardrails?
- Profiles opt-in, visible and editable by the employee; nothing inferred without their sight
- Current managers see nothing until the employee applies
- Recruiter list contains only employees who opted in to be surfaced; suggestions to employees are invitations, not shortlists
- Profile data never feeds performance, pay or redundancy processes
- GDPR notice and DPIA; works-council consultation where required
What leaves your boundary is set per build; the inputs above are the ceiling, and where the model runs, what it retains, and the DPA are agreed with your security team before anything is connected.
Our read
Clearly valuable with real deployments behind it. Needs care on data and adoption.
Parts of this may exist in your current tools. The case for building is usually the join across systems, or your rules and language, that a suite feature cannot carry.
individual profiles; must stay opt-in and out of current-manager view to avoid chilling applications
Where it sits in the order
Opt-in profile data is the constraint; sensitivity is manageable if the visibility rule is set from day one
Is an Internal Mobility Matching Agent worth building for your function?
That depends on your numbers, your data, and what else is on the map for you. The strategy month works that out.
Thirty minutes. Bring the number this would move.