What did you learn going from engineer to director?

That the argument changes shape but the detail still matters. I joined Rapha as a senior frontend freelancer in April 2018 to deliver the new platform, went permanent that November, and have since been Lead Frontend Engineer, Principal Engineer, Head of Engineering and now Director of Technology. Each step widened the remit. The thing I did not expect was how much of the job became translation: turning technical detail into a decision the business can make.

As an engineer I argued from correctness. As a director I argue in commercial terms: cost, forecast and return are part of the case, not an appendix to it. That is not a softer standard. It is a harder one, because a technically sound idea that nobody adopts is a failure. I would rather make a pragmatic call than gold-plate, and I am comfortable saying "good enough" is the right answer when it is.

No, and I chose not to. I still write and deploy production code and run releases, and I lead from inside the detail rather than above it. That is how I understand the business well enough to support it properly, and it keeps my judgement on architecture grounded in what the systems actually do. The remit is broad for the title, so I prioritise hard. Staying close to the code is one of the things I have decided is worth the time.