Interview Questions You Should Never Ask (And Why)

You're forty minutes into an interview, it's going well, and you ask something friendly to break the ice: "So, do you have kids? Must be tough juggling that with a new job." The candidate answers politely. Nothing happens. Except now you've asked a question that has nothing to do with whether she can do the job, and everything to do with an assumption about who does childcare.

Most hiring managers who ask a risky question aren't trying to discriminate. They're making conversation, or trying to solve a real worry — will this person stick around, can they handle the hours, will they fit in — and reaching for the fastest question that comes to mind. The problem is the fastest question usually asks about a personal characteristic instead of the thing you actually need to know.

Employment law on this varies by country, and Malaysia, the Philippines, the UAE, South Africa and Singapore each handle protected categories differently. This isn't legal advice — check your local labour law or a lawyer if you're unsure. But the underlying judgement call is the same everywhere: if a question is about a personal trait rather than the work, you're taking on risk for no gain. Below are the categories that come up most, why people ask them, and what to ask instead.

Age, graduation year, "how many more years until retirement"

Why it gets asked: worry about stamina, learning new systems, or how long someone will stay.

Ask instead: "This role changes tools every year or two — walk me through the last time you had to learn a new system from scratch." That question surfaces exactly the thing you were worried about, without touching age at all.

Marital status, whether they plan to have children

Why it gets asked: worry about maternity leave, relocation flexibility, or availability for overtime.

Ask instead: "This role sometimes needs travel on short notice / evening calls with our overseas team — is that workable for you?" Ask every candidate the same version of this question, regardless of gender or apparent age. The scheduling need is real; the guess about who has family obligations is not yours to make.

Religion, ethnicity, national origin

Why it gets asked: genuine curiosity, or a worry about visa status disguised as small talk.

Ask instead: if the real question is work authorisation — "Are you legally able to work in [country] for this role, and do you need any sponsorship?" — ask that directly and ask it of everyone. Skip the guessing games about where a name or accent comes from.

Health, disability, past illness

Why it gets asked: worry about absence, or whether someone can physically do the job.

Ask instead: describe the actual physical or attendance requirement and ask if they can meet it. "This role requires standing for most of an 8-hour shift — is that something you can do, with or without accommodation?" That's a functional question about the job, not a diagnosis question about the person. If the candidate needs an accommodation, that's a separate conversation to have once you're both keen — most things are solvable and asking about them upfront usually just filters out capable people early.

Salary history

Why it gets asked: to gauge what number to offer, or check they're not wildly overqualified.

Ask instead: "What's your expected range for this role?" Past salary tells you what someone was underpaid or overpaid before — not what the job in front of you is worth. Anchoring your offer to their history just carries old inequities forward.

Criminal record, in detail

Why it gets asked: genuine risk concerns for roles handling money, vulnerable people, or sensitive data.

Ask instead: if a background check is genuinely relevant to the role, say so plainly and run a formal, consistent check as part of the process — the same check, on the same terms, for every finalist. Asking about it casually in an interview, based on a hunch about one candidate and not another, is where the real risk sits.

The pattern underneath all of this

Every risky question above is really a stand-in for a work-related worry: can they do the physical task, are they legally able to work here, can they meet the schedule, is the salary realistic. The fix is almost always the same — ask about the job requirement directly, ask it of every candidate the same way, and drop the personal detail you were using as a shortcut.

One more thing worth naming honestly: interviews are where most of these questions creep in because they're conversational and improvised. A structured scorecard, written before the interview starts, makes it much harder to drift into personal territory mid-conversation — you're reading from a list of job-related questions instead of reacting to whoever's sitting across from you. If you're testing a specific skill directly — can this person actually do the spreadsheet work, write the email, solve the technical problem — you also remove a lot of the temptation to guess at capability through age, background or health. Tools like AssessFit exist for exactly that reason: a skills test answers "can they do it" without you having to ask around the edges.

None of this means interviews have to be cold or robotic. You can still ask about someone's last job, why they're leaving, what they're proud of. The line isn't warmth versus formality — it's whether the question is about the work or about the person's private life. When in doubt, ask yourself: would I ask this exact question, in this exact way, of every single candidate for this role? If the honest answer is no, that's usually the question to cut.