Free — no signup required

Winning Over the "Veto" Voter

2 min read

It Is Rarely About Code

Bar Raisers almost never veto candidates for minor technical gaps. If you forget the exact syntax for a binary search or misname a design pattern, the Hiring Manager can override that concern — they know you'll ramp up. What Bar Raisers veto for are character signals that predict long-term toxicity, low ownership, or poor judgment. These are not coachable in 90 days. They are deal-breakers.

The 3 Instant Veto Triggers

1. The "Victim" Narrative

"I couldn't ship the feature because my PM kept changing requirements and my manager didn't back me up."

What the Bar Raiser hears: This person externalizes all failure. They will poison team morale and create friction with every cross-functional partner.

2. The "Lone Wolf"

"I basically built the entire platform myself. The rest of the team was too slow and didn't understand the architecture."

What the Bar Raiser hears: This person is not a force multiplier. They will hoard knowledge, create single points of failure, and alienate colleagues.

3. The "Bluffer"

Confidently explaining a concept you clearly don't understand, or claiming experience you don't have.

What the Bar Raiser hears: This person is dishonest under pressure. If they'll bluff in an interview, they'll bluff in a production incident or a status update to leadership.

How to Win: Structured Vulnerability

The counterintuitive move is to show calibrated vulnerability — owning your failures clearly, specifically, and with evidence that you learned from them.

Compare these two answers to "Tell me about a time you made a mistake":

Weak: "I once deployed too quickly and there was a small outage. I learned to be more careful."

Strong: "I deployed a config change without validating it against the staging environment first. It took down the payments service for 5 minutes during peak hours. I wrote the post-mortem, identified three process gaps, and proposed a pre-deploy checklist that the team adopted. We haven't had that class of incident since."

The strong answer demonstrates ownership (no blame), specificity (real details, not vague), impact awareness (payments, peak hours), and systemic thinking (process fix, not just personal lesson). These are exactly the signals a Bar Raiser is looking for.

The key insight: vulnerability without accountability is just complaining. Vulnerability with a clear "here is what I changed" is evidence of a growth mindset and high integrity — the two things that are hardest to fake and most predictive of long-term performance.

This is one of 18 chapters

Every chapter is free — Kubernetes, Terraform, SRE, distributed systems, and more — with fast daily review built in.

Sign up free