AI with Michal

People graph in recruiting

A people graph in recruiting is a data model that represents people as nodes and their attributes and relationships, such as who they worked with, where they studied, their skills, and their employers, as connected edges, so a recruiter can query relationships and paths between people rather than just matching isolated records.

Michal Juhas · Last reviewed June 29, 2026

What is a people graph in recruiting?

A people graph in recruiting stores information about people as a network instead of a flat list. Each person is a node, and the things that connect them, shared employers, schools, projects, skills, managers, and referrals, are edges. Where a spreadsheet or talent CRM treats each candidate as an isolated record, the graph treats the connections between candidates as data in their own right.

That difference matters because the most valuable sourcing questions are about relationships. Who do we already know who could introduce us to this person. Who worked with this hiring manager before. Who else came from the team that just got acquired. These are multi-hop questions, and a graph is built to traverse them quickly, while a row-and-column database has to grind through expensive joins to answer the same thing.

People graphs usually live underneath a product rather than in a recruiter's hands directly. They power the warm-path, similar-people, and team-mapping features of many talent intelligence platforms and sourcing tools. Their power depends entirely on data quality: a graph built on stale edges and bad entity resolution produces confident, wrong connections, so accuracy and refresh discipline matter as much as the structure itself.

Illustration: a people graph showing person nodes connected by labeled relationship edges such as worked-with, studied-with, shared-employer, and reports-to, with a highlighted warm-introduction path traced between a recruiter's network and a target candidate, sitting beneath a talent intelligence panel

In practice

  • A recruiter searching for a hard-to-reach executive uses a tool's people-graph feature to find a warm path: a current employee worked with the target two companies ago. The intro request goes through that connection instead of a cold message, and the response rate is far higher.
  • A sourcing team maps a competitor's engineering org through collaboration and reporting edges, identifying not just individuals but the clusters of people who tend to move together after a reorganization.
  • A platform uses AI to keep the graph fresh, extracting new roles and relationships from updated profiles and resolving duplicate records. A recruiter still treats a suggested connection as a lead to confirm, because a stale edge can imply a relationship that no longer holds.

Quick read, then how hiring teams use it

This is for sourcers, recruiters, and TA leaders evaluating relationship-based tooling, who want to know what a people graph adds and where it can mislead. Skim the first section for the idea. Use the second when you are weighing graph features in a platform.

Plain-language summary

  • What it means for you: A people graph stores candidates as connected nodes, capturing who worked with whom and shared employers, schools, and skills, so you can find warm paths and hidden connections a flat list would miss.
  • How you would use it: Through a tool's features, find an introduction path to a target, surface people similar by background, or map a team, rather than building a graph yourself.
  • How to get started: When trialling a sourcing or intelligence tool, test its warm-path and similar-people features on roles you know well, and check whether the connections are accurate and current.
  • When it is a good time: When relationships drive your hiring, such as executive search, referrals, or mapping teams that move together, more than keyword matching does.

When you are running live reqs and tools

  • What it means for you: The graph's value is the connections, and its risk is bad connections. Treat suggested relationships as leads to verify, not facts, because entity-resolution errors and stale edges are common.
  • When it is a good time: When the tool keeps its graph fresh and you can pair it with a vector database for semantic matching and your talent CRM as the system of record.
  • How to use it: Use the graph for proximity and intro paths, semantic search for relevance, and the CRM for status and outreach. Confirm a warm path with the connector before relying on it.
  • How to get started: Log which graph-sourced introductions actually convert, so you learn where relationship data earns its place versus where plain search is enough.
  • What to watch for: Stale edges, wrong record merges, GDPR obligations on storing rich relationship data, and inferred connections that feel intrusive if surfaced bluntly.

Where we talk about this

On AI with Michal live sessions, people graphs come up when participants compare relationship-based sourcing with semantic search and discuss where connection data adds real signal, such as referrals and executive search. The membership community shares experience with graph-backed tools and where their suggested connections hold up or break down.

People graph vs CRM vs vector search

LayerAnswersBest for
People graphHow is this person connected to othersWarm intros, team mapping, referrals
Talent CRMWhat do we know and where are they in the processSystem of record, outreach, status
Vector searchWho is semantically similar to this personRelevance matching across different wording

Around the web (opinions and rabbit holes)

Third-party creators move fast. Treat these as starting points, not endorsements.

