Sign inAbout the interview question generator
Most interviews are less unpredictable than they feel. The questions come from three places: the requirements in the job description, the highlights and gaps in your resume, and a short list of questions nearly every employer asks. This free interview question generator uses your target title, experience level, preferred question type, and optionally the job description to list the questions you're likely to hear, so you can prepare for the right ones instead of all of them.
A question list only helps if you practice answering it out loud. Below you'll find how to read a job description for likely questions, what each question type is really testing, how to build a small set of stories that covers dozens of questions, and a short practice plan for the days before your interview.
How to use it
- 1
Enter the job title and level
Use the title from the posting and choose entry level, mid level, senior, or executive. Seniority changes the questions, since senior roles get more about strategy, trade-offs, and leading people.
- 2
Pick a question type
Choose mixed for a full first-round set, or focus on behavioral, technical, or situational if you know the format. Recruiters will usually tell you the format if you ask.
- 3
Paste the job description
Adding the posting ties the questions to that role's requirements, tools, and responsibilities. Without it, you'll still get solid questions for the title in general.
- 4
Sort, outline, and practice
Mark the questions you'd struggle with, outline answers to those first, then say them out loud with a timer. Generate again with a different type to round out your prep.
How to predict questions from the job description
Interviewers usually build their questions from the posting, so every major requirement is a question waiting to be asked. Read the description line by line and turn each requirement into the question you'd ask if you were hiring.
Then read your resume the way the interviewer will. Expect questions about your most recent role, any gap or short stint, a career change, and every number you list. If your resume says you cut costs 18%, be ready to explain how you measured it.
- "Manage multiple stakeholders" becomes "Tell me about a time two stakeholders wanted different things."
- "Experience with SQL and Tableau" becomes "Walk me through a dashboard you built and how people used it."
- "Comfortable with ambiguity" becomes "Describe a project where the goal changed partway through."
- "Own the quarterly forecast" becomes "How do you build a forecast, and what do you do when you miss it?"
What each question type is really testing
Knowing why a question is asked tells you what a good answer has to include. Most interviews mix several of these types, and the balance shifts with the role and the round.
- Behavioral ("Tell me about a time..."): whether you've done this before. Answer with one real example using the STAR structure: situation, task, action, result.
- Situational ("What would you do if..."): your judgment in a scenario you may not have faced. Walk through your reasoning, the trade-offs, and who you'd involve.
- Technical: whether you can do the core work. Expect tool, method, or domain questions, case problems, or live exercises, and explain your thinking as you go.
- Motivation and fit ("Why this role?"): whether you've researched the company and want this job specifically.
- Background ("Walk me through your resume"): whether your career story makes sense. Keep it short, in order, and pointed at this role.
Build a story bank instead of memorizing answers
You can't script answers to every possible question, and memorized answers sound stiff. A better approach is to prepare six to eight stories from your recent work, each with a clear situation, what you did, and a measurable result. Most behavioral questions can be answered with one of them, adjusted to the angle the interviewer asked about.
Choose stories that cover different themes, and note next to each one which questions it could answer.
- A project you led or drove from start to finish
- A conflict or disagreement you helped resolve
- A mistake and what you changed afterward
- A time you had too much to do and had to prioritize
- A result you're proud of, with a number attached
- A time you learned something new quickly
A short practice plan before the interview
Reading questions isn't the same as answering them. Most people find their weak spots only when they hear themselves talk, so plan at least two spoken practice sessions before the real thing.
- Three or more days out: generate questions, sort them into easy, unsure, and hard, and outline answers to the hard ones as bullet points, not scripts.
- Two days out: answer ten questions out loud with a timer, aiming for one to two minutes each. Record yourself if you can.
- The day before: run a full mock interview with a friend or the AI mock interview practice tool, and prepare three questions to ask your interviewer.
- The morning of: reread your story bank and the job description, not the whole question list.
Examples
1. Walk me through a campaign you planned from brief to results. What would you change now?
2. Tell me about a time you had to cut your budget mid-quarter. How did you decide what to keep?
3. How do you decide which channels get more spend when attribution data disagrees?
4. Describe a time a product launch slipped and you had to adjust the marketing plan.
5. What would you do if the sales team told you your leads were low quality?
6. Which metrics would you report to leadership for a brand campaign versus a demand generation campaign?
7. Tell me about a time an agency or freelancer missed expectations. How did you handle it?
8. Why this company, and what would you focus on in your first 90 days?
1. Walk me through a project on your resume. What was the hardest bug you fixed?
2. How would you design a simple URL shortener? What data would you store?
3. Explain the difference between a process and a thread.
4. When would you choose a hash map over an array for a lookup-heavy task?
5. What happens, step by step, when you type a URL into a browser and press Enter?
6. How do you test your code before opening a pull request?
7. Tell me about a time you got stuck. How long did you try before asking for help?
8. Read this function aloud and tell me what it returns and how you'd improve it.
1. Tell me about a time a patient's condition changed quickly. What did you notice first, and what did you do?
2. Describe a disagreement with a physician about a care plan. How was it resolved?
3. Tell me about a time you precepted a new nurse who was struggling.
4. Give an example of a time you caught a medication or documentation error.
5. Describe your hardest shift in the past year and how you prioritized your patients.
6. Tell me about a time you supported a family through difficult news.
7. Describe a process improvement you suggested on your unit and what happened.
8. Tell me about a time you had to speak up about a safety concern.
Tips for better results
- Ask the recruiter who you'll meet and what format to expect, then generate questions for that format.
- Prepare a 60- to 90-second answer to "Tell me about yourself," since it often opens the interview.
- Keep most answers to about two minutes, and stop talking once you've reached the result.
- Practice the hardest questions first, because the easy ones will take care of themselves.
- Write down three questions for the interviewer that the job description doesn't already answer.