Not a manager of engineers.
A translator of systems.
[Your name] is a technology executive with deep roots in engineering and a track record of operating at the intersection of architectural strategy and business outcomes.
Replace this paragraph with your career narrative. Speak to the systems you've built, the organisations you've scaled, and the business outcomes you've driven. This is not a job description — it's a positioning statement for the level you're operating at.
The second paragraph goes here. Keep it grounded in specifics: industries, scale (teams, revenue, infrastructure complexity), and decisions you owned — not committees you participated in.
"The role I play isn't technical lead or business partner. It's the structural layer that makes both sides of that equation function."
Third paragraph — your operating philosophy. Why you think the way you do about technical leadership. What you've learned that most people in your domain get wrong.
Clarity over consensus
Good decisions aren't made by committee. They're made by people with enough context to take a decisive position and defend it.
Systems, not symptoms
Most engineering dysfunction is an organisational problem wearing a technical mask. Fix the structure, fix the output.
Translation is the job
If leadership can't understand the engineering reality and engineering can't understand the business priority — that's a leadership failure, not a communication one.