The 25 Best AI Prompts for Job Interview Prep

Most people prep for interviews wrong. They spend hours memorizing canned answers to questions that are easy to anticipate, and almost no time on the questions that are harder to predict or that would actually test their thinking. AI is useful for the stuff that genuinely responds to drilling: finding your strongest examples, polishing a "tell me about yourself," pressure testing your weaknesses, and running mock interviews in the voice of the type of interviewer you are about to face. Where it is not useful is in replacing the raw material of your career. The better your notes about what you actually did, the better these prompts work.

Below are 25 prompts I use when I am prepping a friend (or myself) for an interview. Resumes, job descriptions, raw stories, and rough draft answers all go into {{clipboard}}. Find the five or six that match your prep style and keep them a keystroke away so you can practice the night before without rebuilding prompts from scratch.

---

Download Free for macOS

Researching the company and role

1. Build a company cheat sheet for an interview

I have an interview coming up and I need a cheat sheet on the company that goes beyond the homepage. Not a marketing summary. What a thoughtful candidate would actually want to know before walking in.

Here is what I have about the company: their site, any recent news, and the job description.

{{clipboard}}

Produce:

1. What the company does in one sentence a customer would recognize.
2. Who they sell to (target audience), stated concretely.
3. The three things they seem to be betting on this year, inferred from recent announcements and the job description.
4. Their main competitors and what makes them different from each.
5. A recent news item, hire, launch, or milestone that I could reference naturally.
6. The company's public voice and culture signals from how they write about themselves.
7. The two questions I should have ready to ask that would show I did real research.
8. One risk or challenge the company is probably facing that I should be aware of but careful about bringing up.

Do not invent details about the company. Only work with the material I pasted.

2. Decode the job description for what they actually want

I have a job description and I want to decode what the hiring team actually cares about, not just the laundry list.

Here is the JD:

{{clipboard}}

Produce:

1. The three most important responsibilities, inferred from emphasis and repetition.
2. The hidden requirements that are not explicitly listed: personality, working style, seniority signals.
3. The skills that are "nice to have" versus the skills that are actually must haves despite the framing.
4. What the first six months of this role probably look like, based on the description.
5. The success metric the hiring manager probably cares about the most.
6. Any phrasing that suggests the role is newly created, backfilling someone who left in frustration, or being restructured.
7. The three questions from this JD that will most likely come up in the interview.

Do not pad. If a requirement is not actually important, say so.

3. Map my experience to the job requirements

I want to know where my experience maps to the job requirements and where it does not, so I know what to emphasize and what to be ready to explain.

Here is my resume and the job description:

{{clipboard}}

Produce:

1. A table with three columns: requirement, my matching experience, and a confidence score from 1 to 5.
2. The three strongest alignments I should lead with when they ask about experience.
3. The three biggest gaps and how I should frame them if they come up.
4. The one question the interviewer is most likely to ask about a gap in my background.
5. A specific story from my experience that I should have ready for each of the top three requirements.
6. Any requirement that is a dealbreaker for me to not mention at all versus one I can acknowledge directly.

Do not invent experience. Work only with what is in my resume.

Tell me about yourself

4. Draft a strong "tell me about yourself" answer

I need a good answer to "tell me about yourself." Not a resume read aloud. A narrative that makes sense for this specific role.

Here is my career summary and the role I am interviewing for:

{{clipboard}}

Produce:

1. A 90 to 120 second answer structured as: where I am now (present), what I have done that is most relevant (past), and what I am looking for next (future).
2. The single strongest line I could use as a hook.
3. The two or three specific accomplishments I should name, chosen for fit with the role.
4. A warm closing that transitions naturally into the interviewer's next question.
5. A shorter 45 second version for fast moving interviews.
6. A version in a more casual voice and a version in a more formal voice so I can match the interviewer's energy.

No "I am passionate about." No "throughout my career." No "journey."

5. Tighten a rambling "tell me about yourself"

I wrote my answer to "tell me about yourself" and it is too long, too rambling, and loses the interviewer halfway through. Help me tighten it.

Here is my draft:

{{clipboard}}

Produce:

1. A tightened version under 120 seconds (about 250 words spoken).
2. The specific lines I cut and why each was cut.
3. The strongest sentence in the original that should stay exactly as it was.
4. A suggestion on which part deserves more time and which should be trimmed further.
5. A note on the pacing: where to pause, where to slow down.
6. An alternative structure (problem, pivot, payoff) if the current structure is not working.

