Interview Questions to Ask Candidates: Use With Care

Blog image

Hey — quick honesty up front. I mostly write for the person sweating in the candidate's chair, not the one holding the clipboard. But I've sat on the hiring side too, and I've watched interviewers ask questions that were unfair, useless, or quietly illegal without meaning to. So if you're the one choosing interview questions to ask candidates, here's a careful, practical take — with a clear line about where you should stop reading me and go talk to HR or legal instead.

Why This Topic Is Weaker for Macaron

Blog image

Before the practical part, a straight admission about where this sits — because I'd rather be honest than pretend this is our home turf.

Employer-side intent

Most of what I write is for job seekers, the people being interviewed. This one flips the table: it's for the interviewer. That's a different job with different responsibilities, and it's worth naming so you weigh my employer-side advice accordingly.

HR process fit

Choosing candidate questions well is really an HR-process problem — consistency, documentation, fairness across a whole pipeline — more than a clever-question problem. The hard part isn't the questions; it's the process around them, and that usually belongs with your HR function.

Lower personal-agent bridge

And honestly, this isn't Macaron's lane. Macaron is built for an individual navigating their own career, not for running a hiring pipeline. So take what follows as fair, general guidance, not a product pitch — because there isn't one here.

If Published, Keep It Practical and Fair

If you're going to ask candidates questions, two principles carry most of the weight: make them relevant to the role, and apply them consistently.

Role-relevant questions

Every question should map to something the job actually requires. "Walk me through how you'd handle [a real scenario from this role]" beats a clever brain-teaser that tests nothing relevant. If you can't name which job requirement a question probes, cut it.

Consistent criteria

Blog image

Ask the core questions the same way, in the same order, scored against the same criteria, for every candidate. This is the heart of a structured interview, and the U.S. government's hiring guidance describes structured interviews as a more reliable, valid way to assess candidates, precisely because everyone gets the same questions and the same rating scale. Consistency is also one important defense against bias.

Avoiding personal or sensitive topics

Blog image

Steer clear of anything about a candidate's personal life that isn't job-related — family, age, health, religion, and similar areas. Beyond being unfair, some of these stray into legally protected territory. The EEOC's guidance on pre-employment inquiries is a useful starting reference, but see the legal section below before you rely on anything.

Question Categories Employers Often Need

Most useful interview questions to ask candidates fall into a few role-relevant buckets. These are the strategic categories, not a script to read aloud.

Experience

Ask about real past work relevant to the role. "Tell me about a project like the ones you'd do here — what did you actually own?" gets you evidence rather than claims, and it works well as a screening interview question early in the process.

Problem solving

Give a realistic scenario from the actual job and ask how they'd approach it. You're testing judgment applied to your problems, not trivia, so keep it close to real work instead of abstract puzzles.

Collaboration

Blog image

Ask how they've worked with others — handled disagreement, shared credit, dealt with a difficult stakeholder. Most roles fail on people, not tasks, so this matters more than interviewers tend to assume.

Motivation

Ask why this role and this company, and listen for something specific rather than a generic answer. These hiring manager interview questions tell you about fit and staying power, not just raw capability.

What Requires Legal or HR Review

This is the part where I stop giving advice and hand you off. I'm not a lawyer, employment law varies by country, state, and city, and getting this wrong carries real consequences. Before you finalize any question set, run it past your HR function or an employment attorney.

Local hiring rules

Hiring rules differ by jurisdiction — some places restrict questions about salary history, criminal records, or other areas that are fine elsewhere. What's allowed in one city may not be in the next, so only someone who knows your local rules can actually clear your questions.

Protected characteristics

Many characteristics are legally protected, and questions that touch them — even indirectly, even well-meant — can create liability. The EEOC outlines protected categories at the U.S. federal level, but your specific obligations depend on where you operate and your headcount. This is HR and legal territory, not something to eyeball.

Documentation requirements

Consistent, documented interviews aren't just fairer; they can help support and defend your process if a hiring decision is ever questioned. What you need to record, and how, is another thing to confirm with HR rather than invent your own standard for.

If you're building an interview soon, here's the one move worth doing first — before you write a single question: list the three or four things the role genuinely requires, and make every question map to one of them. Questions that don't map to a real requirement are usually the ones that turn out unfair, useless, or risky. Then take the set to HR before you use it.

One honest note to close: Macaron isn't a hiring tool, and we won't pretend it is. It's built for the person on the other side of your table — the candidate managing their own career. If that's also you when you're not the one interviewing, that's where we help. For the hiring side, your best tools stay a fair, consistent process and a good HR partner.

FAQ

What makes certain candidate questions potentially unfair or risky?

Two things: the question isn't related to the job, or it touches a candidate's personal or protected characteristics. A question that doesn't map to a real role requirement invites bias, because you end up judging on gut feel; a question about family, age, health, or similar can stray into legally protected territory. The fix is to keep every question tied to the work and consistent across candidates — and to confirm anything you're unsure about with HR or legal.

When should interview questions be standardized across candidates?

Effectively always, for the questions that feed into your decision. Asking every candidate the same core questions, in the same way, scored on the same criteria, is what makes your comparison fair and your process defensible. You can still leave room for natural follow-ups, but the backbone should be consistent — that consistency is the entire point of a structured interview.

What should small teams review with HR or legal before using new questions?

Anything touching salary history, criminal background, age, disability, or other sensitive areas, plus your local jurisdiction's specific rules, which vary widely. Small teams often skip this because they don't have a big HR department, but the obligations still apply — and the exposure can be worse without a process. If you don't have in-house HR, a short consultation with an employment attorney before you finalize a question set is worth it. This isn't legal advice; it's a nudge to go get some.