Interview Question Picker

What separates a good interview question from filler

• Ask about the actual work, not the perks. “What does the first ninety days look like for this role?” tells you whether the job is even defined yet; the benefits page tells you nothing you couldn’t read at home.
• Questions that make the interviewer think are the ones they remember afterwards. “What’s the hardest part of this job that isn’t in the description?” gets an honest answer far more often than “what’s the culture like?” ever does.
• Match the question to the stage and the person. A recruiter on a phone screen cannot answer strategy questions, and a founder in a final round should not be spending their slot explaining your start date.
• Never ask something the careers page already answers. It reads as unprepared, and it burns one of the two or three real slots you get on information you could have looked up in a minute.
• Ask at least one question you actually want the answer to. You are deciding as well — the job you took without asking the awkward question is usually the one you leave eight months later.

Example output

1. What does the first ninety days look like for whoever takes this role?
Why this works: a vague answer usually means the role isn’t defined yet — and an undefined role becomes your problem by month two.

2. Which part of the system are you most worried about right now?
Why this works: at Series A there is always one. Their answer tells you what you would actually be maintaining.

3. What’s the hardest part of this job that isn’t in the description?
Why this works: it gives permission to be honest, and honest answers are the only ones worth deciding on.

4. How do you decide between shipping fast and paying down what’s already there?
Why this works: every engineering culture answers this differently, and you will live inside the answer daily.

5. Who would I be on call with, and what does a bad week look like on that rota?
Why this works: on-call is the single largest hidden variable in an infrastructure-heavy role.

6. How will you know in six months that hiring me was the right call?
Why this works: turns a fuzzy job into a short list of things you can actually be measured against.

7. What’s the biggest risk to the company over the next two years?
Why this works: a CTO in a final round has an answer ready. Hearing it tells you what you would be joining.

8. Is there anything about my background that gives you pause?
Why this works: it surfaces the objection that would otherwise be discussed after you leave the room.

(Example output — the picker adapts to the role, stage and side of the table you enter.)

Questions candidates should ask

What does the first ninety days look like for whoever takes this role? — A vague answer usually means the role isn’t defined yet, and that becomes your problem in month two.
What’s the hardest part of this job that isn’t in the description? — Gives permission to be honest, and honest answers are the ones worth deciding on.
Why is this role open? — Growth, backfill and “the last person burned out” are three very different jobs.
How will you know in six months that hiring me was the right call? — Turns a fuzzy role into things you can actually be measured against.
Who would I work with most closely day to day? — Your manager sets the tone, but your peers set the hours.
What does a normal week look like — how much of it is meetings? — The most reliable predictor of whether you will get anything done.
How does the team handle disagreement about priorities? — Every team has this problem; only some have a way of resolving it.
What’s changed about this team in the last year? — Recent history tells you more about stability than any org chart.
What would you want me to fix first? — If they answer instantly, there is a real purpose behind the role.
How is feedback given here — and when did you last give some? — The second half of the question stops the generic answer.
What’s the promotion path from this role, and who took it last? — Named examples separate a real ladder from a slide.
How much of this job is on-call, out-of-hours or travel? — Better asked awkwardly now than discovered in week three.
What tools and systems would I be living in every day? — Tells you what the work is actually made of.
What’s the one thing you’d change about working here if you could? — Asking the interviewer about their own experience gets you a human answer.
How did the last person in this role do, and where are they now? — Internal move, promotion or exit are three different signals.
Is this role remote, hybrid or in-office in practice, not in policy? — Policy and practice diverge, and the tone of the answer tells you which is real.
What’s the budget and headcount picture for this team next year? — A polite way of asking whether the job survives the next planning cycle.
What are the next steps, and when should I expect to hear? — Ends the interview with a commitment you can follow up against.

Questions that impress in a final round

What’s the biggest risk to this company over the next two years? — Senior people have an answer ready, and hearing it tells you what you would be walking into.
Which customer segment is growing fastest, and is it the one you planned for? — Shows you think about the business, not only the role.
What has the team already tried for this problem that didn’t work? — Saves you from proposing it again in month one.
Where does this team’s work show up in the company’s numbers? — Teams that cannot answer this are the first cut in a bad quarter.
What would make you say no to a request from this team? — Reveals the real priorities sitting behind the stated ones.
How do decisions actually get made here — who has to be in the room? — The org chart rarely matches the answer.
What do you want to be true in three years that isn’t true today? — A vision question that cannot be answered with a slogan.
If I do this job well, what changes for your customers? — Ties your work to someone outside the building.
What do new senior hires here consistently get wrong? — Practical, and shows you plan to arrive humble.
How much budget certainty does this team have? — Fair to ask by the final round, and any hesitation is itself data.
What part of the strategy are you least sure about? — Invites candour; a confident non-answer is also informative.
Was anyone considered internally for this role? — Tells you whether you would arrive with someone else’s disappointment in the room.
What would you need from me in the first week to make this easy? — Moves the conversation from evaluation to working together.
Is there anything about my background that gives you pause? — Lets you answer the objection you would otherwise never hear.
What happens next, and who makes the final call? — You want the decision-maker’s name before you negotiate.

Questions hiring managers should ask

Walk me through a project you owned end to end — where did it go wrong? — Ownership and honesty tested in one question.
What part of your last job would you not want to do again? — Gets closer to real motivation than “why are you leaving”.
Tell me about a decision you made with incomplete information. — Most work is exactly this, and few interviews test it.
What do you believe about your craft that most of your peers disagree with? — Separates people who think from people who recite.
How would your last manager describe you at your worst? — The framing makes an honest answer socially possible.
What did you learn in month one of your last role that you wish you’d known on day one? — Tests reflection and tells you how they ramp.
Show me something you made and explain the hard part. — Portfolios are polished; the hard part never is.
When did you last change your mind about something important at work? — Rigidity is the expensive hire nobody screens for.
What would you need from us to do your best work? — Their answer doubles as your retention checklist.
How do you decide what not to do when everything is urgent? — Prioritisation under pressure is most of what seniority means.
Tell me about a time you disagreed with your manager. What happened? — Listen for whether the disagreement was ever actually resolved.
What’s a piece of feedback that stuck with you? — Vague answers usually mean feedback never really landed.
What questions do you have that the job description didn’t answer? — Candidates who prepared show it here first.
If we hired you and it didn’t work out, what would the likely reason be? — Uncomfortable, revealing, and fair, because you are both guessing.
What are you optimising for in your next job — money, scope, stability or learning? — Naming it early prevents an offer nobody wanted.

Frequently asked questions

What questions should I ask at the end of an interview?

Two or three you genuinely want answered, aimed at whoever is in front of you. A recruiter can tell you about process and comp bands; a hiring manager can tell you what the first ninety days hold; a founder can tell you where the company is exposed. Asking the right person the right question matters more than asking a clever one.

How many questions should I actually ask?

Bring five or six, expect to ask two or three. Interviews run over and the last slot is often short, so put the question you most want answered first rather than saving it. If you are told there is no time, ask for the one answer by email — that is a reasonable request and the reply is usually more considered.

Is it bad to ask about salary in an interview?

Not at a screening stage, where confirming the band saves everyone weeks. It is worth avoiding as your only question in a final round, where it reads as though nothing else about the job registered. Ask about range early with the recruiter, then spend the later rounds on the work itself.

Why is this free — what's the catch?

No catch and no signup. This tool is funded by EaseClaw, an AI agent that finds people publicly asking for what you sell and drafts your replies. If the free tool is useful, some people try the free trial. That's the whole business model.

More free tools

All free tools →