Senior Staff Software Engineer - App and Partner Ecosystem

Databricks · Seattle, Washington · Engineering · listed March 19, 2025

The shape of it

Seniority
Executive
Experience asked
10+ years
Where
Not stated
Stated pay
$217,100 – $298,550 USD
Requirements listed
3
Length
838 words

In the posting’s own words

As a Senior Staff Software Engineer, you will define the vision, architecture, and strategy for this ecosystem. You will play a key role in enabling customers to integrate cutting-edge applications, helping developers thrive on Databricks, and shaping the future of data and AI platforms.

What it asks for · 3

  • 10+ years of experience building data-intensive applications or systems. Strong expertise in database systems (SQL, NoSQL, OLAP/OLTP) and big data processing (Apache Spark™, Flink). Experience designing high-performance APIs (REST, GraphQL, gRPC) and managing integrations.
  • Strong understanding of data security, governance, and compliance frameworks (RBAC, GDPR, HIPAA), as well as cloud infrastructure (AWS, Azure, GCP), Kubernetes, Terraform, and CI/CD pipelines.
  • Ability to mentor engineers, influence architectural decisions, and advocate for best practices.

Tools and skills named

Data
  • Databricks10×
  • Spark2×
Cloud & infra
  • AWS
  • Azure
  • CI/CD
  • GCP
  • Kubernetes
  • Terraform
Security & compliance
  • Security3×
  • GDPR
  • HIPAA
Frameworks
  • GraphQL
  • gRPC
  • REST
Languages
  • SQL
Ways of working
  • Cross-functional

Words the posting leans on

  • data12×
  • ecosystem7×
  • applications6×
  • developers6×
  • partners6×
  • platform6×
  • customers5×
  • experience5×
  • development4×
  • practices4×
  • build3×
  • enabling3×
  • frameworks3×
  • future3×
  • innovation3×
  • integrations3×

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.