Where it started
Before backend APIs, I was the kid wiring sensors to robots. I studied mechatronics engineering and graduated with two research projects instead of one: an FPGA emulation of the Deutsch–Jozsa quantum algorithm, and a CNN that let a physical robot navigate autonomously.
The lesson I didn't know I was learning: hard problems are usually just unfamiliar math plus unfamiliar tooling. Production systems turned out to be the same thing, with more Slack channels.
The climb
At CODE Exitos I went from developer to Tech Lead in two years, then Engineering Manager reporting to the CTO in three. I led 12 engineers building platforms for Wendy's, Takeda, Stellantis and Sifera.
My favorite project was steering a legacy monolith into microservices — fewer 3 AM pages, 40% less downtime. I also brought in GitHub Actions + Docker pipelines that cut deployment times by 30%. Boring on purpose. Reliable in practice.
Now
Today I'm Lead Software Engineer at FortressOS — promoted from Senior within 14 months. I lead a cross-functional team of 5 developers and 2 QA engineers, and I sit at the bridge between product and engineering: sprint planning, live stakeholder demos, translating 'business ask' into 'clean architecture'.
Since taking over, sprint delivery went from 86% to 94% and team velocity from 6.5 to 7.8 points per sprint. I still personally ship 8.3 points per sprint at 96% completion across five shipped internal projects — leading by example isn't just a phrase, it's a commit history.
There's a version of my story that isn't in the résumé: the open-source packages with steady weekly downloads, the merged NestJS docs PR, the president-of-the-student-association era, and the food adventures I mention whenever someone asks about Honduras. Keep scrolling — or jump to the résumé.