AI/myAi
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity

Fix CV keyword extraction — derive from candidate CV, not matched job #55

Merged
claude merged 1 commits from feature/fix-keyword-extraction-prompt into main 2026-06-09 13:40:10 +00:00
Conversation 1 Commits 1 Files Changed 2
+231
claude commented 2026-06-09 13:38:22 +00:00
Member
Copy Link
Copy Source

Problem

Keywords extracted during CV-to-job matching were being influenced by the job description, returning terms like DevOps Engineer, C#, AWS for a Software Architect CV matched against a DevOps posting. These keywords flow into cv-search-job and drive job-board searches — so misaligned keywords produce irrelevant results.

Fix

Updated the keywords instruction in ai.cv-match.system-prompt (en + ro) to explicitly tell the LLM to derive keywords from the CV only — the candidate's seniority, primary role title, and core technologies they genuinely emphasize — regardless of the job being matched.

Change

Single migration FixKeywordExtractionPrompt in cv-matcher-data. No code changes.

Test plan

  • Run a CV match for a senior/architect profile against a mismatched job (e.g. DevOps posting)
  • Confirm keywords in the response reflect the candidate's actual role and tech stack, not the job's
  • Verify cv-search-job receives meaningful search terms for job board scraping
## Problem Keywords extracted during CV-to-job matching were being influenced by the job description, returning terms like `DevOps Engineer, C#, AWS` for a Software Architect CV matched against a DevOps posting. These keywords flow into `cv-search-job` and drive job-board searches — so misaligned keywords produce irrelevant results. ## Fix Updated the `keywords` instruction in `ai.cv-match.system-prompt` (en + ro) to explicitly tell the LLM to derive keywords from the **CV only** — the candidate's seniority, primary role title, and core technologies they genuinely emphasize — regardless of the job being matched. ## Change Single migration `FixKeywordExtractionPrompt` in `cv-matcher-data`. No code changes. ## Test plan - [ ] Run a CV match for a senior/architect profile against a mismatched job (e.g. DevOps posting) - [ ] Confirm `keywords` in the response reflect the candidate's actual role and tech stack, not the job's - [ ] Verify cv-search-job receives meaningful search terms for job board scraping
claude added 1 commit 2026-06-09 13:38:22 +00:00
Fix CV keyword extraction to reflect candidate identity, not matched job b52ef8ddff 
The AI prompt now instructs the LLM to derive keywords entirely from the
candidate's CV (seniority level, primary role title, core technologies they
emphasize) rather than from the job description being matched. This ensures
the job-board search keywords used by cv-search-job represent who the
candidate actually is, not a mirror of the job they happened to match against.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
gelu approved these changes 2026-06-09 13:39:12 +00:00
claude merged commit a3567ce8e9 into main 2026-06-09 13:40:10 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
gelu
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude gelu
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: AI/myAi#55
Delete Branch "feature/fix-keyword-extraction-prompt"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?