Customer Success Architect
Posted 5 Oct 2026
BranchFactor Summary
The original posting with the fluff stripped out
- Expected experience
- 4+ yrs
- Management level
- Individual contributor
- Employment
- Remote
- Contract
- Full-time
No salary listed for this role.
About us
OpenObserve is a fast-growing, developer-forward observability platform built for modern, high-scale systems. We help engineering teams ship faster and sleep better by making logs, metrics, and traces simpler, faster, and far more cost-efficient. A cloud-native architecture and smart indexing deliver real-time insight without the usual complexity or runaway costs.
We're backed by Nexus Venture Partners and Dell Technologies Capital. The open-source project has more than 22K GitHub stars and 10K active deployments, and our customers include some of the largest engineering organizations in the world. They choose OpenObserve to unify observability, cut spend, and speed up incident response.
Our culture is product-obsessed, customer-driven, and high ownership. We move quickly, value clarity, and give people room to take big swings.
About the role
Reporting directly to the Chief Revenue Officer, you'll own the customer's technical journey with OpenObserve, and it starts before the contract is signed. You'll work alongside sales during proofs of concept, take pilots through to full deployment, and then make sure customers get what they bought OpenObserve for and stay with us for years.
This is a technical role. Our customers are platform engineers, SREs, and DevOps leaders, many of them mid-migration from Datadog, Splunk, or Elastic. They'll expect you to understand their architecture, get your hands into the product, and have an opinion about what good observability looks like.
It's a good fit if you come from engineering, SRE, or support and have found that the part of the job you like most is working with the people who use what you build. You'll keep your hands in the technology and spend most of your week with customers. We'll coach you on the commercial side.
It is also not a support role, and the difference matters to us. Support is reactive: a ticket comes in, it gets fixed, it gets closed. Success is proactive: you know what the customer is trying to achieve, you notice when they're drifting away from it, and you act before they have to ask. You'll work closely with support and engineering and you'll own escalations, but your job isn't to close tickets. It's the outcome.
What success looks like
Twelve months in, four things are true:
-
Your customers renew, and most are sending more data than when you started. Retention and growth in your portfolio are the scoreboard.
-
Pilots become deployments. Customers who started with a POC are in full production and off their incumbent, on the timeline they were promised.
-
You see problems before the customer does. A drop in usage, a champion who left, a team that never onboarded. You caught it and did something about it.