Interview red flags, and the green flags worth noticing

Before listing anything, the caveat matters more than the list. Interviews are artificial, stressful situations, and almost every individual behaviour that gets called a red flag also has an innocent explanation. A candidate who seems evasive may be nervous. One who criticises a former employer may have had a genuinely bad experience they are describing accurately. One who arrives underprepared may have been given two hours' notice.

What makes something worth acting on is repetition across the conversation, or a behaviour so specific that no benign reading survives. Blaming one previous manager is a data point that means little. Blaming every previous manager, in every example, for every setback, is a pattern — and the pattern is the signal. This distinction is worth holding deliberately, because red-flag lists are the part of hiring advice most easily turned into a reason to reject candidates for being anxious. The interviewer's job is to notice the behaviour, then probe it, and only then decide. Rejecting on a first impression of a single moment is the failure mode these lists are supposed to prevent, not one they are exempt from.

The most reliable warning sign is a candidate in whose account nothing was ever their fault. The last job ended because the manager was unreasonable, the project failed because another team was incompetent, the targets were missed because they were unrealistic. Any one of these can be true. All of them, consistently, across a career, describes someone who has not learned anything from their own mistakes, because they have not registered having made any.

The way to test it is to ask directly for a failure they were responsible for and what they changed afterwards. A candidate who can describe a specific mistake, without minimising it and without excessive self-criticism, and can say what they do differently now, is demonstrating the single most useful trait in a new employee. A candidate who cannot produce one — who reframes every prompt into a story where they were correct and someone else was not — is telling you something durable about how they will respond when something goes wrong on your watch. Note that the useful version of this question requires patience: many candidates initially offer a sanitised failure, and the real answer comes after a follow-up asking for one where the consequences actually mattered.

When someone describes work they genuinely did, detail comes easily: who else was involved, what went wrong, what the numbers were, what happened next. When someone describes work they were adjacent to or did not do, the account stays at a level of generality that sounds reasonable but does not resolve when pressed.

The test is to ask for the next layer down. What was your specific part? Who did the rest? What did you do when it went wrong? A candidate who did the work answers immediately, often with details you did not ask for, because they are recalling rather than constructing. A candidate who did not gets more abstract as you press, moves to describing how such things are generally done, or redirects to what the team achieved. Two cautions. Some people are genuinely poor at describing their own work, particularly in an unfamiliar register or a second language, so distinguish inarticulacy from evasion by asking about something concrete and low-stakes and seeing whether the detail appears. And a candidate saying 'that part wasn't mine, I did this bit' is being precise, which is the opposite of a red flag and deserves to be recognised as such.

A candidate who cannot say what your business does, having applied to it, is showing you their standard of preparation for things that matter. This is worth treating as a soft signal rather than an automatic exclusion, since candidates applying widely under financial pressure may not have researched every application, and that is a circumstance rather than a character trait. It becomes a real signal at second interview, where anyone still unable to describe the business has had ample opportunity.

Dismissiveness about the role is a firmer signal and shows up in specific ways: describing the job as a stepping stone in front of you, treating parts of the work as beneath them, or being visibly uninterested in the practical realities of how the business operates. In a small business this matters more than in a large one, because roles are broad and everyone does some unglamorous work. Someone who has already decided which parts of the job are for other people will be a management problem within weeks. Worth distinguishing, though, from a candidate who is honest that they want to progress beyond this role eventually. That is ambition rather than dismissiveness, and it is usually a good sign.

Positive signals get less attention than warning signs and are at least as predictive. The clearest is asking good questions — not the polite closing enquiry about next steps, but questions revealing they have thought about the work: what goes wrong most often, what the previous person found hardest, how success is measured, who they would depend on. These come from someone imagining themselves doing the job rather than trying to be selected for it.

The second is admitting what they do not know, cleanly and without anxiety. 'I haven't used that system, but I learned the other one in about a fortnight' is a stronger answer than a claim of familiarity that turns out to be thin, and it predicts an employee who will tell you when they are out of their depth rather than improvising. The third is curiosity about the business itself — how it makes money, who the customers are, what the constraints are — which in a small business correlates strongly with someone who will notice problems and mention them. The fourth, easiest to overlook, is a candidate who is precise about their own contribution, including where it was limited. Precision under questioning is difficult to fake and is a reasonable proxy for honesty about work generally.

The risk in any red-flag list is that it supplies vocabulary for rejecting candidates on grounds that are actually about background or manner. 'Seemed evasive', 'not confident', 'poor communication' and 'attitude' are the phrases through which this usually happens, and each can describe a genuine problem or a candidate who is nervous, speaking a second language, or unfamiliar with interview conventions.

The discipline that keeps this honest is to require the specific behaviour rather than the label. Not 'seemed evasive' but 'asked three times what his own role was on the project and did not answer'. Not 'poor communication' but 'could not explain the process to me in a way I could follow, which the job requires daily'. If you cannot state the behaviour, you do not have a finding, you have an impression — and an impression recorded as a red flag is how a structured process gets undone from the inside. Recording the behaviour also lets you check whether you are applying the standard evenly, which is the question that matters. The same discipline applies to green flags: 'asked what goes wrong most often' is evidence, while 'good energy' is a feeling about a person that will correlate with people resembling you.