The Engineer Who Learned to Lead - Then Wrote the Manual
The plan was academia. James Stanier finished his PhD in compiler design at the University of Sussex and looked at the postdoc landscape. What he found there changed everything. The opportunities weren't materializing the way he'd imagined, so he did what any pragmatic engineer does: he pivoted. He joined a small startup in the same town he'd been studying in. That company was Brandwatch.
What followed was not a clean career arc. It was something messier and more interesting - a decade spent figuring out, in real time, what it means to stop writing code and start building the conditions for other people to write better code. Stanier rose from backend engineer to Senior Vice President of Engineering as Brandwatch grew through three rounds of VC funding and ultimately sold to Cision for $450 million. He's quick to describe the shift to management as "an accident, kind of an opportunity, and kind of an interest all rolled into one." That kind of self-aware candor runs through everything he does.
Along the way, he noticed something that bothered him: the resources available to new engineering managers were thin. Technical people were being promoted into people roles with almost no support structure. The industry expected engineers to figure out management the same way they figured out algorithms - alone, under pressure, hoping for the best. Stanier decided to do something about it. He started writing.
Writing is the process where difficult ideas form. It's a back-and-forth game with the paper.
- James StanierThe blog came first. Then the newsletter. Then Pragmatic Programmers came calling. Become an Effective Software Engineering Manager appeared in 2020, just as the world was rethinking what office work even means. It hit a nerve. The book structured what new managers actually needed to know during their first year - not abstract principles, but concrete tools. Calendar management. Meeting cadences. How to delegate without abdicating. How to give feedback without it feeling like an ambush.
Two years later came Effective Remote Work - timing that felt almost inevitable given what 2020-2022 had done to every assumption about where work happens. Remote work wasn't new to Stanier. He'd been practicing it for years, writing from Cumbria in the Lake District while leading teams across time zones. The book wasn't theoretical. It was lived experience wrapped in a framework.
In September 2021, Shopify hired him as Director of Engineering. The scale changed dramatically. He went from running an organization through an acquisition to leading hundreds of engineers across major strategic initiatives at one of the world's most watched e-commerce platforms. Three and a half years later, he emerged with the material for book three.
Become a Great Engineering Leader, published in September 2024, targets a different audience than his first book. Not new managers trying to survive their first year - but directors, VPs, and CTOs trying to operate at organizational scale. The three levels of warfare framework appears here: tactics at the manager level, operations at the director level, strategy at the VP and CTO level. It's a serious book for serious people who've already cleared the early hurdles and are staring at the harder ones.
In April 2025, Stanier stepped into a new chapter: CTO for the veterinary division at Nordhealth. The move has a characteristically practical logic to it. Healthcare technology, meaningful domain, a focused unit where technical leadership can create real change. A PhD who started with compilers is now pointing technology at animal care. The distance between those two things says something interesting about what an engineering career can actually look like.
Through all of it, The Engineering Manager newsletter has kept publishing. Nearly 30,000 people receive his thinking on a regular basis - a number that says less about his marketing instincts and more about the genuine scarcity of clear-eyed, experience-based writing on what it actually takes to run engineering organizations well. The tone is direct. The advice is actionable. And when he's uncertain, he says so.
Enabling and helping others do a great job is really satisfying. The technically competent manager is rarer than people think - and that scarcity creates opportunity.
- James StanierAsk him for the one book a new manager should read and he'll give you Andy Grove's High Output Management every time. Not because it's perfect - but because it's honest about what management actually is: an activity, not a status. Grove's formulation that "the output of a manager is the output of the manager's team plus the output of the organization they influence" runs through Stanier's work like a spine. It's the sentence he quotes most often because it's the sentence that changed how he understood his own job.
His working habits are deliberate to the point of being slightly remarkable. He batches meetings, protects stretches of uninterrupted time, practices inbox zero by checking email only three or four times a day, and keeps what he calls a capture notebook for the ad-hoc information that would otherwise evaporate. These aren't productivity hacks borrowed from someone else's blog. They're the operational systems of someone who took Grove's output formula seriously and built a personal infrastructure around it.
There's a concept Stanier calls "Mount Stupid" - the place where talented junior engineers undersell themselves due to imposter syndrome, while distant senior leaders overestimate their own grasp of the details. He uses it to describe why good decisions are rarer than they should be. The fix, in his view, is closing the gap: senior leaders staying connected to the technical reality, junior people being given the psychological safety to say what they actually see.
Authenticity is a word he reaches for frequently, and not in the corporate-speak way. He means it literally: that manufacturing a management persona is counterproductive, that the people reporting to you can tell the difference, and that trying to be a different version of yourself in a leadership role is exhausting and unnecessary. His own voice is the proof of that argument. There's no performance in how he writes or talks. Just a person who found that thinking carefully about something and then writing it down is, surprisingly, the best way to figure out what you actually believe.