Senior Staff Applied AI Engineer - Context Retrieval

Benefits

Parental leave

Not verified

Non-birth-parent leave

Not verified

Family-building benefits

• Fertility benefits: Not verified
• Adoption assistance: Not verified
• Surrogacy assistance: Not verified

Mental health support

Not verified

Relocation assistance

Not verified

Childcare support

Not verified

Learning budget

Not verified

Verification

Not verified

Salary

Not verified not verified - source not recorded; timestamp not recorded

401(k) match

Not verified

Was this benefit information wrong? Tell us.

Schedule

Shift type

Not verified

Weekend work

Not verified

Application

Cover letter

Not verified

Assessment

Not verified

Deadline

Not stated

Where they hire

State eligibility is not yet verified.

About this role

Senior Staff Applied AI Engineer - Context Retrieval Mountain View, California; San Francisco, California P-1549 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 infrastructure platform so our customers can use deep data insights to improve their business. The Mission Databricks agents are only as good as the context they can retrieve. Whether an agent is answering a question about last quarter's revenue, debugging a failing job, generating SQL against a 10,000-table lakehouse, or summarizing a Wiki page, its quality is bounded by what it can find - and how well it understands what it finds. We are hiring a Senior Staff Applied AI Engineer to own context retrieval for Databricks agents across SaaS providers . This is a zero-to-one role with two deeply connected charters: - 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. If you have deep Information Retrieval wisdom, have shipped retrieval systems for RAG and agentic workloads, and

Read the full description at databricks.com. FewerJobs shows a source-linked preview and links to the original posting.