Databricks is a cloud data platform built on Apache Spark that combines data engineering, analytics and machine learning on one storage layer. Its central idea is the lakehouse: keep data in open files in object storage — S3, ADLS or GCS — but put a transaction log over them so they behave like tables. That log is Delta Lake, and it is what gives the platform ACID transactions, schema enforcement and evolution, time travel to earlier versions, and MERGE for upserts on data that was previously append-only.
Compute is separate from that storage. Clusters and SQL warehouses are started, scaled and stopped independently, which is why cluster sizing, autoscaling and policy are cost decisions as much as performance ones. Underneath, Spark's Catalyst optimizer and Tungsten execution engine plan and run the work, and the practical performance skills are the ones that follow from the physical plan: partitioning strategy, shuffle behaviour, broadcast versus sort-merge joins, and diagnosing skew. Delta table maintenance — OPTIMIZE, Z-ordering or liquid clustering, and VACUUM — is what keeps read performance from degrading over time.
Around that sit the platform services. Workflows orchestrate multi-task jobs with dependencies and retries. Structured Streaming and Delta Live Tables handle continuous ingestion from Kafka, Auto Loader and change data capture sources. Unity Catalog provides the governance layer — a metastore spanning workspaces with catalogs, schemas, grants, lineage and audit. MLflow tracks experiments, versions models in a registry and serves them behind endpoints. Databricks SQL exposes the same tables to analysts and BI tools.
Why this skill matters now
Most organisations now hold far more data in object storage than in any warehouse, and the question has shifted from where to put it to how to make it trustworthy and queryable without copying it three more times. The lakehouse pattern answers that directly, and Databricks is the platform most enterprises evaluate first, which is why the skill appears in data engineering, analytics engineering and ML platform job specifications alike.
Cost is the second driver, and it is now a board-level conversation. Because compute is billed by the second and clusters are trivially easy to over-provision, a team that does not understand cluster policies, autoscaling behaviour, shuffle partitions and file layout will spend several times what the same workload needs. Employers have noticed that the same person who tunes the job also halves the bill.
Governance completes the picture. Unity Catalog turned access control, lineage and audit from an add-on into a design decision that has to be made before the first table is created, and migrating a workspace-scoped estate onto it afterwards is real work. Engineers who can design the catalog layout, the grant model and the pipelines together are the ones in demand.