The Room That Taught Me Everything
Early in my career I walked into a sprint planning meeting convinced I had the right answer. I'd spent the weekend thinking through the architecture, mapped out the component tree in my head, and was ready to present. Halfway through my pitch, a quieter engineer on the team — someone I'd honestly underestimated — raised her hand and said, "I think there's a simpler way."
She was right. Completely right. And I remember the heat of embarrassment, the instinct to defend my approach anyway, and then the slow realization that nothing she said was an attack. She just wanted to build the right thing.
That moment stuck with me more than any course or certification ever has.
What Humility Actually Looks Like in Practice
Humility in leadership isn't about being passive or underselling your experience. It's about staying genuinely open to the possibility that you're wrong — even when you're the most senior person in the room.
In practice, it looks like this:
Saying "I don't know" without hesitation. Senior engineers who perform certainty to protect their status create cultures where questions feel dangerous. When you model not-knowing openly, your team follows. People stop pretending. Problems surface earlier. You ship fewer disasters.
Attributing ideas to their source. If someone on your team suggested the caching strategy that saved the day, say so in the retro. In front of everyone. This isn't just good manners — it builds psychological safety at scale. People contribute more when they know they'll be seen.
Asking for reviews on your own code. I make it a point to request feedback on my pull requests even when I'm confident in them. It sends a clear signal: review isn't punishment, it's how we all get better. And sometimes, even on code I was proud of, someone catches something I missed.
The Technical Case for Humility
Here's the thing that often gets overlooked: humility makes you a better engineer, not just a better colleague.
When you're willing to question your own assumptions, you slow down at exactly the right moments — before you've over-engineered something, before you've painted the team into a corner with a decision that's hard to reverse. The most expensive bugs I've seen in production weren't caused by lack of skill. They were caused by someone being too certain too early.
Humble engineers ask more questions during discovery. They write better documentation because they don't assume the reader shares their mental model. They're more likely to seek out the person closest to the problem — even if that person is a junior dev who's been working the support queue — before drawing conclusions.
Humility Doesn't Mean Indecision
This is the part people get wrong. Humility and conviction are not opposites.
You can hold a strong opinion, argue for it clearly, and still remain open to being persuaded. The difference is internal: are you arguing because you believe it's the best path, or because backing down feels like losing? One of those is engineering. The other is ego.
The best technical leaders I've worked alongside could walk into a room, make a definitive call when one was needed, and then — if new information changed the picture — update their position without drama. No face-saving. No "well, what I *meant* was..." Just: the situation changed, here's where we are now.
That kind of leadership is rare. And it's magnetic.
A Note to Senior Engineers Specifically
The more experience you accumulate, the harder humility gets. You've been right enough times that the pattern-matching in your brain starts to feel infallible. It isn't.
Every new codebase is different. Every team has context you don't have yet. Every junior engineer who joined six months ago has been living inside this system in ways you haven't. Their instincts about what's painful, what's fragile, what nobody touches because it always breaks — that knowledge is gold. Go looking for it.
The best thing I ever did for my growth as a leader was to start treating "I've never seen it done that way" as a reason to get curious, not defensive.
Closing Thought
Humility is not the absence of confidence. It's confidence that doesn't need the room to agree with it.
The engineers who've shaped how I think about leadership weren't the loudest ones. They were the ones who listened carefully, gave credit freely, changed their minds gracefully, and made everyone around them better without making it obvious they were doing it.
That's the standard I'm still working toward.
