Most job descriptions are badly written. Not because recruiters are bad people, but because JDs get drafted in a rush, copied from old postings, and edited by four different people before going live. You end up reading a wall of standard phrases and still have no idea who they actually want. Claude handles this better than any human reader, because it doesn't get tired and doesn't make assumptions based on the company brand.
I put together 4 prompts that actually work. No magic, just specific questions that pull out what's between the lines of any job posting. I use them myself before every screening call.
Prompt 1: what they actually want (and didn't write)
This is the first and most important prompt. Copy the job posting text and give Claude this task:
Prompt: "Here is a job description. Split it into three categories: (1) hard requirements - they won't look at you without these; (2) 'nice to have' that are actually hidden hard requirements - things phrased softly but meant seriously; (3) requirements not mentioned in the text but logically implied by the role, stack, or industry. For each category, give a short explanation of your reasoning."
Why does this matter? Because recruiters often write "nice to have" where the hiring manager means "don't even show up to the tech interview without this." Claude spots language patterns and tells these apart much better than you do when reading your fifth JD of the day.
Prompt 2: red flags you glossed over
When you really want a job, you stop noticing the warning signs in the posting. That's just how the brain works. Claude doesn't want the job, so it's more honest.
Prompt: "Read this job description as a skeptical candidate with 10 years of experience. Find up to 5 potential red flags - phrasing that might indicate a toxic environment, unrealistic expectations, a blurry role scope, signs of team chaos, or company financial instability. For each one, explain what specifically concerns you and what question to ask on the screening call to test your suspicion."
Phrases like "we're looking for someone comfortable with constant change" or "this role suits someone who can wear many hats" - Claude catches these and explains what they might mean in practice. Sometimes nothing scary. But better to know upfront.
- "Fast-paced environment" - could mean a busy team or could mean chaos with no processes
- "Ownership mentality" with no team description - often means you'll be flying solo
- Posting open for 60+ days - either very specific requirements, or something is pushing candidates away
- Three different job titles in one posting - internally nobody agreed on who they're looking for
- No salary range or just "competitive" - either they don't know, or they know and it's embarrassing
Prompt 3: questions you should NOT ask on the screening call
A screening call with a recruiter isn't a tech interview, but people still mess it up. Not from lack of knowledge, but from asking the wrong questions. There are things a recruiter can't or won't answer, and if you ask them, you come across as either naive or confrontational. Claude helps filter those out before the call.
Prompt: "I'm preparing for a screening call with a recruiter for this role. Here are the questions I want to ask: [insert list]. Tell me which ones: (1) sound bad in a recruiter screening - better asked to the hiring manager or later; (2) signal incompetence or not reading the JD; (3) are actually useful for a recruiter to answer. Rephrase the bad ones so they can be asked properly."
For instance, asking a recruiter "what's the backend architecture?" is odd - they don't know. Asking "how many devs are on the team?" is fine. Asking "why is this position open?" right on the screening call is a bit aggressive - better in round two. Claude breaks down these nuances without judgment.
- Technical stack or architecture details - pointless to ask the recruiter
- "What's your code review process?" - great question, wrong person
- "When will I hear back?" at the end of the very first call - sounds anxious
- Anything already answered in the job description - it signals you didn't read it
Prompt 4: what to tweak in your CV for this specific role
Most people either don't tailor their CV at all, or they rewrite the whole thing - both are wrong. Tailoring is not about rewriting, it's about repositioning emphasis. Claude can tell you exactly what to bring forward.
Prompt: "Here is the job description and here is my CV. Do not rewrite the CV. Instead tell me: (1) which 3 items from my experience most closely match the priorities of this role - and whether they should be moved higher; (2) which keywords from the JD are missing from my CV but my experience actually covers - where I should rephrase for accuracy; (3) what in my CV is likely to catch the ATS for this role, and what might get lost."
If you want to speed this up, run your CV through the AI CV Analyzer first - it gives you a baseline ATS score with line-by-line feedback on each section. Then bring those specific findings to Claude along with the JD. The two tools complement each other well: one gives you the general picture, the other sharpens it for a specific posting.
How to turn this into one pre-application flow
In practice this takes 15-20 minutes. Not every posting is worth it - but if you've already decided to apply, better spend those 20 minutes than find out on the screening call that half their requirements surprised you.
- 1Copy the JD text into Claude - prompt 1, get a realistic read on requirements
- 2Run prompt 2 for red flags - decide whether this role is even worth your time
- 3Draft your screening call questions and check them through prompt 3
- 4Paste in your CV and run prompt 4 - adjust the emphasis, don't rewrite everything
- 5Add the job to your tracker with status and notes - so you don't forget what you learned
That last point is underrated. Three weeks later you won't remember what specifically worried you about company N's posting, or which questions you had prepared. If you keep a job tracker with notes for each position, that information doesn't disappear between rounds.
A couple of words on limitations
Claude doesn't know the company's internal culture. It only sees text. If the JD is well-written and honest, the analysis will be accurate. If it's a template with no detail, Claude will tell you there's not much to work with - and that itself is useful information. A vague job posting is also a signal.
One more thing: if you're applying from Ukraine to foreign positions, keep in mind that Claude may not know local market nuances. For Polish, Czech, or British companies, some "red flags" might be completely normal in that culture. You need extra context here - either from people who've worked there, or from market data.
- Short descriptions with no details - Claude will say there's too little to analyze, and it'll be right
- Cultural norms of different markets - verify separately, Claude isn't perfect here
- New or niche tech stacks - Claude can be wrong about what counts as a "logical" implied requirement
Short version: it's a tool, not an oracle. But even as a tool it takes a significant chunk of cognitive load off your plate - load that used to hit you exactly when you'd already burned through your twentieth posting of the week.
Organise your job search with Trackr
Track applications, analyse your CV with AI, and prepare for interviews - free.
Get started free
