San Antonio, Texas
I build engineering teams and the systems they deliver. With 18 years across financial technology, ecommerce, and enterprise platforms, I focus on the intersection of sound architecture, regulatory complexity, and the kind of technical leadership that makes teams and products better.
About
My career started writing PHP at a small web agency and evolved into nearly two decades of building increasingly complex systems. Today I serve as a Lead Software Engineer and Program Technical Lead at USAA, responsible for technical direction across multiple agile teams and a portfolio of over 24 applications in the real estate and mortgage technology domain.
Over the past six years at USAA, I have led enterprise modernization programs, driven FFIEC compliance architecture across entire application portfolios, and delivered measurable outcomes — from eliminating $250K in annual vendor costs to archiving 15 years of mortgage data to Snowflake. In 2025 I simultaneously led two teams across entirely different technology domains, forming a brand-new Salesforce engineering team from the ground up while stepping in mid-year to keep critical mortgage initiatives on track for a second team.
Before USAA, I spent nine years at Jane Iredale growing from junior developer to the company's de facto technical lead — introducing CI/CD, Docker, automated testing, and a full B2B wholesale platform that touched payment processing, shipping logistics, and international tax compliance.
Outside of work I lead San Antonio's Hour of Code effort as the NISD STEM liaison, bringing coding education to thousands of students across local schools each year.
Skills
Contact
I take on select freelance and consulting engagements — particularly in financial technology, API integration, system architecture, and engineering process improvement.
Whether you need a technical lead for a project, an outside perspective on your architecture, or hands-on development in a complex domain, I'm happy to have a conversation about what you're building.
LinkedIn is the best place to start.
Me Personally
I tend to think in systems — which probably explains why I ended up in software, but also why I find myself drawn to problems that don't have obvious solutions. Whether it's an architecture decision at work or figuring out the right brushstroke in a painting, I'm most engaged when I'm figuring something out from first principles.
Continuous learning isn't something I do because my job requires it. It's just how I'm wired. I'm currently working through Japanese (slow and humbling in the best way), picking up Go as a language, and always have something in progress — whether that's a certification, a side project, or just something I got curious about and couldn't leave alone.
I believe the best engineers are curious about the world outside their IDE. The ability to explain a complex system simply, to see patterns across domains, to stay patient when something isn't working — those come from a life lived beyond the terminal.
Every year I lead San Antonio's Hour of Code effort as the NISD STEM liaison — coordinating volunteers, working with teachers, and bringing coding into classrooms that might not otherwise have access to it. I show up every year because I genuinely believe that the earlier a kid realizes they can build things with a computer, the more possibilities open up for them.
This isn't separate from my engineering career — it's the same instinct. The same reason I stay late to walk a junior engineer through a problem instead of just fixing it myself. Mentorship is how knowledge compounds. One person who gets it will teach ten more.
I serve as the direct liaison between NISD and volunteer coordinators, handling logistics, school communication, and on-the-day facilitation across multiple campuses each year.