YouTube

  • Searches for "talent graph sourcing" and "relationship based recruiting" surface explainers on graph-backed tools and warm-introduction sourcing.

Reddit

  • r/recruiting has threads on referral and relationship sourcing and on the tools that claim to surface connections.
  • r/datascience discusses graph databases and entity resolution, the technical backbone of any people graph.

Quora

  • Searches for "what is a people graph" and "graph database for recruiting" collect explanations of the model and how it differs from a relational database.

Related on this site

Frequently asked questions

What is a people graph in recruiting?
A people graph in recruiting is a way of storing information about people as a network rather than a flat list. Each person is a node, and the things that connect them, shared employers, schools, projects, skills, managers, or referrals, are edges between nodes. This structure lets a recruiter ask relationship questions a row-and-column database struggles with, such as who in our network has worked with this hiring manager, or who is two connections away from a target candidate. People graphs sit underneath many talent intelligence platforms and sourcing tools, powering features like warm-intro paths, similar-people suggestions, and richer matching. The value is in the connections, not just the individual records.
How is a people graph different from a database or CRM?
A traditional database or talent CRM stores each person as a record with fields, and relationships are awkward to express and slow to query at depth. A people graph makes relationships first-class: connections are stored directly as edges, so traversing them (find everyone who worked with X, then everyone they worked with) is fast and natural. A CRM answers what do we know about this person; a graph answers how is this person connected to everyone else. They are complementary, not rivals. Many teams keep the CRM as the system of record for outreach and status, and use a graph layer for relationship discovery. The graph adds the network dimension a flat schema cannot represent efficiently.
What can a people graph do that a flat list can't?
The unlock is relationship and proximity queries. With a people graph you can find warm-introduction paths (who do we know who could introduce us to this candidate), surface similar people based on shared background rather than just matching keywords, map a target team and see reporting and collaboration links, and spot internal mobility candidates connected to a hiring manager. You can also discover hidden talent pools, for example everyone who worked at a company before an acquisition, by traversing employer edges over time. A flat list can store these facts but cannot efficiently answer multi-hop questions across them. The graph turns a pile of profiles into a navigable network, which is especially powerful for executive search, referrals, and talent mapping.
How does a people graph relate to AI and semantic search?
They solve different parts of the matching problem and increasingly work together. A vector database captures semantic similarity, finding people whose experience means the same thing even when the words differ. A people graph captures explicit relationships, who is connected to whom and how. Modern talent platforms combine the two: semantic search narrows to relevant people, and the graph adds context like shared connections, warm paths, or team structure. AI also helps build and maintain the graph, by extracting entities and relationships from unstructured profiles and resolving when two records are the same person. The combination, semantic matching plus relationship graph plus AI extraction, is what lets a tool answer find me senior people similar to this hire who someone on my team can introduce me to.
What are the data quality and privacy challenges of people graphs?
Graphs amplify both good and bad data. Entity resolution is the core technical challenge: deciding when two profiles are the same person, or two company names the same employer, because a wrong merge or split corrupts every connection that flows through it. Edges also go stale as people change jobs, so a graph needs constant refreshing to stay trustworthy. On privacy, a people graph is a rich store of personal data and inferred relationships, which raises clear GDPR obligations: a lawful basis, transparency, retention limits, and the ability to honour erasure across connected records. Inferring relationships people did not declare can also feel intrusive. Keep the graph accurate, scoped to a legitimate recruiting purpose, and refreshed, and treat relationship inferences as signals to verify, not facts.
How do recruiting teams use people graphs in practice?
Most teams meet a people graph through a tool rather than building one, since maintaining graph infrastructure and entity resolution at scale is a serious engineering effort. They use the graph features inside a talent intelligence platform or sourcing tool to find warm intros, map target teams, and surface similar candidates, while keeping their talent CRM as the system of record. To use it well, treat graph suggestions as leads to confirm, not truth, because stale edges and bad merges are common. Log which graph-sourced paths actually converted, and keep a privacy baseline. In AI in recruiting sessions, teams explore where relationship data adds real signal, such as referrals and executive search, versus where simple search is enough.

Recruiting OS

Practical AI systems for modern recruiters.

Sourcing workflows, AI skills, live builds, and tactical guidance — designed to be implemented immediately in your stack.

Explore Recruiting OS

← Back to AI glossary in practice