
The Perfect Interview Script: Guide & Template
Learn how to create an interview script that ensures fairness and efficiency. Includes common pitfalls, best questions, and a ready-to-use template.
Remo Vloet7 min.

Learn to spot the 20 most common interview red flags, from vague answers to culture misalignment. Includes how to probe further without confrontation.
Every recruiter has been there: the candidate seemed perfect on paper, aced the first ten minutes, then said something that made your stomach drop. You ignored it. You hired them anyway. Three months later, you wished you had not.
Red flags during interviews are not always obvious. Some are subtle shifts in tone. Others hide behind polished answers. The best recruiters do not just listen to what candidates say. They notice what candidates avoid saying.
This guide breaks down 20 red flags across four categories: communication patterns, experience gaps, motivation signals, and behavioral cues. For each flag, you will learn what it looks like in practice, why it matters, and how to probe further without turning the conversation into an interrogation.
One important note: not every red flag means "don't hire." Some have perfectly reasonable explanations. The goal is not to disqualify candidates at the first sign of trouble. It is to know when to dig deeper.
How a candidate communicates during an interview often mirrors how they communicate on the job. Pay attention to patterns, not isolated moments.
What it looks like: The candidate speaks in generalities. "We improved the process" instead of "I redesigned the onboarding workflow, which cut ramp-up time by two weeks." They use "we" for everything and struggle to articulate their specific contribution.
How to probe: "Walk me through your specific role in that project, step by step." If they still cannot get specific, that is telling.
What it looks like: Early in the interview, they say they left for more responsibility. Later, they mention feeling overwhelmed by their workload.
How to probe: Circle back: "You mentioned wanting more responsibility. Can you help me understand how that connects to the workload challenges you described?"
What it looks like: When asked about a failed project, every problem was someone else's fault. The manager didn't communicate. The team wasn't competent. The candidate never acknowledges their own missteps.
How to probe: "If you could go back to that situation, what would you personally do differently?" This reframes from blame to growth.
You ask about their reason for leaving. They pivot to what excites them about your role. Occasional redirection is normal (nerves), but a consistent pattern of avoidance suggests they are hiding something. Be direct but kind: "I want to understand what prompted your departure from [company]."
Not just one bad experience, but every company was terrible, every manager incompetent. If everyone they have ever worked with was the problem, the common denominator is them. Ask: "Was there a manager or team you particularly enjoyed working with?" One negative experience is normal. The pattern is the red flag.
A candidate's track record tells a story. But you need to read between the lines.
There is an 18-month gap on the CV. Gaps themselves are not red flags. Caregiving, health issues, burnout recovery are all legitimate. The red flag is the unwillingness to discuss it honestly. Normalize it: "Career gaps are common. I'm curious about what you were focused on during that period."
Five jobs in four years, each at the same level. No progression in title or responsibility. Job-hopping with upward trajectory shows ambition. Lateral moves without growth suggest the candidate may struggle to stay engaged. Ask: "What's the common thread across these moves?"
The candidate talks about high-level strategy and impressive outcomes but cannot explain what a typical Tuesday looked like. This often indicates title inflation or a highly delegated role. Ask: "Walk me through a typical day. What tools did you open first?" See our practical guide to interview assessment.
Their CV lists advanced Excel, but they cannot explain a VLOOKUP. CV embellishment is common, but significant gaps indicate dishonesty. Ask scenario-based questions: "If I gave you a dataset with 10,000 rows of candidate feedback, how would you approach finding patterns?"
Engaged candidates are curious. They want to understand the team, the challenges, the growth path. Try: "What's the one thing about this role that you'd most want to understand better before making a decision?"
Skills can be trained. Motivation cannot. These signals help you gauge whether a candidate genuinely wants this job or just wants a job.
They don't know what your company does beyond the job listing. Basic research takes 15 minutes. If they didn't invest that, they probably won't invest in the role either. Ask early: "What caught your eye about us specifically?"
Every question loops back to compensation. Fair pay matters, but the red flag is when money is the only thing driving the conversation. These candidates leave as soon as a better offer appears. Ask: "Setting compensation aside, what about this role excites you day to day?"
They want management, but the role is individual contributor. Hiring someone whose goals don't align means they will disengage within a year. It is not fair to them or your team. Be honest about mismatches. It saves everyone time.
"I'll take anything." "I just need a job." Excessive eagerness combined with no specific interest in the role. But do not dismiss someone solely for being eager. Some excellent candidates are in genuinely difficult situations. Look for whether they can articulate specific fit alongside their urgency.
They refuse to share any range, or name a number wildly outside your band. Be transparent: "Our range for this role is X to Y. Does that work for you?" Candidates who won't engage may have unrealistic expectations or may be using your offer as a bargaining chip elsewhere.
Actions speak louder than answers. Watch for patterns in how candidates behave throughout the process.
Rude to the receptionist, dismissive toward the recruiter, friendly only to the hiring manager. One of the most reliable predictors of workplace behavior. How someone treats people they don't need to impress tells you who they really are. After every interview, check in with everyone the candidate interacted with.
Reliability in the hiring process typically reflects reliability on the job. One reschedule is fine. A pattern is not. Context matters: a parent with childcare emergencies differs from someone who simply forgot.
Every answer sounds memorized. Preparation is good, but over-preparation that masks authenticity makes it impossible to assess the real person. Go off-script: "What's something you've changed your mind about in the last year?" See our guide to situational interview questions.
Glancing at notifications, keeping their phone face-up on the table. It signals the interview is not their full priority right now. Simply note it in your evaluation.
Complaining about a case study, refusing a reference check, pushing back on a second interview. Acknowledge their concern: "Here's why we include this step and what we're evaluating." But be honest: if you are asking for six rounds and a take-home project, the pushback might be justified.
Many red flags can also be symptoms of plain nervousness. Vague answers, contradictions, robotic delivery: anxious candidates display all of these.
Here is how to distinguish them: nervousness improves over time. An anxious candidate warms up and gets more specific; a deceptive candidate stays vague throughout. Nervous candidates are consistent when you circle back 20 minutes later. Show genuine warmth: offer water, smile, make a light joke. Nervous candidates respond to kindness by opening up; evasive candidates remain guarded regardless of atmosphere.
Always give candidates at least 15 minutes to settle in before evaluating. Lead with easy questions. Build rapport. The red flags that matter are the ones that persist after the candidate is comfortable.
Be specific, not judgmental. Write "Candidate could not name a specific contribution to the Q3 project despite being listed as project lead" instead of "Seemed dishonest about experience." Note the context: was it early in the interview (possibly nerves) or in response to a follow-up question? Track patterns, not incidents. One vague answer is noise; four in a row is a signal.
Tools like AI-powered interview summaries help capture these nuances in real-time, so you are not relying on memory alone. Pair that with full transcript transparency to revisit exact moments that raised concerns. What you do not get on top of that is a read on the candidate's personality or a score for your own interviewing: neither can be pointed back at a sentence, and a red flag you cannot play back is still only a hunch. Across a team, dashboards and reporting count what happened rather than analysing anybody. Check out our interview summary guide with templates for a complete framework.
Individual awareness is not enough. Your entire hiring process should be designed to surface red flags naturally. Use structured culture interview questions and a peer-to-peer interview framework. Deploy multiple interviewers, debrief within 24 hours, and regularly calibrate what counts as a red flag for each specific hire. By recording conversations through omnichannel recording, you will not miss a single signal.
There is no fixed number. A single signal deserves probing; a pattern of three or more red flags across different categories is a strong signal. Always weigh severity and context.
Use structured interviews with the same core questions for every candidate. Have multiple interviewers evaluate independently and compare notes afterward. This limits the effect of individual bias.
Yes. For senior candidates, vagueness about specific contributions weighs more heavily, since they should have a track record. For junior candidates, lack of specific experience is more normal, but pay closer attention to motivation and learning ability.
AI interview summaries help you recognize patterns you might miss in the moment. The transcript makes it possible to listen back to exact moments that raised concerns.
About the author

