2 min lesson
Disagree well and reason from first principles out loud
Put yourself in this case: "An interviewer asks a crypto question and you genuinely don't know the answer. What's the truth-seeking move and why does it matter more on a security team?" Give the clearest next step.
Step 1 of 2
Disagree well and reason from first principles out loud
Truth-seeking isn't only about your own mistakes. It's also how you handle a live disagreement and how you behave when you hit the edge of what you know in the room.
- Hit an unknown
- Say “I don't know, here's how I'd reason about it” and derive from first principles - far stronger than bluffing a fact
- Strong opinions, held loosely
- Stake a clear position on a tradeoff, then name exactly what evidence would change your mind
- Disagree well
- Push back on the interviewer's premise with reasoning and concede cleanly when they have the better argument
- Correct yourself mid-answer
- “Actually, I mis-scoped that threat a second ago - the real attack path is…” reads as senior, not shaky
“I argued that we could ship our agent's file-write capability without a sandbox because the model ‘wouldn't do anything destructive.' A teammate built an indirect prompt injection - a malicious comment in a dependency's README - that got the agent to overwrite a config file. I was wrong and I'd been reasoning from how the model behaves on average instead of what an attacker could steer it into. We held the feature, I built a write-scoped sandbox with an approval step for anything outside the workspace and I stopped trusting model intent as a security boundary. The evidence changed my mind faster than I'd have liked, which is exactly how I want it to work.”
That story passes because the mistake is real, the cost is concrete and the pivot is driven by evidence rather than vibes. It also quietly demonstrates agent-security fluency, which is the round you most want to seed early.