Senior Engineer Mindset (Swizec Teller)
Book — owned. 308-page essay collection from the author’s Silicon Valley years; landing copy captured (
clippings/swizec-gumroad-com-l-vixmi.md), recommendation via @smlpth (41❤): “Simple. Actionable. No BS. Derived from the author’s wide reading and significant experience.”
The thesis
“Getting the senior title is easy — just stick around. But to be a true senior, you need a way of thinking that goes beyond the code.”
The origin story (why it exists)
2015: arrives in SV, first Senior title, 6-figure paycheck, “solving the hardest problems, writing the best code.” Three years later, first performance review — the CTO: “you’re a great programmer, the best we’ve got. Everything else, though … terrible. You’d be fired if it wasn’t for your history with the founders and the fact your immigration is tied to this job.” The best engineer on the team, failing as a senior engineer — the book is the essays from figuring out why, and the fix (now: leads multi-team initiatives, picks technologies, negotiates scope with PMs “before it becomes a problem,” +60% salary).
Reading notes
(to fill as read — chapters, quotes, disagreements)
- The failure Swizec describes is the exact gap between Patwari’s operational list and Fournier’s interpersonal one (Senior mindset): top of the technical axis, zero on everything else.
- “Negotiating scope before it becomes a problem” — same move as Varick’s audit-before-build (AI engineering) and spec-first work generally.
- Trajectory covered (solopreneur → seed stage → 100M Series B) matches COT-adjacent growth-stage chaos.
Vault kin
- Senior mindset — the note this book feeds; Patwari (scar tissue) + Fournier (force-multiplication) + Swizec (the mindset essays) = the trilogy
- Career development — job-search mechanics and growth lane