Who I am

I also have a traditionally formatted resume.

TLDR

I am a self-taught, product-focused software engineer with over 13 years of professional experience, blending a strong engineering foundation with a deep understanding of business impact. My early career in Civil Engineering instilled a practical, system-wide approach to problem-solving, which I apply in software by designing solutions that account for the full product and organizational context. I specialize in platform infrastructure, CI/CD, and system architecture, with deep experience building scalable, observable systems that enable teams to deliver reliably. I thrive in cross-functional environments where engineering has a strategic voice and where I can influence technical direction, shape architecture, and mentor others to grow their impact. I take pride in leading through collaboration, clarity, and a commitment to high-quality, resilient software.

OK, the long version…

I didn’t start my career in software. I studied Civil Engineering with the intent to design structures—and maybe even roller coasters. After graduation, I worked on bridge and retaining wall design, using traditional engineering practices alongside light automation through custom scripts that processed CAD and survey data. But what really stood out was how inefficient the processes around me were—especially after relocating to a smaller firm in Texas.

At that company, project tracking was a weekly, four-hour meeting around a spreadsheet. It was painful—and I knew there had to be a better way. So I dusted off some PHP skills and built a basic web app that let everyone update the spreadsheet asynchronously. It was rudimentary, but transformational. Around that time, a friend introduced me to Ruby on Rails. After a few nights with the Agile Web Development on Rails tutorial, I was hooked. I realized I didn’t want to design physical structures anymore—I wanted to build software.

That realization led me to sell most of what I owned and move to San Francisco for a role at Mavenlink. There, I learned how to be a professional developer and how to collaborate on complex problems as part of a product-focused team. From there, I joined Equifax, where I worked on modernizing a legacy Rails codebase. While the enterprise environment wasn’t ideal for me long-term, it taught me how to introduce change incrementally and responsibly.

At Stitch Fix, everything clicked. I joined the warehouse engineering team and finally saw my engineering background and software skills converge. I began to approach problems with a systems-thinking mindset—considering not just the software layer, but how it connected to physical processes and real-world constraints. My contributions spanned distributed systems, operations, and robotics integration. I established coding standards and architectural best practices for Go-based services, serving as subject matter expert as the language expanded across the engineering organization. I participated in on-call rotations and eventually trained new engineers on incident response processes. Collaborating with engineers, process designers, and data scientists, I contributed to efforts that digitized and optimized fulfillment workflows, implementing observability and monitoring systems that supported operational reliability at scale.

At Framebridge, I continued leading technical initiatives that improved how the factory prepared, grouped, and shipped orders. I designed and delivered systems that combined software changes with operational process redesign, improving efficiency and reducing error rates significantly.

After a short sabbatical to recover from burnout (and remodel a bathroom), I worked with a career coach who helped me articulate what truly drives me: a deep sense of ownership and a need to work with aligned, empowered stakeholders. That realization led me to Chatkick, where I joined as the only full-time Rails engineer with 24/7 on-call responsibility. I owned the complete technical roadmap and platform infrastructure for a mature Rails application, establishing continuous deployment to improve release velocity while maintaining zero-downtime deployments. I implemented comprehensive observability and monitoring to enable rapid issue identification in production, modernized infrastructure through dependency upgrades and legacy code removal, and drove strategic technical decisions that balanced immediate delivery with long-term system stability—all while collaborating closely with the founder/CEO. Despite the startup’s early end, it was a defining experience in technical autonomy and complete platform ownership.

Most recently at Sera Systems, I led technical architecture and platform development on a high-performing team. I assisted with implementing continuous deployment from existing CI infrastructure, accelerating release cycles while maintaining system stability. I partnered with frontend leads to co-design system architecture, designed scalable REST API patterns that improved both developer experience and system performance, and built mission-critical systems for time tracking and regulatory compliance. I implemented comprehensive observability and analytics for business intelligence on customer feature adoption. Through code reviews and internal technical presentations, I mentored junior engineers and shared architectural insights across teams. I found deep satisfaction in contributing both through code and by amplifying the work of those around me.

Across all of these roles, I’ve gravitated toward positions of technical leadership—whether formal or informal. I work best when I have a seat at the table, collaborating with others who care deeply about building something excellent. I bring a wide lens to problem-solving, grounded in experience, empathy, and a commitment to delivering high-quality, resilient software that moves the business forward.