15 Reference Check Questions to Avoid (And What to Ask Instead)

Copied templates still open with "Are they a team player?" and "Is there anything I should know?" Those reference check questions to avoid waste referee time, invite gossip, or create a discrimination record. This guide lists fifteen bad reference check questions, explains the reference questions mistakes behind each one, and gives a replacement you can send the same day.

You will get a filter for wasteful, leading, and risky prompts, fifteen replacements tied to observed work, and a simple way to score thin answers.

Why reference check questions to avoid still sit on templates

Most damage comes from inherited forms, "culture" prompts, and phone calls that wander. A Dallas store lead who asks "do they get along with everyone?" thinks they are testing collaboration. A Manchester manager who asks "is there anything I should know?" thinks they are being thorough. Both collect adjectives or protected detail you cannot score.

Reference check questions to avoid fall into three buckets. Some waste time because a referee can answer with a slogan. Some produce a number or a yes that has no example behind it. Some create legal risk because the only honest answer names health, family status, or another protected topic.

Keep prohibited identity probes on a separate removal list. For the discrimination patterns that commonly sit off-limits, use the filter for questions that invite protected characteristics. This article covers the everyday prompts that still fail even when they are not obviously unlawful.

How to spot a wasteful or risky prompt

Ask whether a referee can answer without a date, a deliverable, or a duty from the job you posted. If they can, rewrite it.

Ask whether the wording forces a compliment or a comparison with no scale. "Are they the best person you have ever managed?" is a trap, not a measure.

Ask whether the prompt invites a category you should not store. If the referee can only answer by naming children, illness, or "fit" as a personality label, stop.

A Vancouver clinic that needs evening coverage should describe the published roster. A Lyon warehouse should ask about the published lifting duty and incidents on shift, not about a "bad back."

Fifteen reference check questions to avoid, with replacements

Use the same replacements for every finalist on the same role. Change the follow-up example, not the core prompt. Invite "I did not observe that" as a valid answer.

Generic praise and slogans (1 to 5)

1. Avoid: "Are they a good team player?" Ask instead: "Describe a time they had to finish work that depended on another team. What did they do in the first week, and what was still unfinished?"

2. Avoid: "Would you hire them again?" with no follow-up. Ask instead: "If you hired them tomorrow for this same scope, what would you give them in the first thirty days, and what coaching would you fund?"

3. Avoid: "Are they honest, reliable, and hardworking?" Ask instead: "Give an example where they had to report a miss or a risk. What did they do, and who did they tell?"

4. Avoid: "What is their biggest weakness?" Ask instead: "What would you warn a new manager about working with this person, even if you still recommend them?"

5. Avoid: "Did they get along with everyone?" Ask instead: "Describe a disagreement with a teammate or stakeholder. How did they move the work forward?"

Slogan answers are the most common reference questions mistakes. "Great team player" is not evidence. A named handoff, a date, and a leftover task are.

Thin scores, hypotheticals, and open dumps (6 to 10)

6. Avoid: "How is their culture fit?" Ask instead: "How did they handle a published rule or client standard they disagreed with?"

7. Avoid: "Rate them from one to ten" with no defined scale. Ask instead: "Which parts of the role did they own day to day, and which parts did they only cover as backup?"

8. Avoid: "Can they handle stress?" Ask instead: "Describe a week when volume jumped. What did you observe in quality, and how did they communicate status?"

9. Avoid: "Would their old team say the same thing?" Ask instead: add a second referee who saw different work. Do not ask one person to speak for a group they did not manage.

10. Avoid: "Is there anything else I should know?" Ask instead: "Is there a job-related example we have not covered that would change how you staff this person in the first month?"

Open dumps and forced scores are bad reference check questions because they look complete in a spreadsheet. They hide the missing example. A Utrecht scale-up that collected "nine out of ten" on every finalist still could not explain who owned month-end versus who only backed it up.

Legal risk, gossip, and comparisons you cannot defend (11 to 15)

11. Avoid: "Were they late a lot?" or "Do they have attendance issues?" without a published rule. Ask instead: "Against the published roster or attendance rules, what did you observe, and how did they communicate exceptions?" Do not ask why someone was absent if the reason is medical or family status.

12. Avoid: "What did you pay them?" or "What should we offer?" Ask instead: "What budget, team size, or book of work did they actually own?" Compensation history is not performance evidence, and several markets restrict salary-history questions.

13. Avoid: "Why did they really leave?" framed as gossip. Ask instead: "What was the documented reason for leaving, and what work was in progress when they exited?"

14. Avoid: "Are they the best person you have ever managed?" Ask instead: "Compared with peers in the same role, where did they sit on delivery quality, and what evidence supports that?"

15. Avoid: family, health, or "can they work late because of the kids?" Ask instead: describe the published hours and ask whether the person met comparable hours in the last role. Identity and family probes belong on the removal list in questions that commonly sit off-limits in major markets.

Item 15 is the line where a time-waster becomes a claim. If a referee volunteers protected detail, thank them, return to observed work, and keep that detail out of the decision note.

How to replace reference check questions to avoid without losing signal

Freeze eight to twelve replacements per referee, not a forty-item dump. Put ownership and a concrete incident first. Put conflict, recovery, and the "warn a new manager" item later.

Tell referees they may skip prompts they did not see. Honesty beats an invented culture story.

If you want a longer library after you remove the fifteen above, start from past-focused prompts that force examples and time frames and keep only the blocks that match the role.

A Boston professional-services firm that froze replacements 1, 3, and 8 compared two associate finalists in one sitting. A Wellington retailer that kept "anything I should know?" collected a childcare comment it then had to exclude.

How to score answers so replacements stay comparable

Use a simple rubric per prompt: strong example with a date or duty, mixed example with a clear limit, or not observed. Do not average a glowing peer and a cautious manager into one "culture" number.

Watch for stacked gaps: no ownership, no recovery story, and a referee who never reviewed the work. One thin answer is a probe. Three thin answers are a reason to add a referee or pause the offer.

Examples across hiring markets

In Austin, a construction firm replaced "can they handle stress?" with the volume-week prompt. Both referees described the same storm-week backlog and how the candidate reordered jobs.

In Dublin, a software team dropped "culture fit" and asked about a published coding standard the candidate disagreed with. The peer praised speed. The tech lead said reviews were thin, so the panel added a third referee.

In Toronto, a nonprofit put the documented-exit prompt first after a prior hire left mid-grant. In Auckland, a public-sector desk banned salary-history questions and asked about caseload instead. In Berlin, a hardware company stored scored replacements, not a chat transcript of "anything else."

FAQ

How many replacements should we send per referee?

Eight to twelve core prompts is a practical range for completion. Treat the fifteen-item list as a removal and rewrite library, not a requirement to fire every item at every contact.

Can we keep a one-to-ten score if we define the scale?

A defined scale can sit beside an example. A number alone is still a reference questions mistakes pattern. Require the incident before you record the score.

What if the referee only answers the old slogan questions?

Send the replacements in writing and ask them to skip items they did not observe. If they still return adjectives only, add a referee who saw the work.

Closing

Treat reference check questions to avoid as a frozen removal list. Drop slogans, open dumps, forced tens, gossip about exit, and any prompt that needs a protected characteristic to answer. Ask for ownership, a dated incident, and what happened next so bad reference check questions do not fill the file with praise you cannot reuse.

Avoid risky questions automatically with a reviewed library on the HiveRef home page, or compare plans and included checks when you want the same replacements on every finalist.