Jobs

If you've ever tried to understand a system by staring at raw logs, metrics, or traces and felt like the data was working against you, you know the problem. If you've instrumented services only to realize later that half the telemetry is noisy, redundant, or misleading, you know the pain. The tooling is stuck. Teams are drowning in data and starving for insight. We're building a system that actually understands what your telemetry means, what's valuable, and what's waste. We're getting real pull from companies who are tired of it. They're coming to us. The problem is big, the market is massive, and we're early.

What this role is
We need someone who can own large parts of the product and ship. You'll be responsible for the systems that define how Tero is configured, how telemetry is modeled and understood, and how users interact with that understanding programmatically.

That includes:

• The control plane that models customers, environments, integrations, and telemetry semantics
• The APIs and state that coordinate analysis and system behavior
• The CLI that engineers use to explore, reason about, and act on their telemetry

There's no PM. You'll talk to users, understand what they need, figure out what to build, and build it. Ship, learn, iterate.

This is not a role where you wait for specs and stay in your lane. But it's also not chaos. We care deeply about clarity, good interfaces, and systems that hold up over time.

What Matters
You've dealt with telemetry quality problems firsthand. You've been the developer instrumenting critical services, the person trying to make sense of telemetry that doesn't connect. You've seen how bad data makes debugging slower, automation brittle, and systems harder to reason about. You have opinions about what good looks like because you've lived what bad looks like.

You have product taste. You care about the user experience, not just the system design. You understand that architecture is in service of the product, not the other way around.

You're autonomous but not reckless. You make decisions without waiting for permission. You ship and learn. But you know when to pause, ask questions, and get it right.

You're a strong engineer. Language matters less than judgment. We write Go, but what matters is that you know how to design systems, manage complexity, and make good tradeoffs. Experience across multiple languages and environments is a plus.

You can wear many hats. Deploy your own code. Debug production. Write Terraform. Talk to customers. Early stage means the job is whatever needs doing.

Why this might be for you

• Real ownership. Not ownership of someone else's roadmap. You'll decide what to build and build it.
• Real customers. Not a backlog. People using the product now, telling you what works and what doesn't.
• A team that's done this before. Experienced operators who know the difference between productive intensity and performative hustle.
• Competitive comp, meaningful equity, benefits fully covered.

Who we are
This is not a first-time founder situation.

Ben (Co-Founder) created Vector.dev, the open-source observability pipeline that Datadog acquired. Nihar (Co-Founder) was the first employee at SeatGeek and has built and scaled GTM organizations multiple times.

We're a small team, all senior. No drama. No chaos disguised as speed. We're deliberate about what matters and fast once we know what to do. Slow is smooth, smooth is fast.

We've raised from NextView Ventures, Founder Collective, the co-creator of OpenTelemetry, and other investors who know infrastructure and B2B deeply.

How to apply
Email hi@usetero.com with your LinkedIn, GitHub, personal site, or projects you're proud of. Tell us about a time you've experienced the pain of poor quality in your observability data and what you did about it (a few sentences is plenty).