Staff Backline Engineer – ML/AI

Databricks · Bellevue, Washington; San Francisco, California · Support · listed February 20, 2025

The shape of it

Seniority
Staff
Where
Not stated
Requirements listed
9
Length
947 words

In the posting’s own words

As a Staff Backline Engineer, you will be a technical expert and escalation point for some of the most complex ML/AI issues. You will work across Support, Engineering, Product, and customers to troubleshoot difficult problems, reproduce issues, identify root causes, and drive them to resolution.

What it asks for · 9

  • Deep troubleshooting experience with distributed ML/AI systems and the ability to debug problems across application code, frameworks, infrastructure, and the Databricks platform.
  • Strong hands-on Python experience and the ability to build, modify, and debug ML workloads using frameworks such as PyTorch, TensorFlow, or Scikit-Learn.
  • Strong understanding of Databricks ML/AI technologies, including MLflow, Model Serving, Feature Engineering, Spark MLlib, and model lifecycle management.
  • Strong Apache Spark knowledge, including DataFrames, query execution, distributed computing, memory management, shuffles, and performance optimisation.
  • Experience troubleshooting training and inference performance, including CPU/GPU utilisation, memory issues, data bottlenecks, concurrency, latency, and distributed execution.
  • Experience with ML deployment and infrastructure such as Kubernetes, cloud ML platforms, CI/CD, model monitoring, and production ML systems.
  • Ability to read and reason about code, logs, stack traces, metrics, traces, execution plans, and system behaviour rather than relying solely on documentation or configuration recommendations.
  • Demonstrated ability to independently own ambiguous, high-impact technical problems and drive them from symptom → investigation → root cause → resolution .
  • Strong technical communication skills and the ability to influence Engineering, Product, Support, and customers.

What the job covers

  • Serve as a senior escalation point for complex ML/AI issues involving model training, inference, Model Serving, MLflow, Feature Engineering, with knowledge of Spark, Delta Lake, and distributed workloads.
  • Perform deep technical investigations using logs, traces, metrics, profiling, configuration, source code, and customer workloads to identify root cause.
  • Reproduce customer issues through hands-on experimentation, Python/Spark development, workload construction, configuration changes, and performance analysis.
  • Troubleshoot model training and inference failures, performance degradation, resource utilization, memory/CPU/GPU issues, distributed execution problems, and deployment/runtime failures.
  • Partner closely with Engineering and Product teams to drive difficult issues to resolution and influence product improvements.
  • Identify recurring failure patterns and turn them into better diagnostics, documentation, tooling, automation, and Claude skill capabilities.
  • Mentor engineers and raise the technical troubleshooting capabilities of the broader Support organization.
  • Act as a technical SME for ML/AI platform areas and contribute to cross-functional initiatives with global impact.

Tools and skills named

Models & research
  • Machine learning9×
  • Inference3×
  • GPU2×
  • PyTorch
  • TensorFlow
Data
  • Spark5×
  • Databricks3×
  • Experimentation
Ways of working
  • Technical writing2×
  • Cross-functional
Cloud & infra
  • CI/CD
  • Kubernetes
Languages
  • Python2×
Go to market
  • Customer success
Product & design
  • User experience

Words the posting leans on

  • issues9×
  • technical9×
  • customer8×
  • engineering7×
  • data6×
  • model6×
  • platform6×
  • distributed5×
  • experience5×
  • ml/ai5×
  • problems5×
  • product5×
  • deep4×
  • drive4×
  • execution4×
  • infrastructure4×

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 October 25, 2026 and last changed by Databricks on September 21, 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.