Staff Software Engineer - GenAI inference

Databricks · San Francisco, California · Engineering - Pipeline · listed October 8, 2025

The shape of it

Seniority
Staff
Where
Not stated
Stated pay
$190,900 – $232,800 USD
Requirements listed
11
Length
732 words

In the posting’s own words

As a staff software engineer for GenAI inference, you will lead the architecture, development, and optimization of the inference engine that powers Databricks Foundation Model API.. You’ll bridge research advances and production demands, ensuring high throughput, low latency, and robust scaling. Your work will encompass the full GenAI inference stack: kernels, runtimes, orchestration, memory, and integration with frameworks and orchestration systems.

What it asks for · 11

  • BS/MS/PhD in Computer Science, or a related field
  • Strong software engineering background (6+ years or equivalent) in performance-critical systems
  • Proven track record of owning complex system components and driving architectural decisions end-to-end
  • Deep understanding of ML inference internals: attention, MLPs, recurrent modules, quantization, sparse operations, etc.
  • Hands-on experience with CUDA, GPU programming, and key libraries (cuBLAS, cuDNN, NCCL, etc.)
  • Strong background in distributed systems design, including RPC frameworks, queuing, RPC batching, sharding, memory partitioning
  • Demonstrated ability to uncover and solve performance bottlenecks across layers (kernel, memory, networking, scheduler)
  • Experience building instrumentation, tracing, and profiling tools for ML models
  • Ability to lead through influence - work closely with ML researchers, translate novel model ideas into production systems
  • Excellent communication and leadership skills, with a proactive and ownership-driven mindset
  • Bonus: published research or open-source contributions in ML systems, inference optimization, or model serving

What the job covers

  • Own and drive the architecture, design, and implementation of the inference engine, and collaborate on model-serving stack optimized for large-scale LLMs inference
  • Partner closely with researchers to bring new model architectures or features (sparsity, activation compression, mixture-of-experts) into the engine
  • Lead the end-to-end optimization for latency, throughput, memory efficiency, and hardware utilization across GPUs, and accelerators
  • Define and guide standards to build and maintain instrumentation, profiling, and tracing tooling to uncover bottlenecks and guide optimizations
  • Architect scalable routing, batching, scheduling, memory management, and dynamic loading mechanisms for inference workloads
  • Ensure reliability, reproducibility, and fault tolerance in the inference pipelines, including A/B launches, rollback, and model versioning
  • Collaborate cross-functionally on Integrating with federated, distributed inference infrastructure – orchestrate across nodes, balance load, handle communication overhead
  • Drive cross-team collaboration: with platform engineers, cloud infrastructure, and security/compliance teams
  • Represent the team externally through benchmarks, whitepapers, and open-source contributions

Degree language

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

Tools and skills named

Models & research
  • Inference10×
  • Machine learning4×
  • GPU2×
  • CUDA
  • LLM
Cloud & infra
  • Distributed systems
Data
  • Databricks
Security & compliance
  • Security

Words the posting leans on

  • inference10×
  • model6×
  • systems6×
  • memory5×
  • optimization4×
  • architecture3×
  • lead3×
  • background2×
  • batching2×
  • bottlenecks2×
  • closely2×
  • collaborate2×
  • communication2×
  • design2×
  • distributed2×
  • drive2×

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.