Databricks Data Engineer: Associate vs Professional
Databricks offers two data engineering certifications. The Associate covers introductory data engineering on the platform; the Professional covers advanced work. Neither is a formal prerequisite for the other, though the progression is the obvious one.
Side by side
| Associate | Professional | |
|---|---|---|
| Scored questions | 45 | 60 |
| Duration | 90 minutes | 120 minutes |
| Fee | $200 | $200 |
| Validity | 2 years | 2 years |
| Sections | 7 | 9 |
| Largest section | Data Transformation and Modeling (22%) | Developing Code using Python and SQL (23%) |
| Prerequisites | None | None |
Same price, same validity, same format. The Professional is longer, more granular, and pitched at harder work. Its figures here follow the outline Databricks introduced on 9 October 2026.
The sections
Associate — doing the job:
| Section | Weight |
|---|---|
| Data Transformation and Modeling | 22% |
| Data Ingestion and Loading | 21% |
| Working with Lakeflow Jobs | 16% |
| Governance and Security | 15% |
| Implementing CI/CD | 10% |
| Troubleshooting, Monitoring, and Optimization | 10% |
| Databricks Intelligence Platform | 6% |
Professional — doing it well, at scale:
| Section | Weight |
|---|---|
| Developing Code for Data Processing using Python and SQL | 23% |
| Cost & Performance Optimisation | 15% |
| Data Ingestion & Acquisition | 12% |
| Data Manipulation | 12% |
| Monitoring and Alerting | 10% |
| Debugging and Deploying | 10% |
| Ensuring Data Security and Compliance | 8% |
| Data Governance | 5% |
| Data Modelling | 5% |
What actually changes
Code moves to the centre. The Professional’s largest section is Developing Code for Data Processing using Python and SQL at 23%. The Associate has no equivalent — it tests platform operation rather than code you write.
Ingestion shrinks; optimisation grows. Ingestion falls from 21% to 12%, while Cost & Performance Optimisation appears at 15% with no Associate counterpart. The Professional assumes you can get data in and asks about CDC, sharing and federation instead.
New territory appears. Data manipulation (12%), with VARIANT and AI functions, and a distinct data modelling section (5%) have no Associate equivalent.
Everything gets more granular. Nine sections rather than seven, most of them smaller. That granularity means the Professional spreads thinner across more topics, so blind spots are harder to hide.
Which should you take?
Associate if you are new to Databricks data engineering, or you use the platform but have not been responsible for production pipelines. It is the natural first credential and covers the foundations the Professional assumes.
Professional if you already write production Spark and SQL, tune jobs for cost and performance, and own pipelines that other people depend on. The code and optimisation emphasis will suit you, and the Associate may feel like a formality.
Both, in order, if you are building a career on Databricks. The Associate is cheaper in effort and its content is genuinely assumed by the Professional.
Can you skip straight to Professional?
Yes — nothing prevents it. Whether you should depends on one question: do you write and tune production data processing code on Databricks today?
If yes, go straight there. If you mostly use notebooks and managed ingestion without owning performance, the Associate first is the better route. The Professional’s 23% code section and 15% optimisation section are unforgiving without that experience, and at 60 questions in 120 minutes there is less room to recover from a weak area.