Hello Reader,

Chidi was three months into his first software engineering role when this happened. A cross-functional review, twelve people around the table, a VP scanning the room for signal. The question landed on him without warning, something about the deployment cadence for a feature his team owned. It wasn’t hostile, and it wasn’t even particularly hard, but his mind emptied like a browser with too many tabs crashing at once.

He said something though he’s still not sure what. The meeting moved on and nobody corrected him, but the silence that followed was correction enough.

He replayed that moment for weeks.

Every engineer knows this feeling. You spend 90% of your time in deep work, heads-down in reviews, architecture diagrams, and debugging sessions. But people form their impression of you in the other 10%: the standup where a director drops in, the skip-level where your manager’s manager asks what’s blocking you, the hallway question from a principal engineer who just wants a quick read on something.

These unscripted moments carry disproportionate weight, and they’re becoming more consequential, not less. In an era where AI makes everyone sound articulate in writing, the live moment is fast becoming the only honest signal of how someone actually thinks. Fair or not, people will increasingly judge your capabilities by how you respond when there’s no time to edit.

Six months after that review, Chidi became the person people expected to have a clear take because he learned that the question is never really about the question.

Most questions in a professional setting are really requests for one of three things. Reassurance (Is this under control?), Guidance (What should I think about this?), or action (What do I need to do?).

Once you see this, something shifts. You stop scrambling to produce the right answer and start addressing the real need behind the words. This is the difference between junior reactivity and senior composure, and it’s available to anyone willing to practice it.

The next time Chidi got an unexpected question in a room full of people, he didn’t deflect or say I’m probably not the best person to answer that. Instead he said: From what I’ve seen on the deployment pipeline side, here’s what I can tell you.

He wasn’t claiming omniscience; he was defining the boundaries of what he knew based on his role, his access, and his direct experience. That specificity made him sound more authoritative than any hedge ever could.

This is the first principle: your specific vantage point is your value. You don’t need to know everything. You need to know what you know and speak from it clearly. Replace vague deflections with scoped authority, and you contribute meaningfully without overstating your knowledge.

Consider a junior data engineer named Amara, who found herself ambushed in a 1:1 with her skip-level manager. A question about data quality issues she hadn’t prepared to discuss. Instead of panic-answering, she said: Can you say more about which part is most concerning to you?

That single question bought her ten seconds of thinking time, surfaced the specific concern she needed to address and signaled that she listens carefully before she speaks. Her manager gave her a more focused question and she gave a more focused answer.

Now return to the VP who put Chidi on the spot in that first review. What did the VP actually want? Not a walkthrough of every deployment variable, and certainly not a status update pulled from memory. The VP wanted to know whether to escalate a risk to their boss.

Reassurance was all that was required and once Chidi started decoding questions this way, he stopped over-explaining. He started matching the length and depth of his response to the underlying need. When someone needs reassurance, give them a confident sentence. When someone needs guidance, give them two options and a recommendation. When someone needs action, give them a date and a next step.

The hardest skill in this framework, especially for early-career engineers, is the deferral. Because I don’t know feels like proof you don’t belong. It triggers something deeper than professional discomfort, touching the fear of being exposed as someone who got lucky, who shouldn’t be in the room.

But there’s a version of “I’ll get back to you” that demonstrates ownership rather than absence. The key is framing the delay as a benefit to the person asking, not a confession from the person answering.

“Let me pull the actual data so I’m not working from memory. You deserve accurate numbers. I’ll have it by Friday.”

That sentence does three things: it shows rigor, it centers their needs, and it creates a concrete commitment. It’s the opposite of scrambling. It’s composure made visible.

Twelve months after that first frozen moment, Chidi sat in another cross-functional review. Different VP, different question, same lack of warning. But this time, he scoped his answer, clarified the real concern, and delivered a two-sentence response that addressed the underlying need. The meeting moved on, and that afternoon, the VP mentioned his name in a follow-up email to his manager.

Nobody told him he’d done well, and nobody had to. The signal was already sent.

The moments that build your reputation aren’t the ones you prepare for. They’re the ones you weren’t expecting, and handle anyway.

That’s all for this week.