Architecting Systems for
Async-First Environments.

I am a staunch advocate for Async-First & Distributed work. Drawing from the GitLab philosophy, I believe in Handbook-first communication; if it's not written down, it doesn't exist. This ensures that technical decisions are transparent and accessible across all timezones.

Informed by Basecamp's Shape Up and It Doesn't Have to Be Crazy at Work, I strive to build "calm" engineering cultures. This means protecting the developer's "Deep Work" by eliminating unnecessary synchronization points (M&Ms) and favoring intentional documentation over constant pings.

I’ve long admired the engineering culture at companies like Dropbox, specifically their framing of Staff-level impact through the lens of Direction and Talent. To me, this represents the vital ability to navigate high-stakes ambiguity while evaluating the long-term trade-offs between speed and reliability. I mirror this by "designing for the sync" ensuring complex systems are decoupled so distributed teams can own their domains end-to-end without constant coordination.

At the current stage of my career, my role is to "shape" the work—defining boundaries and mitigating risks before the first line of code is written, allowing distributed teams to execute with high autonomy and zero ambiguity.