What a CV doesn't say
A CV lists what you can do. This one lists the rest. One page, no more.
Maintain code at scale. I build with an AI and I review what it produces. But I'm not a developer: production that has to hold is their craft.
Work without data or the field. Without insights, it's guesswork. And guesswork is expensive.
Execute without understanding. I ask my questions first: once the why is shared, I commit fully, even when the call doesn't go my way.
Stay in my lane. My job is building bridges between teams, while respecting each craft.
Magic AI. It improves a process or an experience when it brings value. It won't transform a product on its own, and it won't replace a team.
Meetings without output. A meeting is justified by what comes out of it: a decision, a deliverable, a call.
40-slide decks. When a clickable prototype and three slides of context are enough.
Saying yes to please. An honest no at the start beats a polite failure at the end.