Remo Vloet is a co-founder of Simply, the AI Operating System for recruitment agencies: inbox, meetings, sourcing, CV parsing, search and matching, documents and automation in one system. With a background in building complex software, he contributes to the technical vision behind Simply.
LinkedInArticles by Remo VloetThere is no magic number. One severe red flag (like dishonesty about qualifications) can be disqualifying on its own. Meanwhile, two or three minor flags (like nervousness-related vagueness) might be completely benign. Focus on the severity and pattern rather than counting. A single serious integrity concern outweighs five minor communication hiccups.
During the interview, yes, indirectly. Probing questions are a way of giving candidates the chance to address concerns. After a rejection, be honest but constructive. You do not need to say 'we noticed red flags,' but you can share specific feedback like 'we were looking for more concrete examples of hands-on experience in X.' This helps candidates improve and reflects well on your employer brand.
Three practices help the most. First, use structured interviews with standardized questions so you evaluate everyone on the same criteria. Second, document red flags with specific behavioral examples rather than gut feelings. Third, debrief with multiple interviewers and compare notes before making a decision. Be especially cautious about cultural communication differences: what reads as 'evasive' in one culture may simply be a different communication style.
The core red flags are the same, but remote interviews add some specific ones: reading answers off-screen, unexplained background noise or interruptions, poor camera/audio setup (which can signal low investment in the process), and difficulty with basic video call etiquette. At the same time, remote interviews make some flags harder to spot, like body language and how candidates treat support staff. Consider adding a brief in-person meeting for final-round candidates when possible.
Gut feelings in hiring are often pattern recognition from experience, but they can also be bias. If you cannot articulate the concern, discuss it with your hiring team. Sometimes another interviewer noticed the same thing and can name it. If no one can identify a concrete concern after discussion, it is usually better to proceed with the candidate rather than reject based on a feeling you cannot explain or defend.

Learn how to create an interview script that ensures fairness and efficiency. Includes common pitfalls, best questions, and a ready-to-use template.
Remo Vloet7 min.

Assess culture fit without gut feeling. These 20 interview questions reveal how candidates work, communicate, and handle conflict in practice.
Remo Vloet9 min.

Find out how Simply can completely evolve your workflow.No slides, just product.