1

Elasticsearch Observability Engineer Jobs in San Ramon, CA

Has shipped on top of Elasticsearch, OpenSearch, Vespa, Algolia, vector databases, or a custom IR ... TypeScript/Node.js proficiency; comfortable with observability tooling (Datadog, Sentry ...

Has shipped on top of Elasticsearch, OpenSearch, Vespa, Algolia, vector databases, or a custom IR ... TypeScript/Node.js proficiency; comfortable with observability tooling (Datadog, Sentry ...

In addition to our successful database business, we're building the industry's first observability ... Spark, Presto, ElasticSearch. * A history of open-source contributions is a plus; being a ...

In addition to our successful database business, we're building the industry's first observability ... Spark, Presto, ElasticSearch. * A history of open-source contributions is a plus; being a ...

In addition to our successful database business, we're building the industry's first observability ... Spark, Presto, ElasticSearch. * A history of open-source contributions is a plus; being a ...

Data Platform Engineer

San Francisco, CA ยท On-site

$200K - $400K/yr

Improve observability, tooling, and developer experience for data, ML, and agent systems. What You ... Deep experience in technologies like PostgreSQL, Redis, Celery, Temporal, ElasticSearch or ...

Senior Software Development Engineer

San Francisco, CA ยท On-site

$144K - $190K/yr

... our observability and security stance, and increasingly the agentic tools that transform how our ... SageMaker, Kubernetes GPU platforms); search-engine internals (OpenSearch/Elasticsearch, vector ...

Showing results 41-60

Elasticsearch Observability Engineer information

What does an Elasticsearch Observability Engineer do?

An Elasticsearch Observability Engineer is responsible for designing, implementing, and maintaining observability solutions using the Elasticsearch stack (Elasticsearch, Logstash, Kibana, and Beats). Their primary role is to ensure that systems are monitored effectively, logs and metrics are collected and analyzed, and issues are detected and diagnosed quickly. They collaborate with development and operations teams to build dashboards, set up alerts, and optimize performance for monitoring infrastructure and applications. These engineers play a key role in improving system reliability and supporting incident response.

How does an Elasticsearch Observability Engineer typically collaborate with development and operations teams?

As an Elasticsearch Observability Engineer, you frequently partner with both development and operations teams to design and implement monitoring solutions using the Elastic Stack. You'll help developers instrument applications for better traceability and support operations in troubleshooting and optimizing system performance. Regular communication is key, as you'll often lead workshops, create dashboards, and respond to incidents collaboratively. This cross-functional teamwork ensures observability solutions align with organizational goals and provide actionable insights.

What are the key skills and qualifications needed to thrive as an Elasticsearch Observability Engineer, and why are they important?

To thrive as an Elasticsearch Observability Engineer, you need expertise in Elasticsearch, log management, and data analysis, often supported by a degree in computer science or a related field. Familiarity with observability tools such as Kibana, Logstash, Beats, and experience with cloud platforms and scripting languages like Python or Bash are typically required. Strong problem-solving abilities, attention to detail, and effective communication skills help you stand out in this role. These competencies are vital for ensuring system reliability, quickly detecting issues, and delivering actionable insights for continuous improvement.

What is the difference between Elasticsearch Observability Engineer vs Elasticsearch Developer?

AspectElasticsearch Observability EngineerElasticsearch Developer
Primary FocusMonitoring, logging, and observability of Elasticsearch clusters and related systemsDeveloping, customizing, and optimizing Elasticsearch applications and integrations
Skills & CertificationsKnowledge of Elasticsearch, Prometheus, Grafana, scripting, and monitoring toolsProficiency in Elasticsearch APIs, Java, REST, and development frameworks
Work EnvironmentOperations teams, DevOps, SREs, cloud environmentsDevelopment teams, software engineers, backend developers

While both roles require expertise in Elasticsearch, the Elasticsearch Observability Engineer focuses on system monitoring and ensuring Elasticsearch health, whereas the Elasticsearch Developer concentrates on building and customizing Elasticsearch-based applications. Their skills and daily tasks differ, but both are essential in Elasticsearch-centric environments.

What are popular job titles related to Elasticsearch Observability Engineer jobs in San Ramon, CA?

For Elasticsearch Observability Engineer jobs in San Ramon, CA, the most frequently searched job titles are:

What job categories do people searching Elasticsearch Observability Engineer jobs in San Ramon, CA look for?

The top searched job categories for Elasticsearch Observability Engineer jobs in San Ramon, CA are:

What cities near San Ramon, CA are hiring for Elasticsearch Observability Engineer jobs?

Cities near San Ramon, CA with the most Elasticsearch Observability Engineer job openings:

Infographic showing various Elasticsearch Observability Engineer job openings in San Ramon, CA as of August 2026, with employment types broken down into 90% Full Time, 7% Part Time, and 3% Contract. Highlights an 86% Physical, 5% Hybrid, and 9% Remote job distribution.

Product Engineer, Search

NxT Level

San Francisco, CA โ€ข On-site

Full-time

Posted 10 days ago


Job description

About this role

We are looking for a Product Engineer (Search) with 3–12 years of experience to own our client's developer-facing search endpoint — closing the gap between retrieval and ranking research and what developers actually feel in the API. You'll be the single person who takes a ranking improvement from research and ships it as a live, polished developer experience in days, not sprints. No PM, no hand-holding — just you, the product, and a fast-moving team building infrastructure for the AI era.

What will you be doing?

  • Own the search API end-to-end — response format, latency, error handling, filtering, and docs — as the sole accountable person for how it feels to developers.

  • Translate retrieval and ranking research wins into shipped product changes developers notice (think: 200ms latency improvements, better recall/precision tradeoffs).

  • Dogfood the API relentlessly — read every GitHub issue and Discord thread touching search and fix friction before users have to ask.

  • Run fast product experiments: form a hypothesis, instrument it, ship it, measure it, and decide quickly with imperfect data.

  • Define what good looks like independently — no PM to scope tickets; you set the priorities and own the outcomes.

Key Requirements

  • Production search experience (retrieval, ranking, relevance) at a developer-facing company — this is a hard requirement, not a nice-to-have.

  • Has shipped on top of Elasticsearch, OpenSearch, Vespa, Algolia, vector databases, or a custom IR stack, and owned an externally consumed search API.

  • Can talk fluently about BM25 vs. semantic hybrid retrieval, re-ranking, and recall vs. precision tradeoffs — unprompted.

  • Founding engineer DNA: has shipped features end-to-end at a sub-200-person startup (Series A–C) without a PM, designer, or QA layer.

  • TypeScript/Node.js proficiency; comfortable with observability tooling (Datadog, Sentry, OpenTelemetry) and cloud infra in production.