CTO at Vulpo. That means I get to figure out which problems are actually worth solving, then make sure we build them properly. I've been writing code since before it was my job. These days it's a lot of Laravel, a lot of architectural decisions, and occasionally explaining to clients why "just make it faster" isn't a ticket I can pick up. What I like about Vulpo is that we don't pretend complexity away. Every project is different, every stack has opinions, and the team actually talks about tradeoffs instead of just shipping and hoping. That's rare. What's even rarer: Vulpo actively encourages staying sharp outside of client work. Conferences, open source, writing — it's not tolerated, it's supported. That matters. If you're reading this because you want to work with us: the bar is high, the conversations are honest, and nobody will micromanage you. That's the deal.
