Software Engineer, Infrastructure - Analytics Platform

OpenAI

Where
Hybrid in San Francisco

Posted 7 months ago· Checked live at OpenAI 1 hour ago

Stale: open 222 daysUp for more than two weeks. It may already be filled.

See how you score for this job

One sentence and your resume. We score it against what OpenAI asks for, line by line.

See my score
Is this job still open?
Yes. We checked it live on OpenAI's own hiring page 1 hour ago.
What is the job?
The Platform Analytics team builds the systems OpenAI researchers use to understand the quality and behavior of the models we train including what models are doing, why they behave in a particular way, and how that behavior changes across experiments. Neptune https://openai.com/index/openai-to-acquire-neptune/?utm_source=neptune-website-redirect is a core part of this work.
What does it pay?
The posting doesn't say.
Our verdict
Stale. Up for more than two weeks. It may already be filled.

What the job is

The Platform Analytics team builds the systems OpenAI researchers use to understand the quality and behavior of the models we train including what models are doing, why they behave in a particular way, and how that behavior changes across experiments.

Neptune https://openai.com/index/openai-to-acquire-neptune/?utm_source=neptune-website-redirect is a core part of this work.

In this role, you will

  • Own critical systems across architecture, implementation, integrations, deployment, monitoring, adoption, and whatever else is required to make them useful.
  • Design, build, and operate the ingestion, storage, retrieval, and query systems behind research analytics at OpenAI.
  • Build platforms for analyzing both structured metrics and unstructured research data, including samples, traces, evaluation results, and model-behavior data.
  • Reason below typical service abstractions about algorithms, data structures, concurrency, storage layout, distributed systems, query performance, and failure modes.
  • Make architectural tradeoffs across ingestion-time processing, data models, storage formats, indexing, query execution, caching, and visualization performance.
  • Work directly with researchers to understand what they are trying to learn, ask the right questions, and challenge a requested solution when a simpler or more effective approach exists.
  • Recognize when several teams are solving the same problem and turn those patterns into shared infrastructure, APIs, platform components, or agent-driven workflows.
  • Write code, investigate production issues, make realistic estimates, guide other engineers, and think through testing, rollout, observability, and rollback.
  • Keep solutions as simple as the problem allows. Introduce complexity only when correctness, scale, latency, or reliability genuinely require it, and address the largest bottleneck first.

You might thrive in this role if you

  • Have owned a critical distributed system or research platform end to end and can explain how you took it from an ambiguous problem to reliable production adoption.
  • Have experience with high performing programing languages (Rust or C++), including performance profiling, concurrency, async execution, memory behavior, serialization, I/O, networking, and failure analysis.
  • Bring deep expertise in at least one relevant area such as distributed databases, storage engines, analytics systems, telemetry, logging, search, ingestion, or query execution.
  • Can reason carefully about partitioning, replication, consistency, retries, backpressure, event lineage, duplicate or delayed data, overload, migrations, and failure isolation.
  • Have experience with ClickHouse or similar OLAP, columnar, time-series, or high-throughput analytical systems. Direct ClickHouse experience is helpful but not required.
  • Bring strong computer science fundamentals and algorithmic reasoning. Competitive-programming experience is welcome but not required.
  • Already use coding agents regularly and have opinions about how AI tools change software development, product interfaces, and engineering leverage.
  • Enjoy working directly with researchers and other highly technical users: understanding their constraints, debugging ambiguous problems, explaining tradeoffs, and closing the loop after shipping.
  • Have the judgment to focus on the largest practical bottleneck rather than expanding every project into a complete platform rewrite.
  • Are a strong engineer first. Clear communication and business judgment are non-negotiable, but your credibility comes from building and operating systems that work.

Similar open jobs

Software engineer jobs in San Francisco (1709)Jobs in San Francisco (11750)