Interviews as proof presentations: pick any claim

Most interview prep optimizes for answering questions. That's backwards. The candidates who get offers don't answer questions well — they invite the hardest question and then have receipts. The reframe is simple and it changes how you build your whole career: an interview isn't a test you pass, it's a proof presentation where you dare the room to pick any claim.

The claim-proof gap

Every resume is a list of claims. "Built a RAG pipeline." "Reduced p95 latency by 60%." "Led a migration." A claim is worth exactly as much as the proof standing behind it, and most claims have no proof behind them at all — which every experienced interviewer knows, which is why they probe. The probe isn't hostile. It's the only way to tell a real claim from a decorated one.

So stop trying to survive the probe. Build so that you welcome it.

What "proof you can present" looks like

For each significant claim, you should be able to produce one of:

• An artifact. The actual pull request, the eval harness, the postmortem you wrote, the dashboard you built. Not a description of it — the thing.
• A decision with a defended tradeoff. "I chose a circuit breaker over more retries because retries were the load source, not the fix. Here's the incident that taught me that." The proof is that you can explain what you didn't do and why.
• A number with its methodology. "60% p95 reduction" is a claim. "60% p95 reduction, measured on the checkout path over two weeks, here's the before/after and how I isolated the change" is proof.

The pattern: a claim points at a result. Proof points at the work, and the work is unfakeable.

How this changes what you build

If you know every claim will be probed, you build differently while you build. You keep the postmortem. You save the eval harness. You write down the tradeoff at the moment you make it, not reconstructed under interview pressure six months later. Your career becomes a ledger of defensible decisions instead of a highlight reel of unverifiable outcomes.

This is why "pick any claim" is the strongest move in the room. It signals that there is no decorated line on your resume — every claim is load-bearing, and you know it, because you built the proof alongside the work. Weak candidates hope the interviewer picks the claim they rehearsed. Strong candidates don't care which one you pick.

The practice

After every meaningful piece of work, ask one question: what's the proof I'd show if someone challenged this? If the answer is "nothing," you did the work but didn't capture the evidence — fix that now, while it's cheap. A career is not what you did. It's what you can prove you did, on demand, to a skeptic. Build the ledger as you go, and the interview stops being a test and becomes a showing.