top of page

How to Build an Interview Guide That Actually Works

Most small businesses do not have a formal interview process. Interviews happen, candidates get hired, and nobody thinks twice about it until a bad hire costs the company time, money, and morale. An interview guide is one of the simplest things a small business can put in place to avoid that outcome.


This guide will walk you through how to build one from scratch, even if you have never done it before.


Start With the Role, Not the Questions

The most common mistake is writing interview questions before you know what you are actually looking for. Before anything else, get clear on what this role requires.


Pull the job description. Talk to the hiring manager. Ask:

  • What does this person need to do well in their first 90 days?

  • What skills are non-negotiable versus nice to have?

  • What does failure in this role look like?

  • What kind of work environment will this person be stepping into?


From there, identify three to five core competencies you want to evaluate. Keep it focused. If everything is a priority, nothing is.


Example competencies for an Office Manager role:

  • Organization and time management

  • Communication and follow-through

  • Ability to manage competing priorities

  • Attention to detail

  • Comfort with ambiguity


Build Questions That Get Real Answers

Once you know what you are evaluating, build questions that connect directly to those competencies. Behavioral questions work best because they ask candidates to draw from real experience rather than tell you what they think you want to hear.


Instead of asking:

  • Are you organized?

  • Do you work well under pressure?


Ask:

  • Tell me about a time you had to manage multiple deadlines at once. How did you stay organized?

  • Describe a situation where priorities changed suddenly. What did you do?


The goal is a real example, not a rehearsed answer. Every question should tie back to a competency you actually need for the role.


Go Beyond Skills: Evaluate Emotional Intelligence

Technical skills can be taught. How someone handles stress, feedback, and interpersonal friction is much harder to change. For small businesses especially, one person with poor emotional intelligence can disrupt an entire team.

Build at least a few questions into your guide that assess EQ. Here are examples organized by what you are trying to understand:


Self-Awareness

Do they know their strengths and blind spots?

  • Tell me about a piece of feedback you received that surprised you. What did you do with it?

  • What is something you are still working on professionally?


Self-Regulation

Can they stay composed when things go sideways?

  • Describe a time when something did not go your way at work. How did you handle it?

  • How do you respond when a manager or client pushes back on your work?


Feedback Acceptance

Will they grow, or will they get defensive?

  • Tell me about a time you disagreed with feedback you received. What happened next?


Empathy and Relationship Management

Can they work well with different people?

  • Have you ever worked with someone who was difficult to get along with? How did you manage that relationship?

  • How do you adjust your communication style depending on who you are working with?


Red flags to watch for:

  • Answers that blame others without any ownership

  • Vague responses with no real examples

  • Dismissive tone when discussing feedback or mistakes

  • The classic I am a perfectionist answer to a self-awareness question


Assess Fit for Your Environment

Skills and EQ matter. So does whether this person can actually thrive in how your organization operates. A candidate who looks great on paper can still be a poor fit if they cannot work within your structure.


Be upfront about what your environment requires. If your team is remote and metrics-driven, say so. If the role requires flexibility in schedule but accountability for output, explain what that looks like in practice. Then ask questions to see if the candidate can work within it.


Example environment fit questions:

  • How do you typically structure your day when working independently?

  • How do you manage competing demands on your time during the workday?

  • Tell me about a time you had to hit strict productivity targets while working independently.

  • Does a flexible but accountable culture motivate you or stress you out?


The goal is not to scare candidates off. It is to give them an honest picture so they can self-select in or out before you both invest more time.


Add a Simple Rating System

Without a rating section, interview feedback ends up sounding like this: I liked them or Something felt off. That kind of feedback does not help you make a good decision or defend one.


A simple 1 to 5 scale is enough. Tie each score to the competency being evaluated, not just the general impression.


Rating

What It Means

1

Does not meet expectations: no clear example, no relevant detail

2

Partially meets: some example, but thin or vague

3

Meets expectations: solid example, reasonable approach

4

Exceeds: strong example, clear skills demonstrated

5

Exceptional: detailed, specific, directly relevant to the role


Each interviewer scores each question or competency independently. When you debrief, you have something concrete to compare rather than competing gut feelings.


What Your Interview Guide Should Include

Keep it simple. A good interview guide does not need to be long. It needs to be usable.


  • Position title and candidate name

  • Interviewer names

  • Core competencies being evaluated

  • Interview questions tied to those competencies

  • What a strong answer looks like for each question

  • Rating scale

  • Space for notes


That is it. One to two pages is plenty for most roles. The more complicated you make it, the less likely interviewers are to actually use it.


Common Mistakes to Avoid

  • Writing questions before knowing what the role actually requires

  • Skipping EQ and environment fit entirely

  • Making the guide so long interviewers ignore it

  • Letting different interviewers ask completely different questions

  • Forgetting to leave room for notes

  • Using a rating system nobody understands


The Bottom Line

An interview guide does not need to be a formal HR artifact. It needs to give your interviewers a clear structure, consistent questions, and a way to compare candidates fairly after the fact.


Start with what the role requires. Build questions that connect to those requirements. Add a few EQ and environment fit questions. Give interviewers a simple way to score responses. That is the whole framework.


Build it once. Refine it as you hire. It will save you from a lot of preventable mistakes down the road.


Need help building an interview guide for your team? Reach out to Acacia HR Solutions.


 
 
 

Comments


bottom of page