Where cutting-edge

AI research meets

world-class engineering

Why did you join Traversal?

I believe in Traversal’s ability to deliver a compelling solution to a complex problem. It’s like the first time cooking with sharp knives — initial shock, followed by satisfaction, and then the expectation of always wanting the best tools. This is a similar epiphany. And the team is a mix of unique perspectives and backgrounds, all passionately pursuing the same vision — and they’re funny people. What’s not to love?

What is the worst incident you handled before Traversal?

I was at a trading firm ~1 year into my post-grad career and responsible for critical overnight jobs written 13+ years earlier in nested SQL stored procedures. The week that my senior eng was OOO, these jobs started failing at 5am, leading me to work around the clock to patch data from the trading day, look into root causes and repeat until identifying the bug. That week burnt me out, and I learned how crucial it is to have every advantage in debugging critical issues.

Why did you join Traversal?

I joined Traversal to work alongside a world-class team addressing one of the most challenging and important problems in the industry: diagnosing and resolving production incidents.

What do you like most about working for Traversal?

The people here are not only some of the smartest I've had the chance to work with, but also some of the nicest and funniest. Every day in the office is a pleasure, and getting to work on such a hard and exciting problem at a place like this is amazing.

Why did you join Traversal?

Incident response is an incredibly compelling application of agentic AI. Throughout the interview process, I was struck by the team's generosity, humility, and passion, and knew that this was the right group of people to tackle such a critical problem.

What do you like most about working for Traversal?

Everyone here is genuinely excited about the problem we’re solving and the feeling is contagious. Every day feels fun and there’s a real sense of momentum around reimagining software reliability.

What is the worst incident you handled before Traversal?

In my OS class, I was building a thread library in C++ when a single = instead of == caused segmentation faults that seemed completely random. Since assignment inside a condition is valid C++ (and usually evaluates to true), the compiler stayed silent — leaving me chasing what looked like a nondeterministic bug in a multithreaded program.

Why did you join Traversal?

Helping organizations ensure continuity for their customers is what drives me — there’s no such thing as too fast when diagnosing and fixing production issues. Traversal’s blend of causal inference and LLMs is the most promising way I’ve seen to help teams turn their observability data into real reliability.