I am a Virginia-based software engineer who likes building practical systems where software, infrastructure, security, and people all have to work together.
My path into software started early, but it became serious in the day-to-day work of a family SaaS and payment-processing business. I learned technology from the ground up: customer-facing forms, internal tools, networking, servers, migrations, security scans, scripts, and the messy operational details that decide whether software is merely finished or actually useful.
Today I work as a software engineer focused on backend services, APIs, tests, and maintainable application code. I am comfortable moving between Java and Spring Boot, Python and Django, C# and .NET, SQL databases, Docker, Nginx, and the Linux environments that host the work. I care about clean code, but I care even more about whether the system is reliable, understandable, and safe for the people depending on it.
The projects in this portfolio reflect that bias toward useful engineering. I have built employee portal tools, an auditable AI chat application, privacy-consent workflows, REST APIs, an Android-to-web SMS bridge using WebSockets, and infrastructure for an online community that grew to hundreds of members. Different stacks, same pattern: find the real workflow, understand the risk, and make the tool easier to trust.
I bring a builder's curiosity, an operator's respect for production, and an Eagle Scout's habit of taking responsibility for the outcome. I like code reviews, documentation, testing, clear communication, and infrastructure choices because those are the places where long-term quality usually gets decided.