docs(evaluation): reframe onboarding and matching guidance around function, not title (#330)

Title-lookalike matching collapses a multi-hat career into whichever single
job-title box sounds closest, then searches only inside that box. /setup
Section 9 now asks about the function before collecting search titles,
search-queries.md says to organize priority categories by function with title
variants under each, and 04-job-evaluation.md's Experience dimension matches on
the function and nature of work performed (framework_version 1.2.2 -> 1.2.3).
From discussion #327's field report and calibration example.
This commit is contained in:
197281t-ship-it
2026-08-16 20:04:42 +02:00
committed by GitHub
parent 762d3218ef
commit 5c423b4064
4 changed files with 17 additions and 5 deletions
@@ -1,5 +1,5 @@
---
framework_version: 1.2.2
framework_version: 1.2.3
---
# Job Evaluation Framework
@@ -65,7 +65,7 @@ How well do the required/preferred skills align with the candidate's capabilitie
**Weak match areas:** [SKILLS_YOU_LACK]
### 2. Experience Match (0-100)
Does work history align with what they're looking for?
Does work history align with what they're looking for? Match on the function and nature of the work performed, not the literal job title - a "Data Consultant" and a "Data Scientist" role can be functionally identical.
| Score | Meaning |
|-------|---------|