skills/resplendent-resume-builder/references/job-application.md

# Job application

Use this reference for job-fit analysis, ATS-oriented tailoring, career changes, cover letters, application-form answers, cold outreach, and resume version management. It consolidates `resume-ats-optimizer`, `job-description-analyzer`, `resume-tailor`, `career-changer-translator`, `cover-letter-generator`, `application-form-filler`, `cold-email-writer`, and `resume-version-manager`.

Also read [professional editorial method](editorial-method.md). When examples or source-backed patterns would help, read [example patterns and sources](example-patterns.md).

## Analyze the role before rewriting

Extract the job title, seniority, core responsibilities, required qualifications, preferred qualifications, domain context, work arrangement, location/authorization constraints, outcomes, tools, and signals about culture or scope. Classify each item as must-have, strong preference, or contextual language; do not treat every repeated noun as a requirement.

Map each requirement to supplied candidate evidence: direct evidence, adjacent/transferable evidence, unsupported gap, or unknown. Surface material dealbreakers candidly. When the user asks whether to apply, give a reasoned recommendation with strengths, gaps, and questions—not a false prediction of hiring odds.

Use **unknown** when the supplied record does not establish whether the candidate has the qualification. Use **unsupported** when the candidate has said they do not have it or the available evidence clearly does not support the claim. Do not convert adjacent evidence into an exact skill: analytics does not establish SQL, stakeholder management does not automatically establish people leadership, and exposure does not establish proficiency.

### Transparent fit heuristic

If a score would help, call it a **candidate-evidence coverage estimate**, never an ATS score. State the scoring basis, for example: must-haves 60%, high-value responsibilities 25%, preferred qualifications 15%; calculate only from visible evidence; and name unknown information. A low score can still support applying when the gap is learnable or requirements are ambiguous, but do not advise misrepresentation.

## Tailor without distortion

Prioritize the candidate's strongest relevant evidence in the summary, skills, section order, and recent bullets. Mirror job-description terminology only where it truthfully describes the candidate's work. Translate jargon across domains by preserving the underlying action, stakeholder, constraint, and outcome.

Do not add unsupported tools, credentials, keywords, or direct-industry claims. Mark optional additions as questions, such as “Have you used SQL in this analysis workflow?” Replace unsupported exact keywords with truthful adjacent evidence where possible. Preserve the master resume as a fuller evidence record; make targeted copies that remain internally consistent.

Use an unambiguous version convention such as `Lastname_TargetRole_Company_YYYY-MM-DD` and retain a small changelog: target, source job link/identifier if supplied, changes made, pending facts, and submission status only if the user reports it.

### Requirement-to-evidence coverage gate

For every targeted resume or application audit, build a compact working ledger before revising and recheck it against the final copy. Track:

| Requirement | Priority | Employer term or useful variant | Candidate evidence | Best placement | Final status |
| --- | --- | --- | --- | --- | --- |
| The stated qualification or capability | must-have, strong preference, or context | exact truthful wording; include a spelled-out term and acronym together once when that improves recognition | direct, transferable, unknown, or unsupported | Summary, Skills, Experience, Education/Certifications, application field, or omit | covered, confirm, gap, or a compound status such as `confirm — possible knockout` |

Treat location, work authorization, required credentials or licenses, education, schedule, and explicit screening questions as eligibility or possible knockout items rather than ordinary keywords. Never imply that wording alone resolves one of these requirements.

Apply the ledger proportionally:

- Prioritize must-haves and high-value responsibilities; do not inventory every repeated noun or cultural phrase.
- For a must-have or high-value responsibility, use the employer's exact term at least once when it truthfully and naturally names supported experience. Add the common expanded form and acronym together once when useful, such as `Oracle Cloud Infrastructure (OCI)`; do not manufacture awkward variants.
- Put technical and domain capabilities in Skills only when supported and useful for scanning. Put ownership, application, scale, and results in Experience or Projects; use Summary only for high-value positioning. Do not repeat a term across sections solely to increase density.
- Convert supported-but-absent terms into natural, evidence-bearing language. For transferable-but-differently-named evidence, use the target term only when the equivalence is defensible; otherwise explain the bridge without claiming the exact skill.
- Keep unknown items as focused confirmation questions and unsupported items as explicit gaps. Surface any uncovered must-have or possible knockout before finalizing.
- For a generated document, confirm that high-priority supported terms survive in the extracted final text and remain connected to the correct role, project, credential, or section.

The ledger is an internal control by default. Show a concise coverage summary when the user asks for an audit or when an unresolved must-have, unknown, unsupported gap, or possible knockout could change the application decision.

## Career-change translation

Define the target role's capabilities, then map past work to transferable evidence: customer discovery, operations, analysis, stakeholder communication, delivery, process improvement, budgeting, leadership, or domain learning. Lead with the bridge rather than apologizing for the old title. Use a summary, selected projects, coursework, certifications, volunteer work, or portfolio only if real.

Call out genuine gaps and suggest ethical ways to close them—portfolio work, coursework, informational interviews, or smaller scope roles—without pretending they are complete. Keep chronology factual.

## Cover letters and application responses

Write a cover letter only when it has a job-specific point: a credible connection between demonstrated evidence and a material need in the role. Default to one page and roughly 250–400 words. This is a ceiling and useful range, not a quota; a shorter letter is preferable to filler.

Use this compact contract:

1. Opening: role plus a specific, supportable reason for interest.
2. Evidence: one or two relevant achievements with context and consequence.
3. Added value: include at least one supported dimension the resume does not make obvious—problem diagnosis, decision criteria, method, constraint, tradeoff, stakeholder dynamic, motivation, or lesson.
4. Connection: explain how that evidence prepares the candidate for a material part of the stated work.
5. Close: one short, direct professional next step.

The resume establishes what happened. The letter should reveal how the candidate approached it, why the example matters here, or what the resume lacks room to explain. Reusing a resume achievement is acceptable only when the letter adds one of those dimensions. Do not repeat a headline metric merely for emphasis.

Before delivery, label each sentence internally using the editorial-method usefulness test. A strong letter is made of supported evidence, useful interpretation, necessary navigation, and a short close. Revise or remove resume repetition, generic filler, and unsupported statements. Avoid generic enthusiasm, company praise without evidence, and claims of research not actually performed. If company information is absent, use the job description or ask for a source.

For application forms, answer the exact prompt, honor word/character limits, and distinguish factual background, motivation, work samples, technical capability, behavioral examples, and opinion questions. Draft concise responses first; offer a longer version only if the field allows it. For behavioral prompts, use a supplied STAR story or ask for the missing situation, task, action, and result.

For cold outreach, get the recipient, purpose, relationship/context, and one real reason to contact them. Write a short, respectful message with a specific ask. Do not imply a referral, shared connection, prior conversation, or company knowledge that the user has not supplied.

## ATS-oriented review

Run the requirement-to-evidence coverage gate against the revised material. Check that job-relevant supported terms appear in natural contexts, titles and dates are clear, headings are conventional, and the document can be parsed in reading order. Flag keyword gaps as one of: supported but absent, transferable but differently named, unsupported, or unknown. Never use keyword density as the goal.

## Deliverable shapes

- **Job analysis:** requirements map, evidence coverage estimate and basis, strengths, gaps, red flags, and recommended next action.
- **Tailored resume:** change list, revised copy, concise coverage summary when required by the gate, facts to confirm, and version label.
- **Cover letter/application pack:** final draft(s), the evidence each relies on, character count where relevant, and unanswered questions.
- **Career-change plan:** transferable-evidence map, positioning statement, honest gaps, and materials to build next.