We spoke with hiring managers across engineering, product, sales, and operations. The question was simple: what do candidates get wrong when they interview at your company?
The answers were remarkably consistent — and they had almost nothing to do with skills.
"They Don't Know What We Actually Do"
This was the most common complaint, by far. Not that candidates couldn't do the job — but that they had a surface-level understanding of the business that made the entire conversation feel generic.
"I can tell within two minutes whether someone has actually looked at the product," one engineering director told us. "Not just the marketing site — the actual product. If they haven't, we're going to spend the whole interview with me giving context instead of evaluating them."
The fix is straightforward: actually use the product before you interview. Sign up for a trial, explore the interface, read recent release notes. If it's a B2B product with no free tier, at least watch demo videos and read the documentation.
"They Don't Know Where We Are in the Journey"
Every company is at a different point in its lifecycle, and the expectations for a role at a hypergrowth Series B startup are radically different from the same role at a mature public company. Candidates who treat these as interchangeable — using the same pitch, the same examples, the same questions — miss the point entirely.
A head of engineering at a late-stage company described it this way: "We're not looking for someone who wants to build from scratch. We already have the systems. We need someone who can scale them, stabilize them, and lead a large team through maturity. When candidates pitch themselves as 'I love building things from zero,' that's actually a red flag for us."
Know where the company is. Know what it needs at this stage. Frame your experience in those terms.
"They Ask Questions That Are Already on Our Website"
Nothing signals low effort like asking a question whose answer is three clicks away. "What does your company do?" or "Who are your main customers?" after a forty-minute interview makes every prior answer less credible.
The questions that impress are specific, informed, and show that you've thought about the company's particular situation. They require the interviewer to actually think — not recite a canned answer. That's what a strong candidate does.
"They Don't Know Who They're Talking To"
Before any interview, spend fifteen minutes researching each person on the panel. What have they built? What's their professional background? Have they written about anything related to your role?
This isn't about flattery — it's about calibration. A question that would land well with a former founder might fall flat with a career operator. Understanding who you're talking to helps you pitch yourself in the terms that matter to that person specifically.
What Good Preparation Actually Looks Like
The hiring managers we spoke with described preparation that went deeper than most candidates attempt:
- Reading the company's recent blog posts and engineering articles
- Understanding the competitive landscape and how the company differentiates
- Knowing the approximate team size and how it's structured
- Having a point of view on recent company news — launches, hires, strategic pivots
- Understanding the funding situation and what it signals about current priorities
None of this is secret. All of it is findable. Most candidates just don't do it — which is exactly why the ones who do stand out.