Most candidates either apply to everything or nothing. A good JD-fit analysis prompt extracts the real (vs. wishlist) requirements, surfaces hidden signals, and decides “apply / pivot / pass” with reasons.
Who this is for
Job seekers triaging openings, career switchers calibrating ambition, recruiters helping candidates self-select.
When not to use these prompts
Don’t use these to talk yourself out of stretch roles automatically — flag stretches honestly, don’t hide them.
Prompt anatomy / structure formula
Every JD-fit prompt should carry six elements:
- Role: candidate, hiring manager, recruiter — name the persona AI plays.
- Context: target role, company, level, your background.
- Goal: one deliverable — analysis, script, answer, plan.
- Constraints: word count, banned phrases, must-include facts.
- Tone: confident / curious / measured — 2-3 anchors.
- Examples: paste 1-2 of your past answers or sample tone.
Best for
- Apply / pass triage
- Where to upskill before applying
- Cover letter anchor extraction
- Recruiter call talking points
- Salary research baseline
12 copy-ready prompt templates
1. Real vs wishlist requirements
JD: {jd}. Identify: (a) MUST-haves (the role won't function without), (b) NICE-to-haves (wishlist), (c) Cargo-cult lines copied from elsewhere. For each: how I tell the difference. Output a 3-column table.Variables to swap: jd
2. Where I fit / don’t
JD: {jd}. My background: {me}. Score fit on 7 dimensions: domain, level, skills, scope, leadership, cultural, comp range. Each 1-5 + 1-line rationale. Total ≥ 25 = strong apply; 18-24 = stretch; < 18 = pass.Variables to swap: jd, me
3. Stretch role analysis
I'm a stretch for this role. Identify: (1) 2 things I genuinely lack, (2) 2 ways I compensate, (3) 1 area I should not pretend to have. Be honest — pretending gets exposed by interview 3.4. Hidden signals
Read between the lines of this JD: (1) Why does this role exist now (new team, replacement, expansion)? (2) What scope creep is hinted at? (3) What culture clues (verbs like "thrive in ambiguity", "self-starter")? Output a "between-the-lines" note.5. Title-vs-role mismatch
JD title says `{title}`. Read the responsibilities. Does this role actually match the title at typical companies? Flag: (a) under-leveled, (b) over-leveled, (c) unusual scope. Adjust expectations.Variables to swap: title
6. Apply / pivot / pass decision
Based on my fit analysis, decide: (a) APPLY now, (b) PIVOT (target role like this but at smaller / larger / different stage company), (c) PASS. One-paragraph rationale + the next 3 actions.7. Skills to learn before apply
For the genuine gaps in my fit, list: (a) skills I could learn in 4 weeks that close part of the gap, (b) projects I could ship as proof, (c) what NOT to invest in (won't move the needle). Be ROI-aware.8. JD red flags
Audit this JD for red flags: (1) "wears many hats" + no team, (2) "must be passionate" + no comp, (3) "fast-paced" + no leadership context, (4) overly long requirements list. Output flags + decision impact.9. Compensation signal
From JD: company size, location, role level, equity language. Estimate likely comp band. Use levels.fyi / public data. Footnote uncertainty. Don't invent specific offers.10. Cover-letter anchor extraction
From this JD, extract 3 phrases I should echo (not parrot) in my cover letter — the specific responsibility or value they prioritise. For each: a 1-sentence link to my background.11. Recruiter screen prep
Based on my fit analysis, prep recruiter-screen talking points: (a) elevator opener, (b) 1 example matching their top requirement, (c) 1 honest gap question they'll ask, (d) my 2 questions for them.12. JD diff across 3 companies
Compare 3 similar JDs: {jd1}, {jd2}, {jd3}. For each: scope, level signal, must-haves, culture clues. Recommend which to prioritise for application.Variables to swap: jd1, jd2, jd3
Common mistakes
- No specific context (company / role / level) — output is generic.
- Asking AI to “be honest” without your actual record — it confabulates.
- Same answer for every company — interviewers compare notes.
- No tone anchor — answers land flat.
- Skipping fact-checks — AI invents dates / numbers / titles.
- Treating first draft as final — first drafts read AI-flavoured.
- No peer / mentor review — feedback loop missing.
How to push results further
- Paste real examples to anchor AI to YOUR voice.
- Ask AI to play interviewer first; weak answers reveal themselves.
- Write 3 drafts; ship the third.
- Always read aloud.
- Save successful phrasings in a personal bank.
- Have a peer in the role review.
- Time-box practice — fatigue makes you worse.
Practical depth notes
Use these prompts as starting points, not final answers. For Job Description Fit Analysis Prompts: 12 Templates Before You Apply, the useful extra work is to replace every generic placeholder with a real constraint: audience, channel, length, brand voice, examples to imitate, and examples to avoid. Run at least two versions with different constraints, then compare the outputs side by side instead of accepting the first polished response.
A good result should pass three checks: it is specific enough that another person could reuse it, it avoids vague praise or filler, and it gives you an editable artifact rather than a broad suggestion. If the output feels generic, add one concrete reference, one forbidden pattern, and one measurable success criterion before rerunning the prompt. Before saving a prompt as reusable, test it on one realistic input and one edge case. The realistic input proves the template can produce the normal deliverable; the edge case shows whether it handles messy constraints, missing context, or an unusual audience. Keep the better output, but also keep the failed version with a note on what was missing. That small failure log is what turns a prompt collection from a list of nice sentences into a practical working library.
FAQ
- Can recruiters tell AI-written answers?: Yes when generic. Specifics are the antidote.
- How much research is enough?: 60-90 minutes for an important interview. Beyond, returns diminish.
- When to start salary research?: Before applying. Negotiation that begins after the offer is weak.
- Should I use levels.fyi / Glassdoor numbers?: Yes as a baseline, with caveats. Validate against 2-3 sources.
- How to keep prep notes organised?: One doc per company: research, questions to ask, story bank fits.
- How often to refresh research before final?: Quick re-scan day of interview — news / launches in the past week.
Related
- JD matching prompts
- Resume prompts
- Cover letter prompts
- Recruiter reply prompts
- AI Job Description Analysis: Must-Haves, Gaps, Likely Questions
- Career & Interview Prompts hub
Tags: #Prompt #Job search #JD analysis