mentor-patterns

mentor-patterns — what the records reveal

The Mentor watches sets, not single points. Six patterns are worth speaking about; everything else is noise.

Pattern A — Skill gap between profile and market

Skills that show up repeatedly in JD requirements but are absent from candidate_profile.yml > skills. If they also appear in high-scoring positions, the gap is costly (closing it would unlock submissions, not noise).

Detection

# 1. Pull the last 30 positions with their requirements + score
python3 /app/shared/skills/db_query.py positions --limit 30 \
    --status scored,checked --order-by created_at:desc

# 2. Tokenise requirements, compare with profile.skills.primary + .secondary
# 3. Count tokens NOT in profile that appear in N positions

Threshold

Speak only if a missing skill appears in ≥ 5 positions in the last 30 AND ≥ 1 of them has score ≥ 65 (within reach of the submission gate).

Example output

", I have counted. Docker appears in twelve of the last thirty positions in the records. Nine scored between 65 and 78 — within reach of the submission gate, never crossing it. One craft separates you from a third of the path before you."

Pattern B — Recurring exclusions

Counts of ESCLUSA: [TAG] markers in positions.notes over the last 30 days. If one tag dominates, the search direction is misaligned.

Detection

python3 /app/shared/skills/db_query.py positions --status excluded --limit 50 \
    --order-by last_checked:desc \
    | grep -oE 'ESCLUSA: \[(SENIORITY|STACK|GEO|LINGUA|LINK_MORTO|SCAM)\]' \
    | sort | uniq -c | sort -rn

Threshold

Speak only if one tag accounts for ≥ 40% of exclusions AND total exclusions ≥ 20 in the last 30 days.

Interpretation

Dominant tag	Likely cause	Suggested move
[SENIORITY]	Aiming too high (or too low) for the candidate's level	Adjust seniority_target in profile
[LINGUA]	A single language is closing entire markets	Add the language, or shrink geographic scope
[GEO]	work_mode / relocation out of step with the search	Re-discuss preferences with the user
[STACK]	Adjacent-stack noise reaching the team	Tighten Scout filters via Capitano
[LINK_MORTO] (>40%)	Source quality issue, not candidate issue	Forward to Capitano, this is a Scout problem