Senior Software Engineer — Backend (Files Team)

Databricks · San Francisco, California · Engineering - Pipeline · listed October 2, 2026

Tailor your resume for this role →the original posting ↗

The shape of it

Seniority
Senior
Experience asked
3–5 years
Where
Not stated
Stated pay
$166,000 – $225,000 USD
Requirements listed
6
Length
740 words

In the posting’s own words

As a Senior Software Engineer on the Files team, you will innovate at the intersection of storage, performance, and distributed systems, directly shaping our filesystem strategy to power next-generation agentic workloads.

What it asks for · 6

  • Bachelor's degree (or higher) in Computer Science or a related field
  • 5+ years of production-level experience in Java, Scala, C++, Go, Rust, or a similar language
  • 3+ years of experience developing large-scale distributed systems
  • Experience with Kubernetes, Docker, or MicroVM technologies (e.g., Firecracker) and a strong grasp of cloud provider internals (AWS/Azure/GCP).
  • Experience with filesystems and FUSE
  • Experience building object/blob storage (S3, Azure Blob Storage, GCS etc)

What the job covers

  • Design, build, and operate the the filesystem platform powering tens of thousands of data, AI and agentic workloads daily
  • Push filesystem performance for the most demanding workloads — profiling and optimizing across the stack, from the API layer down to the Linux kernel
  • Partner with teams across the platform to design and evolve next-generation compute and storage architectures
  • Set the technical direction for how content is organized across Databricks, standardizing around filesystem primitives that apply to every product surface

Degree language

  • Bachelor's degree (or higher) in Computer Science or a related field

Tools and skills named

Cloud & infra
  • Azure2×
  • Distributed systems2×
  • Linux2×
  • AWS
  • Docker
  • GCP
  • Kubernetes
  • Microservices
Languages
  • C++
  • Go
  • Java
  • Rust
  • Scala
Data
  • Databricks2×
Product & design
  • User experience

Words the posting leans on

  • filesystem7×
  • data5×
  • experience5×
  • storage5×
  • systems4×
  • performance3×
  • platform3×
  • agentic workloads2×
  • agents2×
  • build2×
  • building2×
  • content2×
  • customer2×
  • design2×
  • distributed systems2×
  • engineer2×

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.

Tailor your resume for this role →apply on Databricks’s board ↗

More open at Databricks

every open role at Databricks →

How this page was made

An automated read of a public job posting, fetched October 2, 2026 and last changed by Databricks on October 2, 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.