Engineering leader and founder.
Systems that are honest about how they work, and generous about who they work for.
I've been fascinated by how systems really work for as long as I can remember: engineering systems, people systems, and now the ones we're building with machines. Twenty years of building software and leading engineering teams, across startups, scale-ups and the public sector, taught me that the hard problems are usually about power: who gets to decide, who carries the cost, and who the system was built for. My work is to explore how people, machines, and the systems we share really work together, and to build the tools, teams, and practices that let power, care, and capacity be shared with consent and accountability.
I'm currently building Orillo, which helps software teams say yes to their agents, with proof of the human judgment behind every change. I'm also developing Consentful Leadership, a framework for what it means to design the systems people work inside with consent, transparency, and agency as structural principles.
Based in Barcelona.
Helps software teams say yes to their agents, with proof of the human judgment behind every change. Placket, its open-source recorder, goes public in October.
A leadership framework grounded in a structural claim: every leader designs the system their people work inside, and most do it by default. Consentful Leadership is the practice of doing it deliberately, with consent as a structural principle. Developed through twenty years of engineering leadership.
Capacity-first task management for people with variable energy. Built on spoon theory: the core question is "what fits within my capacity today?" not "what should I do?" No guilt, no streaks, no punishment for saying not today.
Your own notes and knowledge, brought to work on your terms: two-way, rule-governed sharing between a person and the places they work.
I'm a queer, trans, disabled, and neurodivergent engineering leader. These aren't biographical footnotes. They directly shape how I think about systems, power, capacity, and what it means to design organizations people can actually be whole inside of.
My technical background spans Python, TypeScript, React, Ruby on Rails, and AWS. My leadership experience centers on building inclusive engineering teams, mentoring engineers and managers, and designing both technical and organizational systems. I've worked at Gusto, Regard, and across early- and late-stage startups and government.
I'm interested in how AI tools are changing engineering work, how organizations govern themselves, and how the invisible structures that shape what people can do inside institutions can be made visible and intentional.
I'd like to hear from people redrawing who decides at work, between leaders and teams and between people and AI.