About
I'm a full-stack software engineer with experience building and maintaining production web applications and distributed backend systems.
I work primarily with React, TypeScript, and Go, developing frontend features alongside backend services that support real-world usage. I design RESTful APIs, define clear request and response contracts, and deploy containerized workloads using Docker and Kubernetes in cloud environments on Google Cloud Platform.
In parallel, I serve as the technical founder of QuisMotion, where I lead a cross-disciplinary team working on adaptive and resilient intersection systems. My role includes defining system scope, outlining architecture, translating operational constraints into technical requirements, and coordinating across software, embedded, and infrastructure domains. I also lead stakeholder discussions with public and private sector partners to align technical decisions with operational and regulatory constraints.
A significant part of my work, both professionally and in my own projects, involves maintaining system stability. This includes debugging across distributed services, analyzing logs to isolate root causes, and validating fixes before release. I care about making systems predictable and understandable, not just functional.
I've found that clarity scales better than cleverness. Software that's easy to understand is easier to maintain, and systems built with structure tend to hold up better under pressure.
Behind the Code
I've always been curious about how systems behave in the real world, especially when something breaks. That curiosity extends beyond software into aviation, history, and the kinds of stories that look at how things hold together or fall apart.
Outside of engineering, I spend time outdoors and read frequently. I also independently study cybersecurity and embedded systems because I'm interested in how software interacts directly with hardware and larger infrastructure.
QuisMotion started from something simple. I was repeatedly late to class because of inefficient traffic patterns. Instead of just being frustrated, I became curious about how intersection systems actually worked and whether they could be improved.
What began as a personal annoyance turned into a deeper interest in how infrastructure decisions affect everyday life. Working on the project changed how I think about software, not just as code, but as something that operates in physical environments and influences real-world outcomes.
I'm currently completing my Bachelor's in Computer Science, expected summer 2026, and plan to pursue a Master's in Cybersecurity. Long term, I'm interested in working in defense or federal environments where reliability and security are practical expectations rather than abstract goals.