OpenObserve Inc. - Customer Success Architect

• The best people in this job are part engineer, part consultant, part diplomat. They can debug an ingestion pipeline in the morning and talk a frustrated VP through a renewal in the afternoon, and they're interested in both. • Has 4+ years in a technical role such as software engineering, SRE, DevOps, support engineering, or solutions engineering, and wants to spend more of the week with customers. Prior customer success or technical account management experience is a plus, not a requirement. • Has 4+ years in a technical role • Has real observability experience. You've used, run, or supported tools like Datadog, Splunk, Elastic, Grafana, or New Relic, and you have opinions about what good monitoring looks like. • Is technical enough to be credible with engineers. You're comfortable with Kubernetes, cloud infrastructure, OpenTelemetry, and log, metric, and trace pipelines. You can write SQL, read a config file, and reproduce a problem yourself before you escalate it. • Is technical enough to be credible with engineers. • Understands the difference between support and success. You don't measure your week in tickets closed. You measure it in whether your customers are getting closer to what they set out to do. • Understands the difference between support and success. • Has high emotional intelligence. You hear the frustration under a polite email. You know when an engineer wants an answer and when an executive wants reassurance. You can deliver bad news without getting defensive and without losing the room. • Has high emotional intelligence. • Is smart and curious. You want to know why something works, not just that it does. You'll dig into a customer's stack because you find it interesting, and you learn new technology fast. • Is smart and curious. • Communicates clearly, in writing and in person, with hands-on engineers and with executives. • Communicates clearly, • Has commercial sense, or wants to build it. You don't need to have owned a renewal before, but you're curious about how the business side works and can tell an expansion opportunity from a favor. • Has commercial sense, or wants to build it. • Is organized. You can run a portfolio of accounts and several evaluations and migrations at once without dropping things. • Is organized. • Thrives in early-stage environments. You're comfortable with ambiguity and would rather build the process than inherit it. • Thrives in early-stage environments.