Skip to main content
The recruiter ontology is the source of truth for search intelligence. Boolean strings, LLM suggestions, job descriptions, and recruiter feedback are evidence or proposals until they are reviewed and published into a market pack.

Core Objects

  • concepts: canonical recruiting concepts such as titles, credentials, skills, employer archetypes, and hard exclusions.
  • terms: display text and normalized keyword forms attached to concepts.
  • markets: parent and child recruiting markets.
  • market_pack_versions: immutable published market-pack releases.
  • market_terms: concept terms with market-specific treatments such as hard_match, soft_match, or hard_exclusion.
  • evidence: source-backed observations for terms and relationships.
  • ontology_proposals: tenant or market-scoped suggestions awaiting review.
  • approval_decisions: immutable reviewer decisions.
  • candidate_feature_snapshots: evidence-backed feature matches captured during scan scoring.
  • ontology_feedback_events: recruiter verdicts and reason codes tied back to a scan and candidate.
  • ontology_term_performance: aggregate accept/reject/maybe counters by market, pack version, term, and treatment.
  • ontology_evaluation_sets and ontology_evaluation_labels: offline regression sets for market-pack quality.

Normalization

Matching is case-insensitive by default but punctuation is preserved:
Use the helper endpoint to preview normalization:

Seed Launch Markets

The launch seed creates six publishable market packs:
  • capital-markets-engineering-us
  • software-engineering-us
  • data-ai-us
  • healthcare-nursing-us
  • sales-business-development-us
  • wealth-management-us
Run migrations first, then seed:
Or seed through the internal API as a RevCenter team user:
The wealth-only seed endpoint is still available:
Fetch the latest published pack snapshot:
Compile criteria into a deterministic search-plan preview:
The response separates hard requirements, soft preferences, positive signals, negative signals, hard exclusions, provider warnings, and Google X-ray query families.

Runtime Behavior

Candidate intake now attempts to infer a market pack from the extracted criteria. For wealth-management searches, the API returns an ontologyPlan preview when wealth-management-us is published. When a candidate scan starts, the backend stores that plan in search_plan_versions and stores the compiled query families in serper_queries. The scan pipeline uses those stored queries before falling back to the older CriteriaV2 dork builder. Search chat refinements also attempt ontology compilation. If the refinement is marked rescore_only, no new Serper queries are stored. During scoring, the backend now snapshots evidence-backed ontology features into candidate_feature_snapshots. These snapshots include matched terms, failed hard requirements, hard exclusions, and evidence excerpts from the profile data. When a recruiter marks a candidate as accept, reject, or maybe, the verdict is written into ontology_feedback_events and rolled up into ontology_term_performance. This creates the first measurable learning loop without allowing feedback to silently rewrite a published market pack. Inspect term performance for a market:
Inspect feature snapshots for a scan:
Inspect recent feedback events:

Evaluation Sets

Evaluation sets hold labeled known-good, known-bad, and ambiguous candidates for market-pack regression testing. Create a set:
Add a label:
Summarize a set, optionally against a scan ranking:
The summary reports label counts plus ranking metrics such as precisionAt10, precisionAt25, ndcgAt20, and meanReciprocalRank when a scan is supplied.

Manual Market Editing

Create a concept:
Create a market:
Create a draft pack version:
Attach reviewed terms to the pack:

Phase Coverage

The current implementation covers the backend foundation across the planned phases:
LLMs may propose mappings, but this ontology layer prevents raw model output from silently becoming canonical recruiting knowledge. Remaining production work is mostly breadth and UI: expert-review screens, additional market packs, full hybrid retrieval infrastructure, and larger regression datasets.

Deployment Smoke Test

After deployment:
Then verify:
Run a wealth-advisor scan, mark one candidate accepted or rejected, then confirm rows exist in candidate_feature_snapshots, ontology_feedback_events, and ontology_term_performance.