Key terms
Workerbee’s vocabulary — the concepts you’ll see across the Console, the API, and every AI connector.
| Graph | A database of occupations, skills, and education connected as nodes and relationships, so the platform can reason across related concepts instead of doing flat keyword lookups. |
| Canonical Occupation / Skill | A normalized, deduplicated representation of a job title or skill, so "Software Engineer" and "SWE," or "JS" and "JavaScript," are recognized as the same thing. |
| Structuring | The step where an unstructured resume or job description is parsed into consistent fields (skills, titles, education) — not chunked-and-embedded, but converted into facts on the Graph. |
| Success Profile | A standardized definition of what "good" looks like for a role — required and nice-to-have skills, experience, and other criteria — so every candidate is evaluated against the same bar. |
| Worker Passport | A person's structured profile record: parsed resume data, canonical skills, work history, and other attributes, normalized so it can be matched against roles. |
| Talent Intelligence | The layer that compares a Worker Passport against a Success Profile (or runs broader workforce queries — mobility, succession, skill gaps) and returns ranked, evidence-backed results. |
| Job Match / Ranking | The output of comparing candidates against a Success Profile: a rank, a score, and a human-readable rationale — never a black-box number. |
| Decision Audit | A retrievable record of what was asked, what was answered, and what evidence was used for a given ranking or query — built for compliance, not added after the fact. |
| Candidate Anonymization | Network/external candidate identities are withheld (shown as initials) until the candidate consents to being identified. A product guarantee, not a demo limitation. |
| k-anonymity suppression | Small result sets are suppressed so a query can't be used to single out one individual by elimination. |
| MCP (Model Context Protocol) | An open protocol that lets AI assistants and agents call Workerbee's capabilities as typed tools, instead of a one-off custom integration per client. |
| Connector | The authorized integration point that lets an AI client (Claude, ChatGPT, Gemini, an MCP-compatible IDE) access Workerbee on a user's behalf, set up through an OAuth-style consent flow. |
| Integration (ATS / HRIS / LMS) | A live connection to an external system (via Kombo) that keeps a customer's Graph data in sync automatically, as opposed to a one-time file upload. |
Was this page helpful?