From Data Engineering to AI Agents: How Databricks Is Reshaping the Enterprise Data Stack Hiring growth, product signals, talent flows, and org structure
Databricks' hiring growth is concentrated in a single role: Forward Deployed Engineer reached 13.4% of all postings in August (month 8), pulled up from a low point six months earlier. Agent-related hiring language spread earlier but never became a formal structure of its own. And the product actually reshaping the hiring mix is not the one drawing the most attention—it is the far less visible Lakebase.
Report date 2026-08-20Produced by Metix AICoverage U.S. · India · Netherlands
01 · Executive summary
01Databricks' Agent investment has not yet surfaced in job titles—and its fastest-growing product signal is not the most visible one
Databricks' Agent signal sits in its product and hiring language, not yet in its org structure. The larger shift in the hiring mix comes from a different line — Forward Deployed Engineer — and from a far less visible product, Lakebase. These three core findings draw on independent evidence from job text, current employees, and product keywords.
137
Current employees with AI/ML titles
By comparison, Snowflake has 82
10×
6-month increase in Lakebase hiring mentions
0.4% → 4.6% (July, month 7 peak)
40×
Peak increase in Forward Deployed Engineer hiring volume
May (month 5) low of 1.8/month → 71.5/month in August (month 8)
40.6%
Databricks year-over-year employee growth
Snowflake was 20.7% over the same period
01The fastest-growing role in the hiring mix is Forward Deployed Engineer: 40× in three months, with August (month 8) volume more than 6× Agent-titled hiring
This was not a smooth ramp: the line was still falling from month 2 to month 4, turned only in month 6, and has climbed since.
02Agent language is advancing ahead of formal roles: 137 current employees have AI/ML titles, while dedicated Agent roles stay under 1%
The share rose from 1.1% to 2.1% over six months as Engineering, AI Research, and Product/GTM joined in sequence.
03Lakebase hiring mentions rose 10× in six months while Agent Bricks stayed flat
Database-function roles, classified by function rather than product name, rose over the same period—a different classification method pointing independently the same way.
04Databricks’ talent-flow advantage over Snowflake closely matches its employee-growth advantage
Databricks’ employee growth rate is about 2× Snowflake’s; talent-flow direction and five-year headcount change independently fall in a similar range.
02 · FDE signal
02Most of Databricks' hiring growth is concentrated in a single role: Forward Deployed Engineer
In Databricks job descriptions, the share of Forward Deployed Engineer roles rose from a May (month 5) low of 0.3% to 13.4% in August (month 8). Absolute hiring volume climbed from 1.8 to 71.5 roles per month, an increase of about 40×. The series declined across months 2 through 4, then accelerated sharply from June (month 6). August volume of 71.5 roles per month was more than 6× the 11.0 monthly roles carrying Agent titles. Only 13 current employees hold the FDE title. Hiring trends and current employees both point to a new function that already exceeds Agent-titled hiring in scale and is still being built out rapidly.
Monthly share of hiring: Forward Deployed Engineer, AI/Agent, and Engagement Manager
The three lines diverge completely. Combined AI/Agent roles fluctuated between 2.1% and 4.0% over 6 months without a clear trend, while Engagement Manager roles—whose job descriptions explicitly say they sell and promote FDE services—fell from 3.3% to under 0.2% from June (month 6) onward as FDE hiring became large enough to stand on its own.
03Agent has entered the job descriptions, not yet the org chart
Over the past six months, Agent-related roles nearly doubled as a share of Databricks hiring, rising from 1.1% to 2.1%. The increase was not a one-off spike in a single team: Engineering, AI Research, and Product/GTM joined in sequence, broadening the hiring footprint. Yet Agent-related wording stays under 1% of LinkedIn-visible current Databricks titles; a full-title search across all functions returns the same.
Monthly share: Engineering (Agentic Applications)
Share declined from 97% to 56%, but Engineering remained the largest of the three lines.
2026-02
96.9
2026-03
83.9
2026-04
88.4
2026-05
80.0
2026-06
59.3
2026-07
54.3
2026-08
55.6
Source: Metix AI
Monthly share: AI Research
The line only appeared in month 5, then peaked at 37%.
2026-02
0.0
2026-03
0.0
2026-04
0.0
2026-05
20.0
2026-06
37.0
2026-07
21.7
2026-08
18.5
Source: Metix AI
Monthly share: Product/GTM
The share dipped in month 5, then expanded visibly from month 7 to 26%.
2026-02
3.1
2026-03
16.1
2026-04
11.6
2026-05
0.0
2026-06
3.7
2026-07
23.9
2026-08
25.9
Source: Metix AI
04 · Product signal
04The product reshaping the hiring mix is the one getting far less attention
The share of Databricks job descriptions mentioning Lakebase increased about 10× in six months, from 0.4% to a July (month 7) peak of 4.6%—the clearest single-product signal in the dataset. Over the same period, the more visible AI product Agent Bricks showed no growth trend, fluctuating between 0.7% and 1.4%. Database-function roles, classified by hiring function rather than product name, rose over the same period and independently point in the same direction. The less-publicized product is the one reshaping the hiring structure.
Months 2 to 8: Lakebase, Genie, Agent Bricks, Unity Catalog/AI Gateway, and Database Function
Lakebase and Genie traced almost the same rising curve, closing August (month 8) at 3.9% and 2.9% respectively. Agent Bricks peaked at its starting point of 1.4% in February (month 2). Unity Catalog/AI Gateway was broadly flat over 6 months, moving from 3.8% to 4.1% after dipping to 2.2%. Database Function rose from 1.4% to 1.7%, with a 2.4% June (month 6) peak, independently confirming the same direction through a different classification method.
Open circle = 2026-02 · Solid circle = 2026-08
← Swipe horizontally to view the full chart →
Source: Metix AI
05 · Talent flow and organization structure
05Talent flow and headcount growth point to the same gap, yet the two orgs look nearly identical
The comparison below looks at Databricks and Snowflake from three angles: source companies, flow direction, and function mix.
Talent moving to Databricks—larger source companies
All 9 larger source companies send more talent to Databricks.
Amazon/AWS
915
Google
731
Microsoft
523
LinkedIn
353
Meta
288
Uber
234
Cloudera
228
Tableau
207
Splunk
167
Source: Metix AI
Talent moving to Snowflake—larger source companies
The same 9 companies sent 2,260 people to Snowflake, about 60% of the 3,646 who went to Databricks.
Amazon/AWS
579
Google
375
Microsoft
481
LinkedIn
125
Meta
210
Uber
63
Cloudera
172
Tableau
109
Splunk
146
Source: Metix AI
Talent moving to Databricks—smaller source companies
Among 7 smaller source companies, 5 favor Databricks; Fivetran and dbt Labs favor Snowflake.
MongoDB
56
Confluent
55
Anthropic
18
Fivetran
14
OpenAI
13
Cockroach Labs
8
dbt Labs
7
Source: Metix AI
Talent moving to Snowflake—smaller source companies
The same 7 companies sent 115 people to Snowflake, about two-thirds of the 171 who went to Databricks.
MongoDB
36
Confluent
35
Anthropic
6
Fivetran
19
OpenAI
4
Cockroach Labs
7
dbt Labs
8
Source: Metix AI
Talent flow between Databricks and Snowflake, by direction
The number moving to Databricks is about 2.2× the reverse flow.
→ Databricks
130
→ Snowflake
59
Source: Metix AI
Current employee function mix: Databricks vs. Snowflake
The combined share of AI/ML, Security/Governance, Field/Customer Enablement, and Corporate Functions is nearly identical at the two companies (8.6% vs. 8.5%). The clearest named difference is IC Software Engineering (24.9% vs. 19.6%). The chart shows only six priority functions.
Databricks
7,163Current talent
Snowflake
6,377Current talent
FunctionDatabricksSnowflake
Software Eng.24.89%19.55%
Sales/GTM41.80%38.44%
AI/ML1.91%1.29%
Security0.66%1.18%
Field Enablement3.22%2.84%
Corporate2.82%3.17%
Source: Metix AI
06 · Priority teams
06Talent roster
Based on available professional profiles, this roster compares representative Databricks and Snowflake talent across four technical lines: AI, Database, Security/Governance, and Data Engineering. Each group contains 2 people and is intended to illustrate team composition, not a ranking or exhaustive list.
Databricks
AI
A●● R●●
Software Engineer, Applied AI (San Francisco)
LLM Systems · Text-to-query Systems · RAG
B●● A●●
Machine Learning Engineer, GenAI (San Francisco)
Mosaic AI · Model Deployment · Applied ML
Databricks
Database
Y●● L●●
Lakebase (Madison)
Meta · Intel · Database Platforms
R●● D●●
Member of Technical Staff, Lakebase (Amsterdam)
Neon · Cloud-native Database · Growth Engineering
Snowflake
AI
P●● J●●
AI Data Cloud Architecture, Solutions (Mountain View)
Applied ML · Enterprise Architecture · Solutions
A●● J●●
AI Architect (Bengaluru)
Data Analytics · Enterprise Architecture
Snowflake
Database
J●● T●●
Software Engineer, Database Security (San Francisco)
SWE Leadership, Company-wide Data Governance (San Francisco)
Platform Leadership · Scalable Systems
B●● E●●
Sr. Staff Security Engineer (Lehi)
Enterprise Security · Staff IC
Databricks
Data Engineering
S●● A●●
Lead Data Engineer (San Francisco)
Lakehouse · Spark · Delta Lake
M●● G●●
Staff Data Engineer (Gurugram)
Cloud Data Architecture · Staff IC
Snowflake
Security / Governance
A●● S●● P●●
Security Data Governance (Atlanta)
Compliance · Risk · Governance
P●● P●●
Security Software Engineer (San Jose)
Security Automation · Product Engineering
Snowflake
Data Engineering
Z●● M●●
Principal Cloud Data Engineer (San Francisco)
Cloud Data Platforms · Principal IC
A●● G●●
Senior Data Engineer, IC4 (Pune)
Data Platforms · Senior IC
Source: Metix AI · Available professional profiles
FAQ
Questions this report answers
What does From Data Engineering to AI Agents: How Databricks Is Reshaping the Enterprise Data Stack | Metix AI cover?
Across the US, India and the Netherlands: Forward Deployed Engineer postings grew about 40× in three months, Lakebase is the product reshaping the mix, and Agent remains product language.
What population and methodology does From Data Engineering to AI Agents: How Databricks Is Reshaping the Enterprise Data Stack | Metix AI use?
Databricks' Agent signal sits in its product and hiring language, not yet in its org structure. The larger shift in the hiring mix comes from a different line — Forward Deployed Engineer — and from a far less visible product, Lakebase. These three core findings draw on independent evidence from job text, current employees, and product keywords.
How should this report be cited?
Metix AI Talent Intelligence, 2026-08-20. From Data Engineering to AI Agents: How Databricks Is Reshaping the Enterprise Data Stack | Metix AI. https://metix.ai/reports/mapping/databricks-ai-talent-strategy-2026
Need to turn a competitor's talent structure into an actionable shortlist?
Metix AI can use a target company's function mix, product-line keywords, and inbound and outbound talent flows to build a private candidate pool, competitor list, and validation evidence.