I wasn’t great at school, but I excelled at fiddling with computers. At 14, hacker movies got me into cybersecurity, which gave me a deep early sense of how systems actually work.

University was where I met software for real. I combined coding with a love of games, and at 19 published my first Unity title to the App Store. Seeing strangers use something I’d made was the moment that locked it in. I’ve been writing code daily since.

I started as the first engineering hire at InnTrend, an early-stage startup with an office in Beirut. I built its quality management platform from scratch to production, with full ownership of the architecture and shipping calls. Before Weaviate, I also did remote client work for companies abroad, including projects that came through Polar Stork, where I was tech lead, fully remote for a US company. I shipped 7+ web and mobile apps there, among them a VoIP tool that supported the Lebanese Red Cross through COVID-19.

At Kardinal, a young AI startup in Paris, I owned 12+ Go microservices and cut a high-volume API’s response time from 2 to 5 seconds down to under 1 second. I also open-sourced GoRabbit, a RabbitMQ integration for Go that the engineering org adopted.

At Weaviate, remote-first, I own features end to end: frontend, backend, or ops, whichever the feature needs. I take input from product, then self-organize from there: I refine a feature, implement it, maintain it, test it, fix it, and improve it. Part of that work is the open-source CLI I helped ship, which lets AI agents provision cloud infrastructure without going through the console. That responsibility sits with everyone on my team, not just me, and there’s a tech lead ahead of me.

I’m now in my tenth year, and along the way I founded The We Project, a wedding planning SaaS I built end to end: marketing site, app, admin console, and Go backend, with 10+ tagged production releases shipped in about seven weeks. I don’t wait to be told what to do. I refine what’s given to me and ship it myself. Most of what I produce today runs through Alfred, and it remembers what changed last time, so I’m not re-explaining myself every session.