Interview Questions to Ask Candidates

The best interview questions to ask candidates force them to reconstruct real decisions - not recite rehearsed strengths. Below are 20 strategic interview questions that work across roles, grouped by what they reveal, each with guidance on what a strong answer shows. For role-specific depth, use the 50+ role question sets linked at the end. The Cognitive runs question sets like these as live interviews, scored against a rubric fixed before the call.

Strategic interview questions to ask candidates (with what strong answers show)

1. "Walk me through the piece of work you're proudest of. What made it hard?" - Strong answers name constraints, trade-offs, and their specific contribution; weak ones describe the team's work.

2. "Tell me about a decision you got wrong. What did you change afterward?" - Tests honesty and learning; candidates who can't name a real mistake haven't reflected.

3. "What did you actually do in your first 90 days at your last role?" - Specifics here predict specifics on the job.

4. "Describe a time you disagreed with your manager. How did it resolve?" - Reveals judgment, communication, and whether they can disagree productively.

5. "What's the most important thing you've deprioritized recently, and why?" - Prioritization under constraint is the real skill behind most roles.

6. "Teach me something you know well in 2 minutes." - Communication clarity and depth of understanding, in 1 question.

7. "What would your last team say is your weakness - and would they be right?" - Self-awareness with an external anchor beats the rehearsed 'perfectionism' answer.

8. "Walk me through how you'd approach your first month here." - Tests preparation and whether they think in plans or platitudes.

9. "When did you last change your mind about something important at work?" - Intellectual flexibility; strong answers include what evidence moved them.

10. "What does 'done' mean to you on a piece of work?" - Quality bar and ownership, revealed indirectly.

Good interview questions to ask candidates, by what you're testing

  • Ownership: "Tell me about a time something failed and no one asked you to fix it. What did you do?"
  • Collaboration: "Describe the hardest stakeholder you've worked with. How did you make it work?"
  • Problem-solving: "Give me a problem you solved where the obvious answer was wrong."
  • Resilience: "What's the longest you've persisted on something that wasn't working - and was persisting right?"
  • Motivation: "What would make you leave this job in a year?" - honest answers predict retention better than 'where do you see yourself in five years'.
  • Judgment: "Tell me about a time you had to decide with incomplete information. How did you bound the risk?"
  • Craft: "What separates good work from great work in your field?"
  • Coachability: "What's the most useful piece of critical feedback you've received?"
  • Speed vs quality: "When is it right to ship something you're not proud of?"
  • Curiosity: "What have you learned recently that wasn't required for your job?"

How to run these questions so the answers are comparable

  • Ask every candidate the same core questions in the same order - unstructured interviews are the biggest source of noise in hiring.
  • Score against anchored criteria immediately after the interview, tied to what was actually said.
  • Follow up twice on every substantive answer: 'what specifically did you do?' then 'what would you do differently?' Rehearsed answers collapse on the second follow-up.
  • At volume, consistency breaks down across human interviewers - The Cognitive's AI interviewer holds every candidate to the same rubric and the same scoring standard, while deciding each follow-up live from the answer given, and returns evidence-scored results.

Pre-screening interview questions for a phone screen

A phone screen is the short first call that decides who gets a full interview. Pre-screening interview questions are filters rather than assessments: they confirm motivation, availability, compensation expectations and a first read on the core competency, so nobody spends an hour finding out something a short call would have surfaced.

  • "What does your current role actually involve day to day?" - the fastest check that the résumé and the job match.
  • "What are you looking for that you can't get where you are?" - motivation, and the earliest honest signal about retention.
  • "Which parts of this work have you owned end to end, and which have you only worked alongside?" - ownership versus proximity, settled in 1 question.
  • "What is your availability, notice period, and location or timezone situation?" - the logistics that sink offers when they surface late.
  • "What compensation range are you working toward?" - asked in the screen, not at the offer, wherever local rules allow it.
  • Keep the screen's criteria a subset of the full interview's, so the two stages ladder instead of duplicating each other.
  • The Cognitive runs this stage as a live AI interview any hour of the day: the rubric is fixed before the call, and each question is chosen in the moment from what the candidate just said.

