Interview Questions to Ask Candidates, and What a Good Answer Sounds Like

Interview Questions to Ask Candidates, and What a Good Answer Sounds Like

Mercedes Gordo runs delivery and customer success at Nova and spent two years at LinkedIn in Dublin. Her view on interview question lists: they tell you what to ask and leave you alone for the part that actually matters.

Updated 7 min read

Most lists of interview questions have the same problem. They tell you what to ask and then leave you alone for the part that decides the hire, which is knowing what you just heard.

A question on its own is the easy third of the job. The useful unit has three parts: the question, what a strong answer demonstrates, and the red flag underneath it. Write those three next to each other and the interview stops depending on how sharp you happen to feel that afternoon.

Here’s the structure we use, and what goes in each block.

Start by reading the person, and expect rehearsed answers

Two or three opening questions, no more. How they’d describe themselves professionally and what their manager would say about them. Why this role, and why they’re looking now. What their next step needs to include for them to call it a good move.

You’ll get polished answers to all three, and that’s fine, because the value of this block isn’t the answer. It’s having something to cross-check an hour later when they’re describing a real situation under pressure. The gap between how someone describes themselves and how they describe a specific Tuesday is where the signal is.

Do this: keep it to three questions. This is a read, not a questionnaire, and every minute here is a minute not spent on the part that’s hard to fake.

The career walkthrough, and the question most interviews skip

Ask where they’re coming from and where they’re going, then ask for the experience most relevant to this role. Standard so far.

Then ask the one that isn’t:

“Beyond the obvious parts of your experience, what else have you done, your own projects, initiatives, side projects, in or outside work, that you think adds up for this role? The things that wouldn’t come up if we only talked about your usual track record.”

That question exists because of the person who built the internal tool their whole team now runs on, or who leads a technical community, and who will never mention it unless asked, because it wasn’t a job title.

✅ What a strong answer shows: a coherent narrative with progression. They surface what’s relevant without being prompted, explain job changes naturally, and connect even the non-obvious work to what the role needs.

🚩 The red flag: a disjointed or inflated story, no ability to separate the relevant from the incidental, and in particular being unable to connect their own experience to the role when asked directly.

⚠️ One boundary on that question, and it matters: the door to “outside work” is for projects and initiatives, not for private life. If a candidate brings up family, health, beliefs or origin, you don’t evaluate it and you don’t follow it. Only what’s relevant to the role counts.

Do this: a non-linear career is not a red flag. It’s a question. Ask it before you conclude anything.

The technical block: scenarios, not definitions

Pick three to six technical competencies the role genuinely requires, and give each one or two questions. At least one has to be a real scenario that person will face in the job, not textbook theory.

The difference is stark in practice. “What’s forecast bias?” gets you a definition anyone can recite. This gets you something else:

“A forecast lands with a 30% bias in one product family. How do you diagnose it, and what do you do?”

For each one, write down the two halves before the interview:

✅ Desirable: what a strong answer demonstrates. The concepts they reach for, how they frame the problem, the tools they mention unprompted.

🚩 Red flag: what gives away someone out of their depth. Vagueness where specifics should be, no ownership of the decision, conceptual mistakes.

Writing those two in advance is what stops you grading on fluency. Confident people describe weak work convincingly, and quiet people describe excellent work badly.

Do this: anchor the desirable answer in what you actually know about the role. If you don’t have enough context to say what good looks like, say so, and don’t invent an industry standard to fill the gap.

The behavioral block: a real situation, never an opinion

Choose the soft skills that matter for this role, not a universal list. Ownership, stakeholder management, communication under pressure, influence without authority if the job needs it.

Then ask each one in STAR format, which just means asking for a real situation instead of an opinion:

“Tell me about a time you had to [the concrete situation tied to the competency]. What did you do, and how did it end?”

✅ Desirable: a clear personal action, a measurable outcome, and something they took from it.

🚩 Red flag: the whole story told in “we” with no sign of what they personally did, no result, blame pointed outward, or an example so vague it may not have happened.

That first red flag is the most common one and the most useful. Plenty of people describe a team’s achievement in perfect detail and never once say what their own hands did.

Do this: when you get “we”, ask “and what was your part in that?” The answer to the follow-up is worth more than the original answer.

Calibrate for seniority, or the bar moves on its own

The same question has a different passing grade for a mid and a senior, and if you don’t write that down you’ll drift.