Do not lose the moments that are specific to me. Cut the connective tissue, not the story.

6. Generate variations of my answer for different interviewers

I have one strong "tell me about yourself" answer but I want variations for different interviewers: hiring manager, HR, engineering, executive, and peer.

Here is my base answer:

{{clipboard}}

Produce:

1. A version tuned for a hiring manager: leads with outcomes and fit for the team.
2. A version tuned for HR: leads with motivation, culture fit, and narrative.
3. A version tuned for a technical peer: leads with the craft and specific technologies.
4. A version tuned for an executive: leads with strategic impact and judgment.
5. A version tuned for a fellow engineer or peer: leads with curiosity and collaboration.

Each version under 120 seconds. Each preserves the core of the answer but emphasizes different elements. A note on which version to use if I am not sure who the interviewer is.

Behavioral questions with STAR

7. Turn a raw story into a STAR structured answer

I have a rough story from my experience that I want to use for a behavioral question, but it is messy. Turn it into a clean STAR answer (Situation, Task, Action, Result).

Here is the raw story and the question it is for:

{{clipboard}}

Produce:

1. Situation: one or two sentences of context, grounded in specifics.
2. Task: what was actually expected of me and why it was hard.
3. Action: the specific things I did, in first person, emphasizing my individual contribution.
4. Result: the concrete outcome with a number or specific detail if possible.
5. A short coda: what I learned or what I would do differently.
6. Total length: 90 to 120 seconds when spoken.

Do not invent details. If the story is missing a part I need, tell me what to ask myself to fill it in.

8. Generate a list of behavioral questions likely to come up

Based on the role and the job description, predict the behavioral questions I am most likely to face so I can prep specific stories for each.

Here is the role and JD:

{{clipboard}}

Produce:

1. Ten behavioral questions ranked by likelihood.
2. For each question, the competency it is testing.
3. The kind of story I should have ready for each one (scope, stakes, complexity).
4. A pattern check: any competency that shows up in multiple questions, so I can prep a single story that covers several.
5. The one question that is most likely to be a curveball for someone with my background, and why.

Do not list generic "tell me about a time when" questions. Tailor them to this role.

9. Write a behavioral answer that avoids common mistakes

I wrote a draft answer to a behavioral question and I want you to catch the common mistakes before I use it in an interview.

Here is the question and my draft:

{{clipboard}}

Check for:

1. Whether I talked about myself (I) or the team (we). Behavioral answers should emphasize my individual contribution.
2. Whether the situation is specific or generic.
3. Whether the action is concrete, not a list of buzzwords.
4. Whether the result has a number, a before/after, or a specific outcome.
5. Whether the answer runs too long or too short.
6. Whether the story actually answers the question asked, or drifts into a different story.
7. Any language that sounds rehearsed or corporate.

Rewrite the answer with the fixes applied. Flag anything I need to remember to say in my own voice rather than reading your rewrite.

Technical and case interviews

10. Generate a set of technical questions for my role

I have a technical interview coming up for a specific role and stack. Generate a set of likely questions I should prep for.

Here is the role, the stack, and my level:

{{clipboard}}

Produce:

1. Ten technical questions ranked by likelihood and difficulty.
2. For each question, the concept it is testing.
3. A one line hint on how I should approach it (the first thing to say out loud when I hear the question).
4. A flag for any question that is a known trap for candidates at my level.
5. The three questions I should prep cold because the answer is pure recall.
6. The three questions I should prep by practicing out loud, not by memorizing.

Do not include leetcode style questions unless the role specifically requires them.

11. Walk me through a case study question

I have a case study or product sense question and I need a structured walkthrough so I can practice the approach.

Here is the case or question:

{{clipboard}}

Produce:

1. The first thing I should say to buy time and signal I am thinking clearly.
2. A framework for structuring the answer appropriate to this kind of question.
3. The three key questions I should ask the interviewer before diving in.
4. A sample walkthrough of the answer using the framework, in first person.
5. The one trap I should avoid in this kind of question.
6. The one signal the interviewer is looking for that most candidates miss.
7. A time allocation: how long I should spend on each part.

Do not give me the perfect answer. Give me the approach and let me practice.

12. Review my solution to a technical problem

I solved a technical interview problem and I want you to review my solution before the real interview.

Here is the problem and my solution:

