Where cutting-edge

AI research meets

world-class engineering

Why did you join Traversal?

When I left Grafana in 2024, I told myself that AI-native companies would emerge over the coming years to disrupt the Telemetry Industrial Complex and if given the opportunity, I'd pursue a role in one of those firms. Traversal is the best positioned and resourced company to win this race...

Why did you join Traversal?

I’ve watched great engineers lose days stitching together raw telemetry during incidents. In a previous role building an identity threat investigation agent, I saw teams spend days reconstructing what actually happened because signals were scattered across auth policies, device context, and user behavior logs — with no single system showing the full picture. I joined Traversal because we’re building the reasoning system that should have existed in the first place — not just layering AI onto dashboards, but helping engineers make sense of complex systems.

Why did you join Traversal?

As a former practitioner, I know how tough it is to tackle this challenge at scale—and do it consistently. That’s why I’m so excited about what we’re building at Traversal. It’s a real breakthrough that will help organizations deliver more reliable results for their customers while enhancing the everyday experience of their employees.

Why did you join Traversal?

I’m most passionate about products that I would personally be excited to use daily. As a developer, I would love a product that automates tedious root cause investigations of tons of logs and code changes. Traversal already tackles this with incredible accuracy, and I’m confident that their highly talented team and research-first approach will push the product’s capabilities even further.

Why did you join Traversal?

Traversal passed my 3 criteria with flying colors: high talent density... solving an ambitious problem with AI... working shoulder-to-shoulder in NYC. (Plus lunch!)

What is the worst incident you handled before Traversal?

A few years ago, I implemented query queueing for a Trino gateway. I wrote a full test suite — including load tests — and felt confident going into production. A few days after release, most analytic workloads were stalled or failing, and there wasn’t an easy rollback path. It turned out to be a race condition involving Redis. An eventful week.

Why did you join Traversal?

It’s a fast-moving space — I like competition, and I believe we have the edge. I’m familiar with and deeply interested in this industry (ex-SignalFx/Splunk), excited about the product vision, and really hit it off with the team. The timing for disruption feels uncanny. This is my sixth startup, and I thrive in the 0 → 1 (and beyond) phase — here for the chaos, the fun, and the camaraderie.

Why did you join Traversal?

Because it marks a fundamental category shift — from observability dashboards and correlation to machine reasoning grounded in causal inference. Built by exceptional technical founders and launched at precisely the right technological inflection point, Traversal is redefining how enterprises understand and operate complex systems.

Why did you join Traversal?

I joined Traversal because it’s tackling a critical challenge for engineering teams, improving how incidents are identified, managed, and ultimately resolved. Honestly, getting the chance to build growth again alongside Nick Billy made the decision even easier.