What rises with level: scope, autonomy in ambiguity, influence without authority, and whether they can carry a decision without being handed the frame. If it matters for the role, add one or two questions that specifically separate the levels.

Do this: write the senior bar and the mid bar as separate lines before you interview anyone. Deciding it afterwards, with a person in front of you, is how a process ends up with two different standards.

What to do with the answers

You don’t need a numeric score for a single interviewer. A guide where every question already carries its desirable answer and its red flags is a rubric. That’s the point of writing them down.

When you do write up the debrief, three rules keep it honest:

  • Rate against the role, never against the last candidate. A brilliant profile on Tuesday shouldn’t raise the bar for Wednesday.
  • Only cited evidence. Every judgment points at something they actually said.
  • No signal is not a bad score. If a competency never came up, it’s marked not assessed. Scoring it from a guess is exactly how a structured interview turns back into a vibe.

A scorecard with weighted competencies earns its place once several people interview the same candidate, because then you need everyone measuring the same things in the same proportion. For one interviewer and one conversation, the guide is enough.

Where this stops working

An interview guide makes a good conversation out of a good shortlist. It can’t rescue a bad one.

If the five people on the list were found by matching keywords on a profile, the best structured interview in the world will tell you precisely which of the five mediocre fits is least mediocre. That’s a sourcing problem wearing an interviewing costume, and it’s why Nova Recruiter ranks 800M+ profiles by the quality of someone’s experience and education rather than by how well they described themselves, with a curated network of 25,000+ assessed professionals underneath.

The part that doesn’t change: the tool narrows the list, and a person runs the conversation. Every one of the eleven free skills behind this guide is built on the same rule, and it’s the right one.

For any team where more than one person interviews, writing the desirable answer and the red flag next to each question is the highest-return hour you’ll spend this quarter. If you’re a solo recruiter running a handful of processes, the career walkthrough question and the “what was your part in that” follow-up will carry most of the benefit on their own.

Frequently asked questions

What interview questions should I ask candidates?

In this order: two or three opening questions to read the person, one on their career path and relevant experience, three to six technical questions tied to competencies the role actually needs, a behavioral question in STAR format for each of the soft skills that matter in this specific job, and a close that leaves room for their questions. What makes it work isn't the list. It's that each substantive question comes with what a strong answer demonstrates and the red flag to watch for underneath.

How many questions should an interview have?

Fewer than most guides suggest. Three to six technical competencies with one or two questions each, plus two or three behavioral ones, is already a full hour done properly. Padding the list to twenty questions means every answer gets four minutes and nothing gets probed. The follow-up is where the signal is.

What is a STAR interview question?

A question that asks for a real situation rather than an opinion. Instead of asking whether someone handles pressure well, you ask them to describe a time they had to deliver under pressure, what they did, and how it ended. The format gets its name from situation, task, action and result. The reason it works is that opinions are easy to produce and specific past situations are not.

What are red flags in a job interview?

In an answer: telling the story in we without ever naming what they personally did, no result or outcome, blaming others for everything that went wrong, a vague or invented example, or being unable to connect their experience to what the role requires when asked directly. What is not a red flag by itself: a non-linear career path, a gap, or a job change. Those are questions to ask, not conclusions to draw.

Should I use the same questions for every candidate?

For the substantive blocks, yes. Same competencies and same base questions for everyone in the process, because the moment the questions change per candidate you can no longer compare the answers, and you have no defense if someone asks how you decided. Follow-up probes naturally differ, since you're digging into what each person actually said.

Do I need a scorecard as well as a guide?

A guide where every question carries its desirable answer and its red flags is already a rubric, which is enough for a single interviewer. A scorecard earns its place when several people interview the same candidate, because then you need everyone scoring the same competencies with the same weights, and evidence attached to each score.

Sources and method

The structure described here is the interview guide method from the Recruiter Assistant skill, built and published by Nova's Customer Success team, with the rubric detail from the Scoring Model skill.

Mercedes Gordo
Mercedes Gordo

Head of Delivery and Customer Success

Mercedes Gordo is Head of Delivery and Customer Success at Nova. Mercedes spent two years at LinkedIn in Dublin as a relationship manager and account director, and previously ran Customer Alliance's Spanish operation.

Connect on LinkedIn →
Sourcing and outreach How to Screen CVs Without Throwing Away Good Candidates Sourcing and outreach The Interview Scorecard: How to Score Candidates on the Same Yardstick