{{clipboard}}

Produce:

1. A correctness check: does my solution actually solve the problem for the stated and unstated cases?
2. Any edge case I am not handling.
3. The time and space complexity of my solution.
4. A more efficient version if one exists.
5. A more readable version if the current one is clever but hard to follow.
6. The question the interviewer is most likely to ask as a follow up, and how I should answer it.
7. A scoring on how strong my solution is for the role's level.

Be direct. If my solution is bad, say it is bad. If it is good, say what makes it good so I know what to repeat.

Handling hard questions

13. Prepare an answer for a question about my weaknesses

I need to answer "what is your biggest weakness" without the cliche "I am a perfectionist" response.

Here are my actual weaknesses or growth areas:

{{clipboard}}

Produce:

1. Three candidate answers, each using a real weakness I gave you.
2. Each answer should name a real weakness, describe how I have been working on it, and show concrete progress.
3. Each should avoid weaknesses that would raise flags for this specific role (for example, not "I am bad at deadlines" for a delivery role).
4. Each should be under 90 seconds.
5. A note on which weakness I should pick based on the role, and why.
6. A trap to avoid: the fake weakness that sounds like a strength ("I care too much").

14. Prepare an answer for why I left or am leaving a job

I need to answer "why did you leave your last job" or "why are you looking to leave your current job" in a way that is honest but does not sound bitter.

Here is the actual context:

{{clipboard}}

Produce:

1. A forward looking answer under 60 seconds.
2. No complaints about a former employer, boss, team, or company.
3. An honest acknowledgment of what was not working, framed as a mismatch rather than a failing.
4. A pivot to what I am looking for that connects to the role I am interviewing for.
5. A version for a neutral departure and a version for a harder one (layoff, toxic environment, burnout).
6. A rule of thumb: the less time I spend on the old job, the stronger the answer.

15. Respond to a question about a gap or job change pattern

I have a resume gap or a pattern of short tenure and I need to address it if it comes up.

Here is the situation:

{{clipboard}}

Produce:

1. A direct answer that addresses the concern head on, under 45 seconds.
2. A framing that makes the gap or pattern into part of a coherent story rather than a red flag.
3. A focus on what I did during the gap (learning, caretaking, health, side projects) that is forward looking.
4. A note on when I should offer the explanation proactively versus wait for them to ask.
5. A short pivot back to the role I am interviewing for.
6. A flag for any phrase I should avoid because it sounds defensive.

Do not over explain. Short and honest beats long and rehearsed.

Questions to ask the interviewer

16. Generate smart questions to ask the interviewer

Interviewers expect me to ask questions at the end and I want ones that are thoughtful, not generic.

Here is the role and what I know about the company:

{{clipboard}}

Produce:

1. Ten questions ranked by how strong they are for this specific role.
2. A mix across topics: role specifics, team dynamics, success metrics, company strategy, culture, the interviewer's own experience.
3. None should be answerable by reading the website.
4. None should be negative or suspicious in tone.
5. At least one should be a question the interviewer will probably not have an easy answer to, which signals I am thinking about the role seriously.
6. A flag for the one question I should save for the hiring manager specifically, not a junior peer.

17. Ask the interviewer about failure, risk, or a real concern

I want to ask the interviewer a question that gets past the rehearsed answers and actually tells me what this job is like. Not a gotcha, just a genuine question that invites a real answer.

Here is the role:

{{clipboard}}

Produce:

1. Three candidate questions, each inviting honesty about a real topic: failure, attrition, changing priorities, or unmet expectations.
2. Each phrased respectfully and curiously, not as an attack.
3. Each should produce a useful signal whether the answer is positive or negative.
4. A warning about how to read the non verbal response if the interviewer deflects or gives a canned answer.
5. A note on which candidate is senior enough to ask these and which is probably too junior to risk it.

Salary and compensation questions

18. Prepare an answer for expected salary

I need to answer "what are your salary expectations" without anchoring too low or pricing myself out.

Here is my research on the market rate and my own target:

{{clipboard}}

Produce:

1. A response that declines to name a number first, redirecting to the role's budget.
2. A response that gives a range, with the bottom of the range being my actual minimum.
3. A response for if they insist on a specific number.
4. A note on when to use each version.
5. The one phrase to avoid: "I am flexible" (it signals I will take less).
6. A follow up question to ask that shifts the conversation back to fit and value before committing to a number.

