Ask These Questions Before You Interview Anyone
The questions that determine whether your next hire works aren't the ones you ask candidates. They're the ones you ask yourself — before the first interview begins.
There's a version of hiring preparation that most people do: review the resume, think of a few questions to ask, maybe look up the candidate on LinkedIn. Five minutes before the interview, you're ready.
And then you spend an hour in a conversation that feels productive — they answered your questions, you answered theirs — and you walk out with an impression but not much else.
The problem isn't the interview. It's that the interview was the first time you formally thought about what you were actually trying to find out.
The questions that determine whether your next hire works are not the questions you ask candidates. They're the questions you need to answer yourself — about the role, the team, and what success actually looks like — before the first interview begins. Getting those answers right makes the interview almost secondary. Getting them wrong means no amount of interview skill compensates.
Here are the ones that matter most.
"What does success look like at 90 days — specifically?"
Not in general. Not "they're settled in and contributing." Specifically.
This is the hardest question on the list because it requires you to think concretely about an outcome you usually evaluate only in retrospect. Three months in, what would make you say, without hesitation, that this hire worked?
For a customer service role, it might be: they handle the morning rush without needing to check in with a manager, they've learned the team's shortcuts and informal processes on their own, and customer complaints about their interactions are below the team average.
For an administrative role: they're proactively managing the calendar without reminders, the owner has stopped following up on tasks they've delegated, and the systems they were handed are running without intervention.
The specifics matter because they become your evaluation criteria. When you know what 90-day success looks like, you can design your interview to surface whether a candidate is likely to get there. Without it, you're evaluating impressions and hoping they translate.
"What would someone do in the first week that would frustrate your team?"
This question surfaces something most hiring managers know intuitively but rarely articulate: the specific friction patterns that make someone a bad fit for your particular team, regardless of their general competence.
These patterns are usually consistent. A team that moves fast and communicates informally finds it exhausting to work with someone who needs formal processes and regular check-ins. A team that expects people to take initiative is frustrated by someone who waits to be told what to do. A team built around quiet, focused work doesn't gel with someone who needs constant interaction to stay engaged.
None of these are flaws in the person. They're mismatches. And mismatches are easier to identify before the hire than to manage after it.
When you answer this question honestly — even just for yourself — you know what to listen for in interviews. The candidate who describes their ideal working environment as "structured, with regular feedback and clear processes" is telling you something important if your team is the opposite. That's not a red flag about their character. It's useful information about fit.
"How much autonomy does this role actually require from day one?"
Not how much autonomy would be ideal. How much does the role functionally demand — in the first thirty days, specifically?
This matters more than most hiring managers realize because it changes what you're screening for fundamentally.
A role that requires someone to operate independently from week one, making judgment calls without supervision, is a completely different hire than a role with structured onboarding, clear procedures, and a manager available to answer questions. The first requires someone who is already comfortable with ambiguity and self-direction. The second can absorb someone who needs more initial guidance.
Both can be excellent hires — in the right role. The mismatch happens when you hire someone who needs structure into a role that doesn't provide it, or someone who chafes under close management into a role that requires it.
Answering this question before you start interviewing lets you test for the right thing. Instead of "do they seem capable," you're asking "do they operate at the autonomy level this role actually requires."
"What has failure looked like in this role before?"
If you've had someone in this position before, you probably have a clear sense of what went wrong. If it's a new role, you can usually extrapolate from adjacent hires or from the conditions of the work itself.
The pattern of failure is usually more specific than it sounds. It's not "they weren't a good fit." It's: they asked for clarification on the same tasks repeatedly after being shown once. They needed more reassurance than the team had capacity to give. They shut down under pressure instead of making a reasonable call. They were technically capable but couldn't match the pace.
When you know the specific failure pattern, you can design questions to surface whether it's present in a candidate before you hire them. That doesn't mean disqualifying anyone who shares certain characteristics. It means listening for how they describe the way they handle exactly the situations you already know are hard in this role.
"What does this team actually need — not what do I want them to be?"
This one is harder to answer honestly.
Every hiring manager has a version of the ideal employee that's partly based on reality and partly based on who they'd like to be working with. Someone low-maintenance who integrates quickly, communicates proactively, and doesn't need much management. That's not a candidate profile. That's a fantasy.
The more useful question is: what does the team actually need right now? Not in general — from this specific hire.
If the team is strong technically but tends toward groupthink, you need someone who will push back. If the team moves fast but misses details, you need someone with a different pace. If the team is collaborative but has one role that requires independent judgment, you need someone who can operate autonomously even in a collaborative culture.
Answering this honestly sometimes means hiring someone who complements the team's weaknesses rather than matching its strengths — which is a harder case to make in an interview room, but a better hire in practice.
Using the answers
These questions aren't a checklist to complete and file away. They're inputs to the interview process.
Your answer to "what does 90-day success look like" becomes the standard against which you evaluate every candidate. Your answer to "what would frustrate the team" becomes what you listen for when candidates describe their preferred working environment. Your answer to "what has failure looked like" becomes the scenario you put in your most important interview question.
When you do this work before you start talking to candidates, the interview becomes a structured information-gathering exercise rather than a gut-feel conversation. You're not seeing who seems impressive. You're testing whether each candidate fits the specific picture you've defined.
This is what TeamSyncAI is built around. It walks you through these questions in a guided process, then uses your answers to generate a complete interview blueprint — questions, evaluation criteria, and follow-up probes — calibrated to exactly what you've described. The five minutes you spend answering them does more for the quality of your hire than an extra hour of interviewing would.