Josh Sauer
Sr. Network Engineer, Lynden Inc.
Runs Fortinet in production and leads DiagDebug Puget Sound. Josh is the reason this exists: he asked for the room.
About
There was no local place for Fortinet engineers to compare notes in person, so we started one. It worked well enough that we wrote down how, so other cities can do the same.
The idea came up in 2026, when Josh Sauer, a network engineer running Fortinet in production, asked why the Puget Sound had no user group for the people who actually run this gear. Josh and Tanner Harrison started one. That's DiagDebug Puget Sound, chapter one.
Rather than keep it to one city, we wrote down how it runs: a short set of policies, a code of conduct, a playbook, and a way for any metro to start a chapter. Spokane, Portland, Boise, and Salt Lake City are forming now and looking for local leaders, which is the honest answer to "how big is this."
Founders
Sr. Network Engineer, Lynden Inc.
Runs Fortinet in production and leads DiagDebug Puget Sound. Josh is the reason this exists: he asked for the room.
Sr. Enterprise Sales Engineer, Fortinet
Handles venues, speakers, and the connection to Fortinet's product and engineering teams. Yes, he works for Fortinet. That's how the food gets paid for.
How it's run
The founders approve new chapters, keep the network policies, and maintain the site and the shared calendars. Each chapter has two to five local leaders who choose the topics, the speakers, the venues, and the cadence.
Chapter leaders also meet once a quarter as an advisory group to compare notes and shape what the network does next. Customers who run Fortinet at their own organizations always make up at least half of a chapter's leaders.
Fortinet's role
Fortinet supports DiagDebug, and one of the founders works there. We'd rather tell you that up front than have you work it out from the catering.
House rules
Everything else, from how many leaders a chapter needs to when a chapter goes inactive, is in the network policies. Everyone who takes part follows the code of conduct.
Questions? Email hello@diagdebug.com. Every message gets a reply within a week.
Read the policies, then fill out the short form. It's a conversation, not an interview panel.
Start a chapter