19. Negotiate an offer after the first number is on the table

I received an offer and I want to negotiate it, but I want to do it in a way that does not feel adversarial or transactional.

Here is the offer and my target:

{{clipboard}}

Produce:

1. An email response that thanks them warmly and then opens the negotiation with a specific ask.
2. The specific ask should be grounded in research, need, or another offer (not "I want more").
3. A fallback position if they say no to the primary ask.
4. A note on what to negotiate beyond base salary: signing bonus, equity, start date, vacation, title.
5. A warning about the points I should not push on, either because they are fixed or because pushing will damage the relationship.
6. A closing that keeps the door open and does not make it an ultimatum.

Post interview follow up

20. Write a thank you email after an interview

I just had an interview and I want to send a thank you note that is warm, specific, and actually useful.

Here is who I met and what we talked about:

{{clipboard}}

Produce:

1. An email under 120 words.
2. References at least one specific moment from the conversation.
3. Reinforces one key point I made during the interview that I want to stay memorable.
4. Addresses any question I did not answer as well as I wanted to, in one sentence.
5. Closes with genuine enthusiasm without being effusive.
6. Subject line under 40 characters.

Do not be sycophantic. Do not pretend the interview changed my life. Just be specific and warm.

21. Follow up after an interview without hearing back

I had an interview and the timeline has passed with no update. I want to follow up without sounding desperate.

Here is the context:

{{clipboard}}

Produce:

1. A follow up email under 80 words.
2. Polite, professional, not guilt tripping or pushy.
3. A specific reference to the interview so it is clear which role I am asking about.
4. A direct but respectful request for an update.
5. A soft reiteration of interest.
6. An implicit acknowledgment that things move slowly, without excusing bad communication.
7. Subject line that signals the intent clearly.

Do not mention other opportunities unless I told you I have one on the table.

22. Debrief my own interview performance

I just finished an interview and I want to debrief myself honestly so I can learn from it. Not to beat myself up, to improve.

Here is how it went:

{{clipboard}}

Walk me through:

1. The moment in the interview I felt strongest, and why.
2. The moment I felt weakest, and what I could have said instead.
3. Any question I think I answered well but that the interviewer did not react strongly to. Why might that be?
4. A signal from the interviewer that I might have missed or misread.
5. What I should prep differently for the next round if there is one.
6. An honest assessment of whether I am likely to move forward, based only on what I told you.

Be direct. If I did not do well, say so. If I am overthinking, say that too.

Mock interview practice

23. Run a mock interview in a specific voice

I want to practice an interview with you playing the interviewer. Ask me questions one at a time, evaluate my answers, and push back when the answer is weak.

Here is the role, the interviewer type (hiring manager, HR, engineer), and what I want to practice:

{{clipboard}}

Instructions for you:

1. Stay in character as the interviewer for the whole conversation.
2. Ask one question at a time and wait for my answer.
3. After each answer, give brief feedback: what worked, what did not, one specific improvement.
4. Follow up on weak answers the way a real interviewer would, with a more specific version of the question.
5. Do not give me the "perfect" answer. Force me to find it.
6. At the end of the mock, summarize the three biggest patterns in my answers and the one thing I should practice most before the real interview.

Start with the first question now.

24. Stress test a single answer

I have an answer to a specific question and I want you to stress test it like a skeptical interviewer.

Here is the question and my current answer:

{{clipboard}}

Produce:

1. Three follow up questions a sharp interviewer would ask based on my answer.
2. For each, the specific weakness in my answer that invited the follow up.
3. A revised version of my original answer that is less vulnerable to those follow ups.
4. The one claim in my answer that is the biggest liability if the interviewer digs in.
5. A version of the answer where I preempt the toughest follow up before it is asked.

25. Rehearse the specific phrasing of a critical moment

There is one specific moment in an interview I am nervous about: a question I know is coming and I want the exact language to use.

Here is the question and the gist of what I want to say:

{{clipboard}}

Produce:

1. A word for word script I could rehearse, between 45 and 90 seconds.
2. A second, shorter version for when I need to be concise.
3. The single most important sentence to say exactly right, in bold.
4. Three words or phrases to avoid because they weaken the answer.
5. A note on where to pause, where to slow down, and where to let the silence sit.
6. A tip on how to make the scripted answer sound unrehearsed when I deliver it.

The goal is confidence in the moment, not sounding like I memorized a script.