Hey, I'm Oto.

I build software systems and the teams around them. Most of my work is about making things simpler than they were before — fewer services, clearer ownership, less friction. I think the best technical leaders make themselves unnecessary, and that's how I operate.

Systems That Last

I care more about how a system behaves in year three than how it looks in week one. Good architecture is mostly about saying no to complexity you don't need yet.

Teams That Own Their Work

The people closest to the code usually know what needs to happen next. My job is to give them the room, the context, and the trust to act on it.

Alignment Over Process

Most delivery problems are actually communication problems. I'd rather spend an hour getting everyone in the same room than a month managing the fallout of a misunderstood requirement.

Principal Architect at Ximedes, where I lead architecture across fintech and faretech products — payments infrastructure for banks, transit systems for public transport operators. Teams range from 5 to 15 depending on the project. Most of my time goes into cross-team technical alignment and making sure architecture decisions actually stick in practice.