Red Flags and How to Probe Them

Interviews are optimised to sell you the job, so warning signs are rarely stated. They surface as evasion, inconsistency between interviewers, or a detail nobody wants to elaborate on.

The ones worth probing:

Attrition. "How long has the average engineer been here?" and "why did the last person in this role leave?" A hesitation, or three different stories from three interviewers, matters more than the content of any single answer.

Process theatre versus chaos. Ask how a change gets from idea to production. Either extreme is a signal: a fifteen-step process at a twenty-person company, or an answer that reveals nobody knows who decides what.

On-call and incidents. "How often does someone get paged out of hours?" and "what happened after the last incident?" If there's no postmortem practice, incidents repeat and you'll live inside them.

Scope of the role. If the job description says senior frontend and the conversation drifts to owning infrastructure, data, and design, ask what the first six months actually look like. Small companies genuinely need breadth — that's fine — but there's a difference between breadth and three unfilled roles.

Working hours across time zones. For a US/EU remote role, ask what meetings are fixed and at what time. "We're flexible" without specifics tends to mean 6pm calls.

How the last hard decision went. A team that can't name one either doesn't make them or doesn't discuss them.

Talking about the AI hype. Founders who can't describe what their product doesn't do are selling, and the engineering reality behind that is usually a demo held together with prompt tweaks.

Then weigh them. A single red flag is normal — everywhere has something. Two founders contradicting each other on strategy is a different order of concern. And notice how the process treats you: ghosting between rounds, last-minute rescheduling, and a take-home that's really three days of unpaid work are all previews of how the company operates internally.

At a small company, culture is not a background variable — it's your daily experience and it comes directly from four or five people you'll have met. A year is a long time to spend somewhere you could have diagnosed in one careful conversation.

• Warning signs appear as vagueness in response to specificity, so ask specific questions.
• Ask why the last person in the role left, and compare answers across interviewers.
• Ask how a change reaches production; both heavy process and total absence of it are signals.
• Ask about paging frequency and whether postmortems happen at all.
• Check that the role's scope matches the title, and ask what the first six months actually contain.
• Pin down fixed meeting times for cross-timezone roles before believing "flexible".
• One red flag is normal; contradictions between interviewers are not.
• The hiring process itself — ghosting, rescheduling, oversized take-homes — is a live sample of the company.