Most interviews fall apart before they even start, not because the wrong questions get asked, but because there’s no consistent structure behind them at all. Two candidates you interview an hour apart should walk away having answered the same core questions, whatever the role, and too many hiring managers wing it instead.
Here’s what actually holds up, position by position, red flag by red flag.
Table of Contents:
- How to prep for an interview, whatever the role
- The three questions every interview needs
- How to structure multiple rounds
- Green flags: what a good answer actually sounds like
- Red flags, and how to tell nervous from dodging
- Growth potential and coachability: what actually predicts it
- Legal dos and don’ts
- How to actually compare candidates and make the call
How to prep for an interview, whatever the role
Prep should look different depending on the role. For an entry-level position, don’t over-invest in homework, personality matters more than resume details, since experience only goes so far in a lot of entry-level jobs. What’s worth knowing ahead of time is whatever the candidate already shared, resume, pre-screen answers, so you can pivot the conversation if it needs it.
Management roles deserve more depth: their background, their actual tasks, and more detailed questions built around how their experience translates to this specific job. The process should get longer too, an entry-level candidate might go through one or two conversations, while a management candidate meets multiple people, sometimes up to the C-suite.
The one thing that shouldn’t change is consistency. Every candidate should get the same core questions. If two people you interviewed an hour apart compared notes, they should recognize the same interview. That’s the difference between asking whatever comes to mind, and actually running a process.
The three questions every interview needs
Whatever the role, open every interview the same way, then build out from there with three core questions.
Start with: what do you know about our company? It’s a straightforward check on whether the candidate did their homework, and it sets the tone that this conversation has a structure.
Ask about values alignment through a real story, not a hobby. Skip “tell me about your hobbies” or “what are you into outside work,” those questions invite affinity bias more than insight, you end up favoring someone who shares your interests rather than someone who’s actually right for the role. Instead, ask for a specific story that reveals how a candidate lives out a value your company actually holds. At CareerPlug, that might sound like “tell me about a time you had to speak up to a manager” or “tell me about a time it was hard to be kind, but you did it anyway.” Those stories tell you far more about real culture fit than a shared hobby ever will.
Tailor the experience question. Don’t ask “tell me about your experience,” or you’ll just get the resume read back to you. Instead: “I see you worked at X doing Y, and this role needs Z, how do you see that translating?” It forces a candidate to connect the dots instead of reciting.
Name the non-negotiables. Days, hours, core tasks, whatever’s actually required. Can they work it? If the answer is no, that’s the end of the conversation, cleanly, with no hard feelings on either side.
Those three categories, values alignment, tailored experience, non-negotiables, are exactly what a good interview scorecard should be built around. If you’re a CareerPlug user, check your account for the built-in scorecard feature that formalizes this exact structure.
How to structure multiple rounds
Keep the first interview standardized no matter the level, culture questions, tailored experience, the non-negotiables. Round two, three, or four is where it should change, especially for management roles. Go situational: if this happened in your first 30 days versus a year in, how would your answer be different? You’re testing judgment at different stages of the job, not just theoretical values.
For a role you’ve managed yourself, build questions straight from real scenarios: a tough interaction with a coworker, a tough interaction with a customer, someone getting hurt on the job. Ask candidates to walk you through something that actually happened to them, not how they think they’d react to something hypothetical.
One more thing worth doing: prep the candidate for what’s next. If someone’s made it through two rounds, tell them plainly that you’re not the one making the final call, but give them a sense of what the next interviewer will ask and what will help them land it. It costs you nothing, and it means the person shows up ready instead of walking in unprepared. Automating the scheduling itself frees up that time for the parts of the process that actually need a human touch.
Green flags: what a good answer actually sounds like
The best answers aren’t the most polished ones. They’re the ones backed by a real story, evidence the candidate actually has the knowledge, skill, or ability the job needs, not just a well-rehearsed line.
A generic question like “what’s your biggest weakness” tends to produce a generic, rehearsed answer. A more specific question gets you a more specific answer: “what’s some coaching or feedback a past manager gave you that was tough to hear, and what did you do after receiving it?” or “tell me about a time you failed at something at work. What happened, and what did you take away from it?” Someone who can walk you through a real example, including what they actually changed afterward, is showing you something a polished non-answer never will.
Also listen for evidence they did their homework, that they read the job ad, looked at your company, have some sense of what your culture actually is.
Red flags, and how to tell nervous from dodging
Nervous and dishonest can look similar on the surface, but they feel different once you’ve done enough of these. Nervous energy usually sounds like a lack of confidence: answers that trail off like a question, a little scattered, but genuine underneath it. Dodging sounds rehearsed and generic, an answer with no real specifics attached to it, no names, no timeline, no actual outcome. Lately that sometimes means literally hearing someone read off an AI-generated script, word for word, a smooth answer that has no story behind it when you ask a single follow-up question. You can hear it in resumes too, when the phrasing doesn’t sound like a real person wrote it. It’s the same reason CareerPlug keeps the actual hiring decision with a person, automation is useful right up until it starts making the call for you.
Watch for discrepancies too. If you ask someone to confirm dates at a previous job and what they say doesn’t match the resume, that’s a signal the rest of what they’re telling you probably isn’t fully accurate either.
Growth potential and coachability: what actually predicts it
Experience matters, but so do the skills and abilities that make that experience actually useful on the job. A salesperson needs to be a skilled rapport-builder. A retail cashier needs to stay calm and smile through a difficult customer interaction. Naming the specific skill a role actually needs, and evaluating for that directly, beats a vague sense of whether you “like” someone, which is more a measure of whether they remind you of yourself than whether they can do the job.
Most candidates for a management-level role already have the experience on paper, roughly 90% of them. So once ability is confirmed, the real question shifts: does this person have a growth mindset, and how much runway do they realistically have to keep developing?
Charisma in the room isn’t proof of that. Someone can be engaged, warm, and excited about the role in an interview and still be resistant to feedback and set in their ways once they’re actually on the job, just as someone quieter in the interview chair can turn out to be genuinely coachable. The real evidence is in the story, not the energy in the room: “tell me about a time you got feedback that was hard to hear, what was it, and what did you do?” or “tell me about a time you didn’t know something important for your job. What steps did you take to get up to speed?” Someone who can walk through an honest answer to either of those has shown you actual evidence of growth, not just enthusiasm.
Weigh how much a candidate is bringing already against how much your company realistically has the bandwidth to help them develop. A candidate with less experience but real, evidenced growth potential can outperform a stronger resume attached to someone who never fully buys in.
Legal dos and don’ts
The rule underneath everything in this section: if it’s not actually relevant to the job, don’t ask it.
A classic case: a candidate mentions relocating for a spouse’s job, and the natural follow-up, out of simple curiosity, is asking what the spouse does for work. Completely innocent, and still a question that crosses the line.
That reframe works for almost anything. Don’t ask if someone has a car, ask if they can get to work. Don’t ask why they need Sundays off, tell them the job requires Sundays and ask if they can accommodate it. If the answer is no, that’s your disqualifier, no explanation needed from either side. The same logic applies to protected categories: age, sex, religion, disability. Don’t ask about the characteristic itself or the reason behind it, ask about the job. You can confirm someone meets a role’s legal minimum age, and you can ask whether they can perform the job’s actual requirements, but you can’t ask their date of birth, their religious beliefs, or whether they have a disability.
Sometimes candidates volunteer things you shouldn’t follow up on: a disability, a health issue, something personal about their family. Don’t ask how it will affect their work, and don’t dig deeper. Whether someone might need an accommodation down the line has no bearing on the hiring decision itself, that’s a separate conversation from evaluating whether they can do the job. The right move at the moment is a simple “thanks for sharing” and a pivot to your next question. In case a conversation starts moving into personal or protected information, steer it back to the role and your standard interview questions.
The best piece of advice for any franchise owner: get an employment lawyer to review your interview questions, your forms, your scorecard. It’s a modest upfront cost, and it’s nothing compared to the cost of getting it wrong. Do it once, then audit it every year, since employment law shifts constantly and varies a lot by state. See our guide to hiring compliance basics for where else this comes up. SHRM.org is a solid free resource for templates and general guidance, and AI tools are genuinely useful for a second opinion on a question you’re unsure about. None of that replaces an actual lawyer, but it’s a reasonable place to start.
How to actually compare candidates and make the call
The approach should change with the level of the role. For entry-level positions, run a short, efficient process, it still needs to be a real process, just a faster one, and move quickly once you find someone genuinely good. Don’t hold out hoping for someone better who might not exist. Just make sure you’ve got the support in place to develop them once they’re in the seat.
For management roles, build a more thorough process and stick to it. Tell candidates exactly what to expect, this week is phone screens, this week is round two, by this date you’ll have an answer, and hold that timeline. It protects you two ways: candidates who were never fully committed will drop out on their own, and the ones who do stick around have already shown you they’re willing to invest in your company before they’ve even started.
When it’s time to decide, do the gut check last, not first. Evaluate the actual evidence: does this person have the skills and experience the job needs, and does their story show real values alignment? Once you’ve done that work, a lingering gut feeling is worth listening to, but it should be checked against your notes and your scorecard, not treated as a standalone verdict. If something still feels off after all that, don’t ignore it. If it feels right, that’s confirmation, not a replacement for the evaluation itself. Just make sure the process matched the role, don’t put an entry-level candidate through four rounds, and don’t rush a district manager hire through one conversation.
Even hiring managers who’ve done this for years get it wrong sometimes, picking someone whose experience looked strong on paper without confirming the skills and values alignment the role actually needed, and watching it fall apart from day one. Bad hires happen to everyone, including people who do this for a living. The only real difference between someone new to hiring and someone who’s done it a thousand times is which mistakes they’ve already made, and what they did about it afterward.
See how CareerPlug’s franchise hiring software turns this kind of structure into something every hiring manager can actually use, no extra setup required. Let’s get started.