How to source candidates to ask these questions to

Candidate sourcing is finding and contacting people who match a role before they apply. Screening judges whoever arrived; sourcing decides who arrives. The best question set in the world cannot rescue a pipeline that never contained the right people, which is why sourcing - not interviewing - is usually the constraint on a hard role.

The Cognitive covers that half as well as the interview: describe the role in a sentence or paste the job description, and it becomes visible, correctable filters over ~900M profiles, with every match ranked against the whole requirement and carrying a written "Why them?" you can check.

  • Search the market, not the inbox: the people already doing the job elsewhere are the reason a pool is deep rather than wide.
  • Start from the requirement rather than the keyword. A search that reads the whole role returns people whose experience matches; a keyword search returns people whose CV wording matches, which is a different and smaller set.
  • Include the adjacent titles deliberately. The widest part of any qualified pool is people doing the job under a label you would not have thought to type.
  • Read the timing signals first - tenure in seat and open-to-work status tell you who is realistically reachable this month.
  • Settle the disqualifiers in the first message - location, level, compensation range, start date - so no interview slot is spent discovering something a sentence would have surfaced.
  • Expect the second and third touch to do the work. A passive candidate rarely answers the first message, and a sequence that stops at 1 measures nothing except how many people were looking that week.
  • Each candidate a search returns costs 1 credit; revealing a verified email costs 5 credits and a direct phone number 10, charged only when the reveal succeeds.
  • Everyone found stays in the role's durable pool, grouped by the day they were found, so a later search never re-surfaces someone you already passed on.
  • Overnight scouting re-scans your open roles and leaves a "While you were away" shortlist waiting at login; taste memory re-ranks future searches toward the profiles you shortlist.
  • How AI candidate sourcing software works
  • Free Boolean search string generator - or skip the string and describe the role in plain English.

Frequently Asked Questions

What are the best interview questions to ask candidates?

The best interview questions to ask candidates are behavioral and specific: questions that make candidates reconstruct real decisions with constraints, trade-offs, and outcomes. Questions like 'walk me through the work you're proudest of' or 'what decision did you get wrong' predict performance far better than hypotheticals or strengths-and-weaknesses questions, because real memories have detail that invention doesn't.

How many questions should I ask in a candidate interview?

Six to ten substantive questions in a 30-45 minute interview, with two or three follow-ups on each. Depth beats coverage: 3 questions probed hard reveal more than twelve answered at surface level. Keep the core set identical across candidates so scores are comparable.

How do you find candidates to interview in the first place?

You source them: search the open market for people who match the role and make the first contact, instead of waiting for applications. Most qualified people are employed elsewhere and not looking, so they never see a posting. The Cognitive searches ~900M profiles from a role written in plain English, shows tenure in seat and open-to-work status on each candidate, and reveals a verified email or a direct phone number only for the ones you keep - charged only when the reveal succeeds.

What is the difference between a phone screen and a full interview?

Depth, not subject. A phone screen is a short filter - motivation, availability, compensation range, a first read on the core competency - meant to decide who is worth a full interview. The full interview is the assessment: competency by competency, with follow-ups that push past the rehearsed version of each answer. Both should score against the same criteria, or the screen is just an extra call.

What is AI sourcing, and how is it different from Boolean search?

Boolean search matches text: a string of titles and skills joined with AND, OR and NOT returns profiles that contain those words. It is precise, brittle, and silent about what it missed - every variant title you did not think of is a candidate you never see. AI sourcing reads the role instead and weighs each profile against the whole requirement, so people who described the same experience in different words still surface, and the string never has to be rewritten. Because that is a judgment rather than a match, it needs to be inspectable: filters derived from the role that you can see and correct, and a written "Why them?" on every result.

What questions should you not ask candidates?

Avoid questions about protected characteristics (age, family plans, religion, health, national origin), puzzle questions with no job relevance, and anything you wouldn't score consistently. Every question should map to a competency you've defined for the role - if you can't say what a strong answer looks like, don't ask it.

Interview questions for other roles

Interview Questions by Role · AI Interview Question Generator · What Is a Structured Interview? · AI Candidate Sourcing Tool

Last updated