Staff Software Engineer - AI Research Infrastructure

Databricks · New York City, New York; San Francisco, California · Engineering - Pipeline · listed May 15, 2026

The shape of it

Seniority
Staff
Experience asked
5+ years
Where
Not stated
Stated pay
$199,000 – $270,000 USD
Requirements listed
8
Length
885 words

In the posting’s own words

As a Staff Software Engineer, AI Research Infrastructure, you will be developing and running the research stack that powers Databricks AI Research. You will design and build services that schedule, orchestrate, and observe large‑scale training and inference experiment workloads across thousands of GPUs, improve our dev tooling and ensure that researchers can iterate quickly without sacrificing reliability, efficiency, or security.

What it asks for · 8

  • BS/MS or PhD in Computer Science or related field
  • 5+ years of software engineering experience, including substantial time working on large‑scale distributed systems or infrastructure.
  • Have deep experience with building and operating distributed systems, data pipelines, or large‑scale backend services, ideally involving GPUs, clusters, or major cloud providers.
  • Are proficient in one or more systems programming languages (e.g., C++, Rust, Go, Java, Scala) and can design, implement, and debug complex services.
  • Have built or significantly contributed to cluster schedulers, resource managers, or large‑scale job orchestration systems (e.g., Kubernetes, Slurm, Ray, custom internal systems).
  • Understand modern ML training and inference workflows (e.g., distributed training, model parallelism, fine‑tuning, evaluation), even if you’re not primarily a research scientist.
  • Can move fast and be pragmatic in getting things done, while caring about operational excellence. Have driven complex systems from prototype to stable, well‑owned services.
  • Communicate clearly with both researchers and engineers, and enjoy translating between research needs and infra realities.

What the job covers

  • Design and implement infrastructure that supports large‑scale experiments, data processing, and model training (e.g., HPC clusters, GPU fleets, or cloud‑based systems)
  • Enable researchers to go from idea to large‑scale experiment in minutes, not days, by building powerful abstractions for job submission, scheduling, and monitoring.
  • Create tooling that improves research developer productivity, such as experiment management systems, CI/testing infrastructure for research code, and workflows that reduce iteration time.
  • Influence the long‑term roadmap for research computation, shaping how Databricks AI Research train, evaluate, and ship models to customers.
  • Serve as a technical mentor and force multiplier for other engineers working on compute, infra, and AI systems.

Degree language

  • BS/MS or PhD in Computer Science or related field

Tools and skills named

Data
  • Databricks7×
  • Data pipelines
Models & research
  • GPU3×
  • Inference2×
  • Machine learning2×
  • LLM
Languages
  • C++
  • Go
  • Java
  • Rust
  • Scala
Cloud & infra
  • Distributed systems2×
  • Kubernetes
Security & compliance
  • Security2×
Product & design
  • Roadmap
Ways of working
  • Testing

Words the posting leans on

  • research13×
  • systems9×
  • engineer6×
  • infrastructure6×
  • large scale6×
  • data5×
  • models5×
  • e.g4×
  • experiment4×
  • services4×
  • training4×
  • building3×
  • clusters3×
  • design3×
  • infra3×
  • researchers3×

Counted from the posting after the mission statement and the legal notices are set aside. The ones near the top are the ones a screener is looking for.

The posting, your resume, and the gaps between them. One click loads all three.

More open at Databricks

every open role at Databricks

How this page was made

An automated read of a public job posting, fetched August 24, 2026 and last changed by Databricks on August 18, 2026. Every list above is pulled from the posting’s own sentences — nothing rewritten, nothing added, no judgment about the role or the company. Counts and seniority are read off the text by rule, so they can be wrong where the posting is unusual. The original is the only thing that binds. Openings close without warning; check the source before spending an evening on it.