Practical Task
Prepare for a job interview from the role and your real experience
Map the job description to stories you can honestly tell instead of memorizing generic interview answers.
What this helps you do
Job seekers who want structured preparation without inventing experience they do not have.
What you need
- The job description
- Your resume or a summary of your real experience
- Any known interview format
Do it step by step
- 1
Paste the job description and your real background after removing unnecessary personal details.
- 2
Ask AI to map the role's major needs to experiences you actually have and flag gaps honestly.
- 3
Choose four or five stories that demonstrate different things: delivery, problem solving, conflict, learning, leadership, or recovery from a mistake.
- 4
Practice telling each story in your own words with context, action, and result rather than memorizing generated prose.
- 5
Generate thoughtful questions about the role, team, expectations, and success measures.
Use this in your AI assistant
Starter instructions
Copy the starter below, then paste it into ChatGPT, Copilot, Gemini, Claude, or whichever capable AI assistant you use. If this Task calls for photos or files, attach them in that AI assistant too — not on this page.
Help me prepare normally for this interview using only my real experience. First map the role's major needs to evidence from my background and mark any gaps honestly. Then identify 5 stories I should be ready to tell, what each story demonstrates, and 5 thoughtful questions for the interviewer. Do not invent accomplishments, tools, or responsibilities. Job description: [PASTE]. My background: [PASTE].
Helpful checkWhat a good result looks like
A compact preparation map that reminds you which real stories answer which needs in the role.
Tips and watch-outs
- Rewrite AI-generated story notes into words you naturally use; sounding rehearsed can be worse than sounding concise.
- If the employer restricts AI use during interviews or assessments, use AI only for ordinary preparation before the interview and follow their rules.
OptionalGo deeper when you want to
Build an evidence map, not a list of likely questions
Start with the role's needs and map each one to evidence you genuinely have: a project, responsibility, result, failure, or learning experience. One story can support several needs, but the assistant should never fill a gap with something that merely sounds plausible.
Keep an explicit 'thin or missing evidence' column. That tells you what to answer honestly rather than what to fabricate.
Practice the skeptical second question
Prepared stories often sound good until someone asks for the part that proves you were actually there. Have the assistant challenge each story with follow-ups about your specific role, tradeoffs, numbers, disagreements, what went wrong, and what you would change.
Pressure-test a story
Ask me one skeptical follow-up at a time. Focus on details that would reveal whether I really understand the work: what I personally did, why we chose that approach, what tradeoff we accepted, what evidence showed it worked, and what I would change now.
Use your questions to test the job too
The last part of preparation is not performing interest. Turn the role description and what you care about into questions that help you evaluate scope, success measures, decision authority, team dependencies, technical debt, growth, and what is difficult about the job today.
After the interview, capture what you learned while it is fresh and update your view of the role instead of treating the process as one-way evaluation.