How to Interview Candidates as a Manager (Step by Step)
A guide to interviewing candidates as a manager: define the role, write structured questions, score fairly, and use AI without handing it the decision.
For Executives, Sales and Managers

How do you interview candidates as a manager?
Decide what the job requires before you meet anyone, ask every candidate the same set of questions tied to those requirements, take notes on what they actually said, and score each answer against a written scale before you talk to anyone else about them. That process is called a structured interview. It beats a free-flowing chat because it keeps you from hiring the person you simply liked talking to. AI can help you draft the questions and tidy your notes. It should not make the decision.
TL;DR
- Write the scorecard first. List three to five outcomes the person must deliver and the skills behind them, then judge every candidate against that list, not against a feeling.
- Ask everyone the same core questions in the same order, so you are comparing answers rather than conversations.
- Ask for specific past examples and live work, not opinions. "Tell me about a time" and a small work sample tell you far more than "What's your biggest weakness?"
- Score each answer on a written scale right after the interview, before you hear anyone else's opinion, so first impressions and group pressure do less damage.
- Use AI for drafting and organizing, such as question banks, interview guides and note cleanup. Do not use it to rank or reject people.
- Stay away from protected topics such as age, family plans, health, religion and origin. Your HR team can tell you exactly what applies where you work.
Why do managers get interviewing wrong?
Most managers are promoted for being good at the work, then asked to hire with no training. So they do what feels natural: read the resume, chat for 30 minutes, and go with their gut. Three things go wrong.
- You hire for likability. A candidate who shares your background, humor or alma mater feels like a fit. That feeling is not evidence they can do the job.
- Every candidate gets a different interview. One person gets a deep technical conversation, another gets small talk. You cannot compare them fairly.
- You decide in the first few minutes and spend the rest of the interview looking for proof.
The fix is not to become a professional recruiter. It is a small amount of structure, done before and after the conversation.
What should you do before the interview?
Preparation is where most of the quality comes from. Block an hour for it.
Step 1. Write down what the job actually is. Not the posting. Answer this: if this person is great, what will be true twelve months from now? Pick three to five outcomes. For a first hire on a sales team, that might be "builds and works a pipeline of its own accounts without daily direction." For an analyst: "delivers the monthly report accurately and flags problems before I find them."
Step 2. Turn outcomes into criteria. Each outcome needs two or three skills or behaviors behind it. Keep the list short. If everything is a must-have, nothing is.
Step 3. Build a scorecard. Copy this and fill it in before you open a single resume.
| Criterion | What good looks like | What weak looks like | Question(s) | Score (1-4) | Evidence (their words) |
|---|---|---|---|---|---|
| Example: Owns problems | Names a time they found and fixed something without being asked | Describes only tasks assigned to them | "Tell me about a problem you spotted that nobody asked you to fix." | ||
| Example: Communicates clearly | Explains a complex topic in plain words, checks understanding | Vague, jargon-heavy, loses the thread | "Explain a project you worked on as if I had no background." | ||
| Example: Handles pushback | Listens, adjusts, keeps the relationship | Gets defensive or caves immediately | "Tell me about a disagreement with a colleague or client and how it ended." | ||
| Example: Role-specific skill | Defined by you per role | Defined by you per role | Work sample or technical question |
Use a four-point scale with no middle. A middle score lets everyone park on "average" and avoid a decision. Define it in one line each: 1 = no evidence, 2 = some evidence but weak, 3 = solid evidence, 4 = strong, specific evidence.
Step 4. Agree on who interviews whom. If several people interview, give each a different set of criteria. Three people asking the same "why do you want this job?" question wastes the candidate's time and your information.
How do you write interview questions that predict job performance?
Good questions ask about behavior you can verify, not intentions you cannot. Use three types.
Behavioral questions ask about the past. "Tell me about a time you had to deliver something with a deadline you thought was unrealistic. What happened?" Past behavior is the best evidence you will get in an hour.
Situational questions ask what they would do in a realistic scenario from your team. "A client emails at 5 p.m. Friday saying the report is wrong. Walk me through the next two hours." These work well for people with little experience, such as someone in a first job, who may not have many past examples.
Work samples ask them to do a small piece of the real job. A recruiter might critique a weak job post. An accountant might reconcile a short, messy set of entries. A marketer might outline a campaign for a one-paragraph brief. Keep it under an hour, tell them in advance, and pay for anything longer than that. It is the closest thing to seeing the job before hiring.
A starter question set
You can adapt these to almost any role:
- Walk me through your most relevant project. What was your part, specifically?
- Tell me about something you got wrong at work. What did you change afterward?
- Describe a time you had to learn something quickly to get a job done.
- Tell me about a time you disagreed with your manager. What did you do?
- What would you want to understand in your first 30 days here?
- What kind of manager helps you do your best work, and what kind makes it harder?
Follow-up questions are where the truth is
Candidates often give a polished first answer. Probe it:
- "What was your role versus the team's?"
- "What did you personally do?"
- "What was the result, and how do you know?"
- "What would you do differently?"
If a candidate says "we" for five minutes, ask what "I" did. A candidate who actually did the work can answer this easily.
Using AI to draft your questions
Paste this into a general AI assistant. Do not include real candidate names or confidential company details unless your company has approved the tool for that.
I'm a manager hiring my first [ROLE] for a team that [WHAT THE TEAM DOES].
The person will be successful if, within 12 months, they:
1. [OUTCOME 1]
2. [OUTCOME 2]
3. [OUTCOME 3]
Create a structured interview guide for a 45-minute interview:
- 5 behavioral questions and 2 situational questions, each tied to one
of the outcomes above
- For each question: what a strong answer includes, what a weak answer
sounds like, and 2 follow-up probes
- One 30-minute work sample appropriate to this role, with a short brief
I can hand the candidate
- Do not include questions about age, family, health, religion, national
origin, or anything else that is not job-related.
What to check in the answer: Cut any question that does not map to an outcome you listed. Rewrite anything that sounds like a trivia quiz. Make sure the "strong answer" descriptions reflect your workplace, not a generic one. AI tends to produce reasonable-sounding but generic criteria, and you know the job better than it does.
How should you run the interview itself?
A 45-minute interview has a simple shape. Use it for every candidate.
- Open (3 to 5 minutes). Greet them, explain the format, and say you will take notes. Telling them this removes the awkwardness of you typing while they talk.
- Core questions (25 to 30 minutes). Ask your planned questions in the same order. Use the follow-up probes. Stay quiet after they answer; silence often produces the best detail.
- Their questions (5 to 8 minutes). Pay attention to what they ask. Good questions about the work, the team and how success is measured are a real signal.
- Close (2 to 3 minutes). Tell them exactly what happens next and when. Then do it. Candidates remember managers who go silent.
A few habits that help:
- Talk less than you think you should. Aim for the candidate speaking about 70 to 80 percent of the time.
- Sell honestly, and later. Strong candidates are evaluating you too. Describe the job as it is, including the hard parts. Hiring someone who quits in three months is worse than losing a candidate who was never a match.
- Do not coach mid-answer. If you nod and say "great, exactly" after one answer, the next candidate does not get that help.
- Treat remote interviews the same way. Share your questions' structure, not a surprise. Judge answers, not video quality or home background.
How do you take notes and score candidates fairly?
This is the step most managers skip, and it matters most.
Write down what they said, not what you think of it. "Led migration of 40 accounts, cut onboarding time from two weeks to one, missed the first deadline because of a vendor delay" is evidence. "Seems sharp" is not.
Score right after the interview. Within 15 minutes, fill in the scorecard: a 1 to 4 for each criterion, with a line of evidence. Do it before you talk to anyone, check their LinkedIn again, or see another candidate.
Score separately before the debrief. If several people interviewed, each submits scores independently. Then meet. When people hear the most senior person's opinion first, everyone else tends to agree. Have the most senior person speak last.
In the debrief, discuss evidence, not impressions. Go criterion by criterion. Where scores differ by two or more points, ask each person what they heard. Often one interviewer asked a different question or missed something.
Check yourself for these biases:
- Similarity: "reminds me of me."
- Halo: one impressive thing colors everything else.
- Recency: the last candidate feels better because you remember them best.
- Confidence over competence: a smooth speaker is not necessarily a strong performer.
Using AI to clean up notes
After the interview, paste your own rough notes into an AI assistant and ask it to organize them. Again, follow your company's rules on what data can go into which tools.
Here are my raw notes from an interview for [ROLE]. Organize them under
these criteria: [LIST CRITERIA]. For each criterion, list only what the
candidate actually said or did, quoting my notes. Do not add anything
that isn't in my notes. Do not rate the candidate. Flag any criterion
where I have no evidence.
What to check: That nothing was added. AI sometimes fills gaps with plausible-sounding details. Compare the output to your notes line by line. The instruction not to rate matters: you want an organized record, and you want to do the judging yourself.
What questions should you never ask?
Rules differ by country and region, so confirm with your HR or legal team. As a general guide, avoid questions about:
- Age or birth year
- Marital status, children, or plans to have them
- Health, disability or medical history (you can describe the job's essential tasks and ask if they can perform them)
- Religion, race, ethnicity or national origin
- Pregnancy
- Sexual orientation or gender identity
- Current or past salary, in places where that is restricted
Small talk is where managers slip. "Do you have kids?" feels friendly and creates risk for you and unfair influence on your decision. If a candidate volunteers personal information, do not follow up on it and do not record it in your notes. Steer back to the job.
How can AI help with hiring, and where should it stay out?
AI is useful in the parts of hiring that are drafting and organizing. It is a bad fit for the parts that are judgment about people.
Good uses:
- Drafting a job description from your outcomes, which you then edit
- Building an interview guide and a work sample
- Preparing you for a specific interview: "Here is the resume. List five questions to probe the gaps in experience relevant to these criteria"
- Turning your raw notes into a clean, structured write-up
- Drafting polite, clear rejection and next-step emails you personalize
Poor uses:
- Scoring or ranking candidates. AI can reflect biases in the text it learned from, and it cannot verify what a candidate did. Some jurisdictions also regulate automated tools used in hiring decisions, so check with HR before using any software that screens people.
- Judging resumes by style. A polished resume often says more about who helped write it than who did the work.
- Pasting sensitive details. Candidate personal data belongs in your company's approved systems, not a random chatbot.
- Replacing the conversation. The interview exists so a human can assess another human.
Also remember that candidates use AI too. Resumes and take-home assignments may be heavily assisted. That is another reason to favor live conversation and follow-up probes: ask them to explain a decision, walk through how they would change their work sample, or tell you what went wrong.
What mistakes do first-time hiring managers make?
- Hiring to fill a seat quickly. A bad hire costs far more time than a delayed one.
- Only interviewing people who look like your last hire. Widen your pool before you start.
- Asking vague questions. "Tell me about yourself" gets a rehearsed speech. Replace it with a specific prompt about relevant work.
- Skipping references. Ask former managers specific questions: "What would you want me to know to manage them well?"
- Moving the bar mid-process. If you change criteria after meeting a charming candidate, you are rationalizing. Update the scorecard for everyone or stick with it.
- Leaving candidates in the dark. Respond promptly, even with a no.
Can I build my own interview scorecard tracker?
Yes, and for a first hire it is worth considering. Most managers end up with scorecards in documents, scores in emails and a spreadsheet nobody trusts. With Remy, you describe the tool in plain English: a form where each interviewer submits 1 to 4 scores and evidence for your criteria, hidden from other interviewers until everyone has submitted, then a debrief view that lines the scores up side by side. Remy builds it as a full-stack app with sign-in and role-based access, so only the people on the panel can see it. A typical initial build takes about an hour. Check with HR about where candidate data may be stored first.
Frequently Asked Questions
How long should an interview be?
Forty-five minutes to an hour works for most roles. That is enough for six or seven structured questions with follow-ups and time for the candidate's questions. For senior roles or those with a work sample, plan multiple shorter conversations rather than one long one, so each interviewer covers different criteria.
How many candidates should I interview?
There is no magic number. Interview until you have enough strong candidates to compare, usually three to five finalists. Interviewing too few makes the first decent person look great. Interviewing too many stretches the process and loses good people to faster employers.
Should I tell candidates the questions in advance?
You do not need to share exact questions, but tell them the format, who they will meet, and what any work sample involves. Candidates perform more representatively when they are not ambushed. For work samples and scenarios, giving the brief ahead of time is fair and still shows how they think.
What if I have no hiring experience and no HR support?
Use the process in this guide as a minimum: a written scorecard, the same questions for everyone, independent scoring, and a debrief on evidence. If there is any HR, legal or recruiting contact at your company, ask them to review your questions and explain local rules on what you can ask and how to document decisions.
Can I use AI to screen resumes?
Be careful. AI can summarize a resume against criteria you wrote, but it can miss context and may reflect bias, and some places regulate automated screening. Use it, if at all, to organize information for you, not to reject people, and ask HR about your company's policy first.
How we source, write, and correct our articles. Editorial standards
Related articles

OKR Examples by Team (Marketing, IT and More) + AI Template

How to Write Performance Reviews with AI (Without Sounding Robotic)

How to Sleep After Night Shift and On-Call Nights (With AI)
