I started my career writing software for a 60-foot robotic arm that recovered an autonomous underwater vehicle off the side of a submarine. That early experience in safety-critical, real-time systems showed me how much design decisions matter when failure isn’t an option.
From there, I moved into tactical networking, where commercial assumptions break down and you have to rethink how software communicates in contested, bandwidth-limited environments. I was drawn to problems that don’t have known solutions — and software architecture turned out to be the discipline that lets me work across all of them.
The most rewarding aspect of my work is seeing research transition into real operational capability. I’ve spent over a decade designing resilient network protocols for environments where connectivity is intermittent, platforms move fast, and data exchange is mission critical.
When the software that I’ve helped design proves it can hold up under those conditions and moves closer to the hands of the people who need it, that’s the payoff. I’m also deeply rewarded by mentoring — watching engineers grow into confident technical leaders and knowing I played a small part in that.
The ww5 Technical Fellowship is where technical depth meets enterprise responsibility. It gives me a platform to raise the bar for how we build software across ww5 — through architecture evaluations, design practice standards, and lessons learned that become lasting improvements. It also connects me to a community of people who care as much about engineering rigor as I do, and who challenge me to keep growing.
The complexity of the systems we’re building is accelerating — autonomous platforms, contested communications, AI-driven networking — and software architecture is at the center of all of it. I’m excited to help ww5 navigate that complexity with strong design foundations, so we can innovate faster with less rework and more predictable outcomes. I’m also energized by the engineers coming up behind us who are asking hard questions and tackling problems in ways that build on what we’ve learned.