Separate Real AI Experience From AI Buzzwords
When to use it
Check whether a resume full of LLM, RAG and agent keywords reflects shipped work or a weekend tutorial.
The prompt
This candidate's resume is full of AI terms. Help me work out what they've actually done before the screening call. {{Paste the resume}} THE ROLE: {{Job Title}}, {{level}} WHAT THE ROLE NEEDS: {{e.g. shipped LLM features used by real customers, model training at scale, evaluation and monitoring}} For each AI claim on the resume: 1. Sort it into one of: shipped to real users; internal tool or prototype; course, hackathon or side project; or can't tell. Quote the line that put it there. 2. For anything that reads as production, what should also be there if it's real: users or traffic, cost, latency, how quality was measured, what went wrong. Point out which of these are missing. 3. Two questions per claim that someone who built it answers with specifics straight away, and someone who followed a tutorial can't. Focus on decisions and failures, not definitions. 4. What a strong answer sounds like and what a weak one sounds like, in plain language I can judge on the call without knowing the technology. Then: 5. Tell me whether the underlying engineering (APIs, data handling, testing, deployment) looks solid, since that usually matters more than which AI framework they named. 6. What I should not count against them: side projects and courses are legitimate evidence of interest and learning, just not of production experience. Don't invent concerns. If a claim is specific and checkable, say it looks credible.
Tip
The question that separates real AI work from demos is almost always 'How did you know it was giving good answers?'. People who shipped something describe an evaluation set, user feedback or a monitoring dashboard. People who didn't describe trying it a few times and it looking right.
How to use it
Paste the prompt into ChatGPT, Claude or whichever assistant you use, then replace every {{bracketed}} part with your own detail. The more specific and messier your input, the better the output — a model given raw notes has more to work with than one given a tidy summary you wrote first.
More Screening prompts
- Screen a Resume Against a JD
- Compare Two Finalists
- Structured Reference Check Questions
- Build a Phone Screen Script
- Turn Screen Notes Into a Candidate Submittal
- Turn Resume Gaps and Job Hops Into Fair Questions
- Work Out What Level a Candidate Actually Is
- Read a Resume That Was Written With AI
- Interpret What a Reference Actually Told You
Open the full tool for all 87 prompts, the glossary, and the JD decoder.