←
Julia Neagu1,763 posts
Julia Neagu avatar✓

Julia Neagu ✓

@juliaaneagu

AI research @Databricks @DbxMosaicAI | founded @QuotientAI ✨ formerly @GitHub @GitHubCopilot 🤖 reformed physicist 👩‍🔬 ~ opinions are my own ~

◷ Joined March 2013▧ 176 Photos and videos
Julia Neagu avatar
Julia Neagu@juliaaneagu·Nov 13

I am hiring a Researcher for my team at @databricks AI Research. If you have a deep instinct for measuring complex systems and want to build self-improving agents at the frontier, I'd love to talk. Link below 👇

Patrick Wendell avatar
⟳ Julia Neagu retweeted
Patrick Wendell@pwendell·Nov 16

1/ Today we’re publishing the Databricks AI Index, showing trends from enterprises who manage AI with our Unity Gateway. Data covers >10,000 companies with broad representation (Digital Natives, Fortune 500, Global 2000, etc...). Enterprise AI consumption is changing quite a bit:

Post attachment
Max Margenot avatar
⟳ Julia Neagu retweeted
Max Margenot@clean_utensils·Nov 2

Hi folks, over the weekend we shipped the Public Eye, a tool for making Congressional bills more legible for everyone. John Q. Public performs agentic search over federal bills sponsored and voted on by your representatives.

Post attachment
Ivan Zhou avatar
⟳ Julia Neagu retweeted
Ivan Zhou@ivanzhouyq·Aug 12

We worked with @spacexai to evaluate Grok 4.6 on the latest OfficeQA Pro V2 from @DbrxMosaicAI. It achieves the SOTA performance with @databricks's Genie harness! The model is strongest on our document understanding and data reasoning tasks, and it is a very efficient driver!

Post attachmentPost attachment
Yuchen Jin avatar
⟳ Julia Neagu retweeted
Yuchen Jin@Yuchenj_UW·Aug 7

At Databricks, AI coding token spend is growing exponentially. 1. The “efficiency frontier” matters. On Databricks Coding Bench, GLM 5.2, Opus 4.8, and GPT 5.6-Sol sit on that frontier: the best quality per dollar. 2. We see cost regressions when comparing Opus 5.0 to 4.8. Newer model doesn’t always mean more efficient. 3. Hard budgets are the wrong primitive. Your biggest AI spenders may also be your most AI-leveraged engineers. 4. There is no best model for every task. Routing, harnesses, evals, and the right mix of open and proprietary models can radically change the economics. We’re investing heavily in all 4, both for ourselves and for our customers.

Post attachment
Patrick Wendell avatar
⟳ Julia Neagu retweeted
Patrick Wendell@pwendell·Aug 7

Today @databricks we're publishing a detailed analysis of techniques we used to drastically reduce our internal AI spend while aggressively growing adoption. Savings come from layering in several techniques, which combine to drive unit costs down as much as 90% in some scenarios. Tl;dr, the wins come from: 1. Shifting defaults to more efficient models, including OSS models such as GLM. Maximum intelligence models simply aren't needed for many coding tasks, and "good enough" models are quickly becoming very cheap. We shift traffic between models using Unity AI Gateway. Approximate savings: 50% or more. 2. Using smart routing to automate model selection. Routing can further squeeze efficiency by dynamically selecting the model or harness that can most efficiently execute a particular task. Our task-level routing leverages @omnigent_ai. Approximate savings: 30%. 3. Providing user visibility and adaptive budgeting. Every user can see how much they spend, and users receive hints on how to contain spend. Heavy spenders encounter progressive friction as they ratchet spend above certain levels. Approximate savings: 10%. 4. Managing context bloat by pruning tool call results and tuning harness settings. Extraneous context costs $$ and delivers no value. Tuning cache settings also help lower average token costs. Approximate savings: 10%.

Post attachment
Krista Opsahl-Ong avatar
⟳ Julia Neagu retweeted
Krista Opsahl-Ong@kristahopsalong·Aug 6

📣 Excited to introduce OfficeQA Pro V2, the next generation of OfficeQA Pro! It's built on a new corpus of 120,000 PDFs provided by the U.S. Treasury. Frontier AI agents average 26% accuracy. More info below 👇 databricks.com/blog/introduc…

Ali Ghodsi avatar
⟳ Julia Neagu retweeted
Ali Ghodsi@alighodsi·Jul 25

This is one of those unintuitive things. Agents that cook longer are often worse. Genie just gets to the results faster. Ontology will be key to getting these agents the context they need to get the answers right quickly.

Julia Neagu avatar
Julia Neagu@juliaaneagu·Jul 25

We found that improving data agent quality also improves efficiency. Sometimes more is less: agents that take long, exploratory random walks are often less likely to arrive at the right answer. We put Genie Code head-to-head against three leading general-purpose coding agents on 400+ real user data tasks. Result below 👇

Post attachment