Free tool for job seekers
Interview questions from a job description
Paste the job post you're preparing for. Each question shows the line it came from, so you can see why it might come up.
Paste the job post
How it reads a job post
The questions come from fixed rules that match phrases in the post, not from AI. They are practice questions drawn from the post, not the employer's actual list.
- A license, degree, certification, card or driving requirement: A screening question, listed first: do you have it today, and what can you show?
- Reliable or dependable transportation: A screening question, listed first: how would you get to work on time for every shift?
- An age, physical, citizenship, work-authorization, drug-screen or medical-exam line: A yes-or-no screen, listed first: physical demands "with or without reasonable accommodation", exams "if you receive an offer", nothing about health or medication. It repeats what the post asks; it doesn't make the requirement lawful. A US-citizens-only line, for example, generally needs a law, regulation, executive order or government contract behind it, and work authorization is a separate question. Medical exams may come only after a conditional offer and only if everyone hired for that job takes them; drug tests follow their own state and local rules.
- Any other short requirement: A question listed with the other requirements: do you meet it today, and what would you point to?
- A "willing to" or "able to work" line, or a schedule, travel or location line: A fit question about your availability: can you commit to it, and from when? You don't need to share personal reasons.
- A years-of-experience line ("3+ years"): A depth question: two examples from those years and your role in each.
- Experience with a tool, field or setting: A proof question: your strongest example, and what you did in it.
- A duty that starts with a verb: A behavioral question about the closest work you've done, even when it mentions a card, a license or an exam. Technical duties sometimes become a scenario: how would you approach it here?
- A nice-to-have: "a plus," "preferred" or "bonus": A bonus question: what have you done with it, or how close have you come? A line that also says "must" or "required" stays a requirement, under any heading.
- Culture, values and stock soft skills: Mostly skipped. Lines such as "strong communication skills" fit almost any post, so at most one gets a question, listed last. A line that names something concrete, such as the product, is kept.
Screening, fit and years-of-experience questions come first, then duties, other requirements and nice-to-haves. The order groups questions by type; it doesn't rank how much each one matters. You get at most 15.
Worked example
This short post:
Customer Support Team Lead What you'll do - Lead a team of 6 support agents across two shifts - Resolve escalated customer issues within SLA - Report weekly metrics to the Head of Support Requirements - 3+ years in customer support, including 1 year as a team lead - Experience with Zendesk - Ability to work one weekend per month
gives these 6 questions:
- From the post: “3+ years in customer support, including 1 year as a team lead”
Which two examples best show your 3+ years of customer support, including 1 year as a team lead, and what was your role in each?
What they check: Your years, scope and depth: say how long you've done this work, then show the kind of work this role does.
Practice follow-up: Who on that team grew the most, and what exactly did you do for them? - From the post: “Ability to work one weekend per month”
Can you commit to working one weekend per month, and from when?
What they check: Whether your availability and plans match what the role needs. Answer about availability; you don't need to share personal reasons.
Practice follow-up: What would you need from the employer to make it work? - From the post: “Lead a team of 6 support agents across two shifts”
Tell me about a time you had to lead a team of 6 support agents across two shifts. What did you do, and what changed?
What they check: Whether you have led people yourself, and what changed for them because of you.
Practice follow-up: What did your team say you should do less of? - From the post: “Resolve escalated customer issues within SLA”
What's the closest you've come to having to resolve escalated customer issues within SLA, and what was your part in it?
What they check: How you find out what the people you serve need, and act on it.
Practice follow-up: How did you know it had worked? - From the post: “Report weekly metrics to the Head of Support”
Walk me through the last time you had to report weekly metrics to the Head of Support. What did you own?
What they check: Whether you can name the number you moved and how much of it was your doing.
Practice follow-up: What was the number before and after, and how much of it was your doing? - From the post: “Experience with Zendesk”
What's your strongest example of work with Zendesk, and what was your role in it?
What they check: That the line on your resume holds up when someone asks for one concrete case.
Practice follow-up: Which actions were yours, and how did they shape the outcome?
What it cannot do
It only reads job posts in English, and it skips company boilerplate such as benefits, pay ranges and equal-opportunity statements.
It can't see the company's own interview questions, and it doesn't invent facts about the company. Prepare the usual ones too: "Tell me about yourself," "Why this company?", pay expectations, and two questions of your own.
A question list is the start. Saying the answer out loud, and handling the follow-up, is where the gaps show.
FAQ
How do I predict interview questions from a job description?
Go line by line through the requirements and responsibilities. Hard requirements such as licenses, schedule and location become screening questions; required years become "give two examples" questions; duties become "Tell me about a time you…" questions; skills become "show me an example" questions. This tool applies those rules and keeps the source line next to each question.
Are these the questions the employer will actually ask?
No one outside the hiring team knows that. These are the questions the post itself points to: the requirements and duties the employer chose to write down. Treat them as a checklist to prepare, not a prediction.
Does my job description get uploaded anywhere?
Not by this tool: the questions are built in your browser. The practice link carries the post after the #, a part of the address browsers leave out of the page request. The practice page reads it in your browser and sends nothing until you press Start; then the post goes to MakeInterview so the interviewer can use it.
Why not just paste the job post into ChatGPT?
You can, and a chatbot can cover more ground: company research, case questions, system design. This page does a narrower job. It shows which line of the post each question comes from, puts screening questions such as licenses, dates and location first, and gives the same list every time. Use it as a checklist of what the post points to, then practice answering out loud, in depth.
How should I practice the questions?
Start with the three duties most central to the role, then the ones where your experience is thinnest. Answer screening questions directly, give one specific example for each behavioral question, and walk through your approach and trade-offs for each scenario. Then answer the follow-up shown under each question, out loud. MakeInterview can run that as a spoken mock interview from the same job post; the first interview is free.