The career master and the pitfalls document are facts the user pastes or attaches per chat; every rule lives in the skills. build.sh zips each skill into claude-skills/dist/. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
83 lines
4.3 KiB
Markdown
83 lines
4.3 KiB
Markdown
# Fit check
|
|
|
|
Run before any drafting. Facts about the candidate come from the career master; constraints it does not record (location, travel, start date, work authorisation) are asked once.
|
|
|
|
## Gate 1: eligibility
|
|
|
|
A hard filter, not a score. Read the posting's eligibility or "who can apply" wording verbatim.
|
|
|
|
| Posting wording | Verdict |
|
|
|---|---|
|
|
| Citizenship or permanent residency required | FAIL: do not score or draft; quote the wording |
|
|
| Security clearance required | FAIL unless the candidate holds or can obtain it; clearance is usually tied to citizenship, so check the scheme |
|
|
| Names the candidate's permit class, or "we sponsor" | PASS, worth a line in the letter |
|
|
| Silent | PROCEED, marked unverified; check the employer's own careers or international-applicant page |
|
|
|
|
Silence is not permission: large employers often gate eligibility on their own site, not in the ad. A company-wide "international applicants welcome" may cover only a named list of programmes; confirm this posting is on it. Report a failure with the quoted source; the candidate may know something the documents do not.
|
|
|
|
## Gate 2: language
|
|
|
|
Read the languages the role itself requires, not the language the ad is written in. Compare each against the languages and levels in the career master.
|
|
|
|
| Requirement vs. declared languages | Verdict |
|
|
|---|---|
|
|
| Language not declared at all | FAIL: quote the requirement, do not draft |
|
|
| Declared, but the stated bar ("fluent", "native", "C1") plausibly exceeds the declared level | FLAG: score and draft, but quote both sides to the candidate |
|
|
| Declared at or above the bar, or no level stated | PASS |
|
|
|
|
Read levels as written; CEFR letters, "professional working proficiency" and "fluent" do not map exactly. When unsure, FLAG rather than PASS.
|
|
|
|
## Scores
|
|
|
|
Score the function and nature of the work, not the literal title: a "Data Consultant" and a "Data Scientist" posting can be the same job.
|
|
|
|
**Skills (0-100)**: 80-100 core requirements are primary skills; 60-79 most match, 1-2 learnable gaps; 40-59 partial, significant upskilling; 0-39 fundamental mismatch.
|
|
|
|
**Experience (0-100)**: 80-100 direct experience in the same domain and role type; 60-79 related, transferable skills clear; 40-59 adjacent, the case must be made; 0-39 unrelated.
|
|
|
|
**Career alignment (0-100)**: 80-100 advances the stated direction with a clear growth path; 60-79 a good role, partly aligned; 40-59 a job that does not build toward the goals; 0-39 a dead end or step back. Read the goals from the career master or ask. Also weigh whether the tasks energise or drain.
|
|
|
|
**Location and logistics (pass / flag / fail)**: commute, remote terms, relocation, travel, start date against the candidate's constraints.
|
|
|
|
**Overall** = 35% skills + 30% experience + 35% career alignment. Location is not weighted.
|
|
|
|
| Overall | Verdict |
|
|
|---|---|
|
|
| 75+ | Strong fit: apply, tailor everything |
|
|
| 60-74 | Good fit: apply, address gaps in the letter |
|
|
| 45-59 | Moderate fit: discuss with the candidate |
|
|
| 30-44 | Weak fit: skip unless there is a strategic reason |
|
|
| below 30 | Poor fit: skip |
|
|
|
|
**Experience below 50**: warn before drafting that the application would need extensive reframing, which raises the backtrack risk, and ask whether to proceed.
|
|
|
|
## Calling the contact
|
|
|
|
Suggest a call only when there are substantive questions: unclear or ambiguous requirements, unclear which competencies are essential, vague day-to-day tasks, or a named contact who invites questions. Never call just to be remembered.
|
|
|
|
Useful questions: the main challenges in the role; how time divides across the listed responsibilities; which competencies matter most; what success looks like after 6-12 months. The call gathers information; prepare a 30-second pitch only in case it is asked for. Reference the conversation in the letter ("After speaking with <name>, ...").
|
|
|
|
## Output
|
|
|
|
```
|
|
## Fit: <role> at <company>
|
|
Source host: employer / ATS / aggregator / unverified <host>
|
|
Eligibility: PASS / PROCEED (unverified) / FAIL (quote)
|
|
Language: PASS / FLAG (quote both) / FAIL (quote)
|
|
|
|
| Dimension | Score | Note |
|
|
|---|---|---|
|
|
| Skills | xx | |
|
|
| Experience | xx | |
|
|
| Career alignment | xx | |
|
|
| Location and logistics | pass/flag/fail | |
|
|
|
|
Overall: xx, <verdict>
|
|
Strengths for this role: ...
|
|
Gaps: ...
|
|
Call the contact? no / yes, with these questions: ...
|
|
Recommendation: apply / apply with caveats / skip
|
|
```
|
|
|
|
Then ask whether to proceed.
|