Senior Staff Applied AI Engineer - Context RetrievalNew$229K

Databricks
Apply now

The opportunity

At Databricks, we are passionate about enabling data teams to solve the world's toughest problems — from making the next mode of transportation a reality to accelerating the development of medical breakthroughs. We do this by building and running the world's best data and AI…

What you'll do

  • Build the retrieval stack: query understanding, content understanding, ranking, retrieval, and evaluation — across the Enterprise SaaS data stored across multiple systems.

  • Build the search subagents that sit on top of that stack and reason about: what context is needed , how to retrieve it , and whether the right thing actually came back — closing the loop between an agent's intent and the substrate that serves it.

  • Build the full retrieval stack from scratch. Own the end-to-end system: query understanding, content understanding and indexing, hybrid retrieval, ranking, and evaluation. Make the architectural calls that will define how Databricks agents access context for years to come.

  • Retrieve across heterogeneous data: structured and unstructured. Index and rank across structured assets (tables, columns, SQL queries, dashboards, code, notebooks, jobs) and unstructured content (docs, wikis, tickets, chat, images, video, audio). Each modality has its own signals — design retrieval that exploits them rather than flattens them.

  • Connect to the SaaS surface area customers actually use. Build connectors and: retrieval adapters for the systems where enterprise knowledge lives. Treat each retrieval source with its own freshness, permissions, and ranking signals.

  • Optimize for two consumers at once. Retrieval must serve both LLMs (grounded,: token-efficient, hallucination-resistant context) and humans (intuitive, explainable discovery). These are different objectives and require different signals — own both.

What they're looking for

  • Crack query understanding for agents. Agent queries don't look like web: queries. Build query rewriting, decomposition, intent classification, and entity resolution tuned for multi-turn agentic workflows.
  • Crack content understanding at scale. Build the pipelines that extract: structure, entities, embeddings, summaries, and metadata from every supported asset type — and keep them fresh as customer data evolves.
  • Build search subagents that reason about retrieval. Design the agentic layer: that decides what context is needed , which sources to query , how to decompose and route the search , and — critically — whether the retrieved content is actually sufficient to answer the question . These subagents will plan multi-hop searches, issue follow-up queries when results are weak, ground claims against retrieved evidence, and hand back high-confidence context (or signal failure) to upstream agents. This is where IR meets agentic reasoning.
  • Build the evaluation flywheel for both retrieval and subagents. Stand up: offline evals (nDCG, MRR, Recall@K, Precision@K), LLM-as-judge harnesses, human-in-the-loop labeling, and online experimentation. Extend evaluation beyond ranking metrics to measure subagent decision quality — did it ask the right follow-up? , did it correctly recognize when retrieval failed? , did it ground its answer in the right evidence? . Quality you can't measure is quality you can't ship.