SingleStore
Software Engineer | Observability
About this role
SingleStore is hiring a Software Engineer for their Observability Team to design and build scalable observability features for traces, logs, and metrics across their cloud-native platform. You'll work on distributed systems challenges spanning data ingestion, processing, storage, and visualization while collaborating with product and customer-facing teams.
What you'll do
- Design and implement scalable observability features for traces, logs, and metrics ingestion, processing, storage, and visualization
- Build and optimize high-throughput data pipelines using OpenTelemetry Collector and related tools to process telemetry data
- Work on control plane and data plane components across multi-cloud environments (AWS, GCP, Azure)
- Develop alerting capabilities with Alertmanager for customer-defined alerts and notification management
- Optimize time-series data storage and query performance using SingleStore DB for high-cardinality analytical workloads
- Participate in on-call rotations to ensure system reliability and respond to production incidents
What they're looking for
- Go (Golang)
- Distributed systems design and concepts
- Kubernetes
- Observability concepts (traces, logs, metrics, APM)
- Production debugging and root-cause analysis
- Cloud platforms (AWS, GCP, Azure)
- Time-series databases
- OpenTelemetry and open-source observability tools
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
SingleStore
SingleStore builds a cloud database platform that powers enterprise data solutions at scale. The company is hiring support engineers, site reliability engineers, and forward-deployed engineers to deliver technical support, optimize cloud infrastructure, and architect customer solutions.
- Website
- singlestore.com
Likely interview questions
- Describe your experience building distributed systems and how you've handled consistency and high availability challenges at scale.
- Walk us through a complex production issue you debugged—what was your approach and how did you identify the root cause?