Engineering Leadership
Going from staff engineer to manager was about 90% the same job. I was already a manager in denial: leading a hundred-plus engineer platform org meant influence without authority long before it meant headcount. The title changed; the work, mostly, did not.
The lessons that travel are unglamorous. Mandates fail and examples win. Remote is better for deep work if you design for it. The best frameworks come from product engineers, not platform teams handing down abstractions. And in the AI era the fastest way to get leadership wrong is to measure adoption by the wrong number and reward tokenmaxxing instead of outcomes.
Most of leadership is systems of people, run with an operating rhythm and honest cut lines, kept human. The posts below are what that has actually looked like across Google, Reddit, and Dropbox.
Reading path (16 posts)
- Adopt the Agent. Build the Loop. -- Everyone is debating Cursor vs Claude Code. Wrong fight. The agent is a commodity. The only thing worth building is the loop around it.
- Tokenmaxxing Is What Happens When You Measure Wrong -- Mandating AI tool usage is correct. Measuring it is a trap. The right move is to measure outcomes, not inputs.
- Relaunching This Blog for the AI Era -- Jeff Adler's engineering blog, eight years of iOS architecture and leadership. Now relaunching for the AI era.
- The Year the Agent Stopped Being a Demo -- 2025 was the year agents went from demo to operational. Some 2024 predictions held. Some didn't. Three bets for 2026, and the gap that hasn't closed.
- AI Is Redefining What \"Senior Engineer\" Means -- Senior engineer used to mean better code. AI is redefining it to mean system design, taste, and judgment. A Dropbox director's take.
- What Two Years of Agentic Coding Did to My Org Chart -- Sixteen months after the agent-managers thesis, here's what actually happened to my org chart. Some held up. Some didn't. Hiring shifted hardest.
- AI Makes You 3x Faster, Then Review Explodes -- AI tools help Dropbox engineers ship 3-5x faster, but without the right processes you just create a traffic jam at code review.
- Engineers Are Becoming Agent Managers -- AI is flattening the engineering output curve at Dropbox. Engineers are managing agents now. Org structures need to change.
- Staff to Senior Manager: 90% the Same Job -- I went from Staff Engineer to Senior Engineering Manager at Dropbox in three months and was surprised how much I was already doing.
- Shipping AI When Nothing Works Yet -- The messy reality of shipping LLM-powered features at Dropbox with real users, real latency budgets, and a cost model that doesn't work.
- Mandates Fail, Examples Win -- Scaling engineering practices to a large iOS org. Why mandates fail and consistency comes from tooling, not enforcement.
- The Best Frameworks Come from Product Engineers -- The best mobile frameworks come from product engineers solving their own problems at Dropbox, not platform teams building in a vacuum.
- A Year of Remote Engineering, Now What -- Twelve months ago I said remote was better for deep work but worse for everything else. A year of data later, the take mostly held, with two things I got wrong.
- Remote Is Better for Deep Work -- Remote is more productive for deep work at Dropbox. In-person unlocks everything else. CI/CD becomes your most important teammate.
- Acquisition to App Store in Three Months -- How my team at Dropbox shipped HelloSign Mobile in three months post-acquisition by finding the right boundary between web and native.
- The Declarative Skeleton That Cut Code by ~40% -- How I built a declarative app skeleton that eliminated boilerplate, cut code substantially, and made test coverage a byproduct of good architecture.
Frequently Asked Questions
How different is the jump from staff engineer to engineering manager?
Jeff Adler argues it is roughly 90% the same job: a tech lead for a large org is already practicing influence without authority, so the transition is more continuous than it looks.
How should engineering leaders drive change?
Through examples rather than mandates. Top-down mandates tend to fail; demonstrated wins that others want to copy tend to stick.
More topics: Agentic Engineering | iOS Architecture at Scale | All posts | About Jeff Adler