DEV Community: Christopher Jakob

You blank in technical interviews even when you know the answer. Let's fix that.

Christopher Jakob — Tue, 13 Oct 2026 17:55:20 +0000

I'm Christopher. Nine years in the Marine Corps, then software and data engineering, including edge computer vision work for the Air Force on a project called Athena. I've briefed people who could end a career with a look. And I've still walked out of a coding interview knowing I knew the answer, and blanked the second the shared editor opened.

If that has happened to you, you are not broken. Your filter is just doing old work.

Why your brain dumps the answer

You do not build confidence. You unhide it. The same person who explains a hash map to a friend over coffee is the one who freezes when the interviewer says "walk me through your approach." Skill did not leave the room. Safety did.

Your brain has a selective filter called the reticular activating system, the RAS. It decides what you notice. It learns from what life fed it. A harsh code review, a teacher who called you out, a panel that went quiet after your answer: those moments trained the filter to treat evaluation as threat.

So in the interview, the filter floods you with threat data. The interviewer's face. The blank cursor. The thought that one wrong line ends the offer. Your body follows: tight chest, hot face, voice that feels thin. That is arousal driven by the filter, not proof you are underqualified.

You cannot logic the filter open. You retrain it with small, repeated experiences that say speaking under pressure is survivable.

The daily rep that transfers

Once a day, give one genuine, specific compliment to a stranger. Cool shoes. Nice jacket. That is a sharp haircut. Say it. Walk on.

It sounds nothing like a whiteboard. It is the same move at a lower volume. You put your voice into a space where nobody invited you, while your body expects judgment. The first few times will spike. Then they will not. Your filter collects evidence that unprompted speech is fine.

That is rung one of a simple ladder:

Genuine compliments to strangers
Light conversation after the compliment
Longer conversation, still with no agenda

Move up only when the current rung stops spiking your heart rate. Do not skip ahead because an interview is next week. Skip ahead and you train panic, not unlock.

How to run the interview itself

Treat the interview like a workout with warm-ups, not a one-shot performance.

Warm up your voice before you join. Talk out loud for two minutes. Narrate your commute. Read a paragraph from any article. Your vocal cords and your filter both need a first rep that is not scored.

Say something in the first sixty seconds. "Thanks for having me." "I'm looking forward to this." "Quick question before we start: how long do we have?" Early speech shrinks the moment. Silence grows it.

Narrate while you think. When you blank, say "I'm going to think out loud for a second." Then do that. Interviewers often care more about how you recover than about a perfect first pass. Silence trains your filter that blanking is catastrophic. Narration trains it that blanking is temporary.

Lower the bar for the first useful sentence. You do not need the optimal solution in sentence one. Try "My first pass would be a hash map keyed on id, then I'd check for edge cases." Wrong is recoverable. Frozen is what costs you the room.

Score the rep, not the offer. Your win is that you spoke, recovered, and kept going. Log it. Three interviews where you recovered from a blank is better training than one perfect round you cannot explain.

What Athena taught me about blanking

On Athena, edge sensors ran a local model. When something significant got flagged, the system shipped context from before, during, and after the event to AWS so the models could keep learning. The model got better because it kept getting new examples, including the messy ones.

Your interview brain works the same way. Every time you blank and quit the thought, you feed the filter another example that pressure equals shutdown. Every time you blank, narrate, and keep going, you feed it the opposite. Enough of those and the blank stops owning the room.

You already have the answers. You already have the voice. The interview did not remove them. Old training hid them.

Your mission this week

Compliment one stranger a day for seven days.
Before your next interview or mock interview, warm up your voice for two minutes out loud.
In that session, speak in the first sixty seconds, and if you blank, narrate for ten seconds instead of going silent.
Write down each rep. Look at the list on Friday.

Then tell me in the comments which part hit hardest: the stranger rep, the warm-up, or staying vocal after a blank.

You Stay Quiet in Meetings When You Know the Answer. Let's Fix That.

Christopher Jakob — Fri, 09 Oct 2026 17:50:16 +0000

You stay quiet in meetings when you know the answer. Let's fix that.

I spent nine years in the Marine Corps. I've been yelled at by people who were very good at yelling. And years later, as a data engineer on an Air Force computer vision project, I still caught myself sitting in a sprint meeting with the right answer in my head, saying nothing, and then listening to someone else say it five minutes later.

That stings. If you've done it, you know exactly the feeling.

Here's what I figured out, and what I actually do about it.

It's not that you lack confidence

I don't believe you build confidence. I believe you unhide it. The version of you that explains a bug fix clearly to a coworker at lunch is the same person who goes silent when the camera is on and the tech lead is listening. Nothing about your skill changed between those two rooms. Something about your filter did.

Your brain has a selective filter called the reticular activating system, the RAS. It decides what you notice out of the millions of things happening around you. It learns from what you feed it. If your past is full of moments where speaking up went badly (a senior dev tore apart your idea, a teacher laughed, a code review got brutal), your filter got trained to scan for threat. So in the meeting, it shows you every reason to stay quiet: the manager's neutral face, the silence after someone else spoke, the chance you're wrong.

The RAS also drives arousal, the physical side. That's the tight chest, the warm face, the voice that feels like it'll crack. That's not weakness. It's a filter doing the job it was trained to do.

The good news is filters can be retrained. You retrain it with new experiences, in small doses, on purpose.

The rep that does the most work: compliment a stranger

This sounds unrelated to standups. It isn't.

Once a day, give one genuine, specific compliment to someone you don't know. The barista, the person in line, the guy at the gym with a good deadlift. "That's a great jacket." Done. Walk away.

Why this works: it's the smallest possible version of the exact thing you freeze on in meetings. You're putting your voice into a space where nobody asked for it. Your body will react the first few times. Then it stops reacting, because your filter keeps collecting evidence that speaking up unprompted is fine, and usually goes well.

That's the first rung of the ladder:

Quick compliments to strangers
Light conversation
Deeper conversation

You move up when the current rung stops spiking your heart rate. Not before.

Bringing it into the meeting

Once the daily reps are going, do these at work.

Speak in the first five minutes. The longer you wait, the bigger the moment gets in your head. Say anything early. "Morning." "I can take notes." "Quick question on the ticket." Your voice is now in the room, and the next thing is easier.

Lower the stakes of what you say. You don't need a perfect answer. Try "I might be off, but I think the timeout is coming from the retry logic." Hedged, useful, and it gets the idea on the table. Being wrong in a meeting costs almost nothing. Being silent costs you the credit, every time.

Write one sentence before the meeting. Look at the agenda and write one thing you'll say. When the topic comes up, read it. Prepared beats brave.

Count reps, not outcomes. Your win is that you spoke. Not that everyone loved it. Track it like a workout. Three meetings this week where you said something is a good week.

What changed for me

On the Athena project, our edge sensors ran a local model. When it flagged something significant, it shipped the context from before, during, and after the event to AWS so the models could keep learning. The system got better because it kept getting fed new examples.

That's the whole idea. Your brain is the model. Every time you stay quiet, you feed it another example that silence is safe and speaking is dangerous. Every time you speak, even badly, you feed it the opposite. Enough examples and the filter flips. The meeting stops feeling like a threat and starts feeling like a place where you have something to add.

You already have the answers. You already have the voice. It's just been hidden under old training.

Your mission this week

Compliment one stranger a day for seven days.
In your next three meetings, say something in the first five minutes.
Write down each rep. Look at the list on Friday.

Then come back and tell me in the comments how it went. Which part was hardest for you?