Writing
04 · 9 June 2025 · 1 min read
What large organisations actually need from engineers
It's not cleverness. It's judgment under constraints.
Large organisations don't fail for lack of clever engineers. They fail because cleverness is the wrong currency once the system has real constraints: regulation, legacy systems, politics, money already spent, and a production estate that can't just be paused for a rewrite.
What they actually need is judgment under those constraints. The ability to spot which problem is load-bearing, which abstraction is quietly becoming a trap, and which "modernisation" is just a more expensive way of keeping the same mess.
Cleverness is cheap. Constraints aren't.
A brilliant design that can't be operated by the people who inherit it isn't brilliant, it's a liability with good documentation. A migration that ignores the settlement, tax, or safety path isn't really a migration. It's a demo with a blast radius.
The engineers who end up indispensable in these environments are rarely the loudest voice in a design review. They're the ones asking what happens when the vendor is late, when the data is wrong, when two systems that are both supposed to be the source of truth disagree with each other, when the one person who understood the system finally leaves.
The real work is translation
You're constantly translating between what the business thinks it bought and what the system can actually do. That takes technical depth, and a refusal to hide behind jargon when the honest answer is uncomfortable. It also takes the humility to keep the software smaller than the organisation's actual ability to run it.
If you want to be useful at that scale, stop optimising for elegance in isolation. Optimise for decisions that still look right after they've made contact with operations, audit, and time.