The Career I Built on Work Nobody Wanted
A career built on the audits, migrations, and offshore coordination nobody volunteered for, because that work maps a company fastest.
We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect
Writing · Tag
35 posts on engineering leadership, page 2 of 3. Or browse the full writing index →
A career built on the audits, migrations, and offshore coordination nobody volunteered for, because that work maps a company fastest.
What a buyer's technical reviewer checks in a reverse acqui-hire when the code isn't the asset: key-person risk, IP scope, and contribution forensics.
Commit count and PR volume are agent-inflated now. Here's what I actually evaluate in reviews, and the 1:1 questions that surface real judgment.
First-PR review, authorship transparency, and mentorship all change when half the diffs a new hire reads were written by an agent. Here's the process.
One operating system runs a team whether the teammate is a person or an agent. My blueprint: trust, pods, outcomes over hours, managing agents like interns.
My team's $200 AI coding seats consume $1,800–$3,500 of API-priced tokens a month. The 10–17x arbitrage nobody prices in, and how to budget for it.
A scared employee hands over access to avoid a manager's wrath, the exact move social engineering exploits. Why psychological safety is a security control.
What the investor's technical reviewer opens first, the AI-specific flags that re-price rounds in 2026, and the gaps you should deliberately leave alone.
Amazon mandated AI coding, let it touch infrastructure unwatched, and lost millions of orders. The fix was more humans per deploy.
A CLAUDE.md is executable tribal knowledge: the onboarding doc you never wrote for humans, finally read by something that acts on it.
The whiteboard coding interview rewards memorization and pedigree, the weakest predictors of real performance. Hire for trajectory instead.
The path to senior ran through the grunt work AI now does in one prompt. The knowing-vs-doing gap hits juniors first, and here's how to grow architects anyway.