Twenty years in, and the engineering only gets more interesting.
I still write production code. That is the job, not a side habit I mention in interviews. I use AI to help me code, review, and ensure all my code is secure and documented; I'm not afraid to say that.
Most weeks, I design AI solutions that have to run on a company’s real knowledge: what they already know, what they are allowed to use, and what the model isn't allowed to invent. Prototype-to-production is the interesting part. I also hire, and I still take the call when a system is on fire.
What that looks like in practice:
At Keeeb I stood up a remote engineering team from zero, 15+ people across backend, AI, and frontend, then took a monolith apart into 12+ Kubernetes services and a public API SDK. The interesting part was not the org chart. It was scaling a product without turning it into a science project.
At Medullar I built the first proof of concept myself, then took a privacy-first, knowledge-powered AI platform the rest of the way: how the knowledge gets in, how the models use it with RAG, agents on top, the production path. I will happily live in that problem until the design is boring in the good way.
I also run a small studio, Luodaint, and ship my own products (Corvidly, Feedjolt, InfluCodes). I like 0-to-1. I like a team. I like AI when it changes the system, not when it is a badge on a changelog.
I am a poor fit if you want a CTO who only manages, a culture of calendar Tetris sold as speed, or a mandate to “do AI” with no opinion about the underlying product. Startup, hands-on, real problem. That is the seat.
If you are hiring a founding engineer, Head of Eng, or a fractional CTO who will still open the repo, send me a note. Coffee is fine too. I am in Terrassa; I work remotely, and I have done this from Barcelona, Dublin, and Boston.
