About

I spent the first decade of my career on the side of technology most developers only meet when something is already broken: a support ticket, a compromised account, a server that needs to come back up before anyone notices it went down. I started as a support intern at a regional electoral court, keeping biometric voter-registration hardware running for a few hundred users a month. From there I moved into infrastructure and support at an IT services company, then into leading it: three years managing a security and support team, owning incident response, vulnerability management, and access policy, with a downtime rate I kept under 1% the whole time I tracked it.

That background keeps shaping how I build now that I write software for a living: it’s the reason a case like Knoxis reaches for a schema-level guarantee instead of a policy nobody enforces, and the reason FunilChat AI’s tenant isolation lives in a database policy first, an application check second. Security and infrastructure work teaches a specific kind of paranoia: assume the check you didn’t write is the one that gets skipped. That instinct carries directly into how I build.

The shift into hands-on development happened over the last two years, alongside a Bachelor’s in Software Engineering (UNIASSELVI, 2025), while working through exactly the kind of unglamorous integration work that teaches a language fast: connecting dashboards to client-owned ERPs, matching numbers across systems that were never meant to talk to each other, building a classroom platform from a teacher’s actual constraints instead of a clean spec.

I’m looking for full-stack developer roles, remote, any time zone, where a security- and infrastructure-literate developer is a real asset rather than a nice-to-have: systems that touch sensitive data, integrate with infrastructure I don’t control, or need someone who has actually been on call for the thing they’re building. The six cases on this site are the evidence; the résumé below is the same story in the shape a recruiter can file.

Interested in a project like this? Get in touch.

Get in touch