Noah Labhart

You build a team that's around go to market.

And then also at the same time, you know, the implementation sort of guidelines are, how did you progress that as you found success and how did you mature it?

And I think to wrap that in a box a little bit, what I'm looking for is, you know, how you build your quote unquote roadmap and maybe for those things, but also maybe how you build the roadmap for the company.

And what do you look at to decide that, okay, this is the next most important thing to build or to address?

I'm curious about team, right?

And you mentioned on the go-to-market side, and you mentioned building a team there.

In general, I'm curious about how you build teams and what you look for in those people to indicate that they're the winning horses to join you.

This episode is sponsored by Mesmo.

If you're responsible for reliability, performance, or platform architecture, you already know the problem.

Telemetry volume is growing faster than teams can manage it.

Mesmo addresses this by moving observability upstream.

Instead of storing everything and asking questions later, Mesmo processes telemetry in motion, filtering, transforming, and enriching logs, metrics, and traces before they reach your observability backend.

The result is cleaner data, reduced ingestion costs, and faster root cause analysis using the tools you already rely on.

Mesmo integrates with platforms like Datadog, Dynatrace, and Open Source Stacks, giving teams more control without adding operational overhead.

This is especially useful for platform engineers and SREs supporting complex, distributed systems where context and speed matter.

To see how active telemetry works in practice, get a demo at mezmo.com slash codestory.

That's M-E-Z-M-O dot com slash codestory.

This episode is sponsored by Unblocked.

There's a good chance you've already tried a few AI code review tools, and you're probably ignoring most of their comments.

Not because AI can't review code, but because it's missing context.