Essays on the parts of senior engineering and engineering management nobody writes job descriptions for — managing your own internal state, communicating without performing, asking for help on time.
The job description covers the technical work, the meetings, the deliverables. It doesn't cover the actual day-to-day: managing your own state when the pressure is on, choosing your words so a tired team hears the right signal, deciding whether to speak up now or wait, asking for help before you're stuck. These essays sit with the invisible work that nobody promotes you for — and that nobody else can do for you.
Plus… why you should stop answering questions you weren't asked
Overwhelm is treated as a personal failing — something to manage privately, push through, or apologize for. None of that is what overwhelm is actually about, and none of it is in the job description.
Read on The Complete Engineer →Hint: they are not a direct report
Managers spend their days managing other people. The one person they forget to manage is themselves — the source of every signal the team is reading.
Read on The Complete Engineer →Why I stopped filling every awkward pause
Silence used to feel like a problem to solve. It's actually a tool — one that makes room for the people in the room to bring their actual thoughts rather than their first reactions.
Read on The Complete Engineer →Quiet is read as deficient. It isn't.
The people in the room who think most carefully often speak the least — and saying that out loud changes how meetings work. Communication isn't volume; it's clarity about what's worth saying.
Read on The Complete Engineer →"Let me think about it first. I'll ask for help later." That order is exactly backward.
"Let me think about it first. I'll ask for help when I'm stuck." That order sounds right, but it's exactly backward — by the time you're stuck, you've already wasted the asking window.
Read on The ADHD Engineer →The quiet question that surfaces once the career landed.
When more productivity systems, more accountability, and more discipline aren't moving you forward.
For senior engineers caught in the loop of "is it me?" — when capable people treat internal experience as evidence of personal failure.
Subscribe to The Complete Engineer — reflective writing for senior software engineers and engineering leaders, sent when there's something worth saying.