The Architect

Nearly a decade of experience moving between three closely related roles, often at once, always in regulated, high-stakes environments. As a technical leader, that means serving as the primary technical authority across business, engineering, and academic stakeholders — defining standards and mentoring teams through full project lifecycles. As a backend engineer, it means building high-performance, production-grade systems: scalable APIs, event-driven data pipelines, and distributed services in Java, Spring Boot, Python, and cloud-native infrastructure on Google Cloud Platform. As a systems architect, it means transforming intricate business logic and legacy monoliths into decoupled, cloud-native platforms with zero-downtime resilience, provisioned as Infrastructure-as-Code.

The throughline across all three is the same discipline: define the boundaries, secure the contracts, build what holds — then teach it. That same discipline now extends to modern practice, guiding the adoption of LLM/SLM capabilities into production pipelines.

Guatemalan. Disruptive by practice. Precise by necessity.