Corporate · onsite · online training worldwide
contact@DevOpsSchool.com· +91 99057 40781·
> Data Engineering & Lakehouse Platform · DevOpsSchool Trainer

Databricks Trainer

Private corporate batches, live online cohorts and 1-on-1 mentoring in the Databricks lakehouse — Spark tuning, Delta Lake, Structured Streaming, Unity Catalog and MLflow — taught by a practitioner who runs it in production.

20 years across DevOps, SRE and Security · 10,000+ engineers trained · Trained teams at JPMorgan Chase, Verizon, Nokia and the World Bank

DeliveryOnline · Onsite · Hybrid
FormatsCorporate · 1-on-1 · Cohort
AgendaCustomisable
Batch size8–30 engineers
Engineers we've trained work at
JPMorgan ChaseBank of AmericaWells FargoVerizonNokiaWorld BankGE HealthcareVMwareOracleQualcommMercedes-BenzAirbusDatadogSplunkDeloitteInfosysWiproCapgemini
# who teaches it

Your Databricks trainer

Rajesh Kumar

Principal DevOps Engineer & Architect

Early-bird MLOpsAIOps practitionerData platform operations20 years in productionPrincipal / architect roles10,000+ engineers trainedM.Tech BITS Pilani25+ certifications

Rajesh teaches Databricks from the physical plan outward — what Spark actually does with a query, where the shuffle happens, why a join spills, and how partitioning and file layout decide both runtime and bill. Delta Lake is taught through its transaction log rather than as a table format: how ACID guarantees are produced, what time travel costs, and why OPTIMIZE, Z-ordering and VACUUM are operational routine rather than optional. Sessions cover Structured Streaming with real checkpoint and watermark behaviour, Unity Catalog designed before tables exist rather than retrofitted, and MLflow through to served endpoints. Every performance claim in the room is demonstrated against the Spark UI with before-and-after timings and cost.

Twenty years across DevOps, SRE and Security, in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe and others. He has trained engineers at JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus — more than 10,000 people personally. He teaches what he runs, not what he reads.

One practitioner, not a bench

You are booked with a named engineer, and that is who turns up. Marketplaces and larger providers rotate whoever is free, so the person who sold you the agenda is rarely the person teaching it.

The same trainer is available for the next engagement, which matters when a team builds on what it learned last time.

18,000+certified learners
500+corporate batches delivered
50+countries served
100+certification programmes
# faculty

Who delivers Databricks engagements

Your batch is assigned a named trainer before it starts, and that is who teaches it. See the full faculty.

How your Databricks trainer is chosen

Engagements are matched on the tool, not the calendar. For Databricks that means a trainer who has run it in production — the Databricks lakehouse — Spark tuning, Delta Lake, Structured Streaming, Unity Catalog and MLflow — rather than whoever is free that week. You are told who is teaching before you commit, and that person is on the discovery call that shapes the agenda.

Where a batch is large enough to need a second trainer, the pairing is declared up front. The lead trainer stays accountable for the syllabus and the assessment either way.

Rajesh Kumar

Principal DevOps Engineer & Architect

India20 yrsLead trainer

Twenty years across DevOps, SRE and Security in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe, IBM/Emptoris, Ness, MindTree and Accenture. He has trained more than 10,000 engineers personally, at organisations including JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus. He teaches what he runs, not what he reads.

Nikhil Gupta

IndiaInstructorCoach

Pranab Kumar

IndiaInstructorCoach

Rohit Ghatol

IndiaInstructorCoach

Amit Agarwal

IndiaInstructorCoach

Anil Kumar

IndiaInstructorCoach

Balachandran Anbalagan

IndiaInstructorCoach

Durga Prasad

IndiaInstructorCoach

Gaurav Aggarwal

IndiaInstructorCoach

Harsh Mehta

IndiaInstructorCoach

Kapil Gupta

IndiaInstructorCoach

Kunal Jain

IndiaInstructorCoach

# how to engage

Four ways to work with this trainer

Private corporate batch

Teams of 8–30

Custom agenda, your timezone, onsite or online, NDA-friendly.

Request a quote

1-on-1 mentoring

Individual engineers

A private instructor and a curriculum built around your goal.

₹99,999

Live & Interactive cohort

Individuals who want peers

Scheduled batch, max 8 to 10 hours of live instruction.

₹34,999

Self-paced video

Self-starters

Full LMS access — 20+ courses and 50+ tools included.

₹833/mo
# private batches

Private Databricks training for your team

A private batch starts with a discovery call. We look at the stack you actually run — the CI system, the cloud, the constraints — and map the agenda onto it, so examples use your topology rather than a generic one.

Delivery is onsite at your premises, live online, or hybrid, scheduled around your release calendar rather than ours. Batches run 8 to 30 engineers.

Every attendee leaves with recordings, slides, lab repositories and a completion certificate. You receive an attendance and assessment report. Invoicing supports PO and GST.

Talk to us about a private Databricks batch

What you provide vs what we bring

  • You: the room or the call, and the engineers
  • Us: trainer, agenda, labs, assessment, certificates
  • Labs: we guide your team through provisioning their own free-tier cloud environment — the skill goes with them
# the technology

What is Databricks?

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.

Databricks training
# outcomes

What your team can do afterwards

Read a Spark physical plan and explain where a job spends its time and why
Tune shuffle partitions, joins and memory to fix skew, spill and small-file problems with measured results
Design Delta tables that stay fast — partitioning, Z-ordering or liquid clustering, OPTIMIZE and VACUUM
Implement CDC and upserts with MERGE, change data feed and time travel
Build incremental ingestion with Auto Loader and streaming pipelines with Structured Streaming and Kafka
Orchestrate production pipelines in Databricks Workflows with dependencies, retries and alerting
Design a Unity Catalog metastore with catalogs, schemas, grants, external locations and lineage
Track, register, tune and serve models with MLflow, and automate the lifecycle as MLOps
Control spend deliberately with cluster policies, autoscaling, instance choice and tag-based attribution
# curriculum

10 modules. Live demos in a real lab, not slides.

01The lakehouse, the workspace and Spark architectureLive & Interactive5 hrs · 2 assignments · 1 capstone

The mental model everything else depends on. What the lakehouse actually is at the file level, how the workspace, clusters, notebooks and jobs relate, and Spark's execution model — driver, executors, jobs, stages and tasks — plus the Databricks-specific optimisations layered on top of open-source Spark.

Topics: Lakehouse architecture: object storage plus a transaction log · Workspace, notebooks, repos, clusters, jobs and workflows · Spark architecture: driver, executors, jobs, stages, tasks, partitions · Databricks Runtime and its optimisations, including Photon · Cluster types: all-purpose, job, SQL warehouse, serverless · The key components in one picture: Delta Lake, Unity Catalog, MLflow, Databricks SQL · Reading the Spark UI: stages, tasks, shuffle and storage tabs · Medallion architecture: bronze, silver, gold as a working convention

  • Assignments: (1) Run one query three ways and account for the difference in the Spark UI; (2) Map an existing data flow onto a medallion layout and mark the gaps
  • Capstone: Produce an architecture note for a real pipeline with layer boundaries and table contracts
02Spark performance — plans, shuffles and joinsLive & Interactive5 hrs · 2 assignments · 1 capstone

The module that pays for the course. Reading logical and physical plans, understanding what triggers a shuffle and what it costs, the join strategies Spark chooses between and how to influence that choice, and the diagnosis of skew, spill and small files from evidence rather than folklore.

Topics: Catalyst optimizer and Tungsten execution: what each contributes · Logical and physical plans, and reading EXPLAIN output · Partitioning strategies: repartition, coalesce, partition sizing · Shuffle mechanics and spark.sql.shuffle.partitions · Join strategies: broadcast hash, sort-merge, shuffle hash · Adaptive Query Execution and what it fixes automatically · Data skew: detection, salting and skew join handling · Memory management, spill and executor sizing · Caching and persistence: when it helps and when it hurts · Photon: which workloads benefit and which do not

  • Assignments: (1) Take a skewed join from failing to passing and document the evidence trail; (2) Halve a job's runtime by changing only partitioning and join strategy
  • Capstone: Deliver a tuning report on a real job with plan analysis and before-and-after cost
03Delta Lake in depthLive & Interactive5 hrs · 2 assignments · 1 capstone

Delta as a transaction log rather than a file format. How ACID guarantees are produced and what concurrent writers do to each other, schema enforcement versus evolution, time travel and what retention it requires, then the maintenance operations that decide whether a table stays fast a year from now.

Topics: The Delta transaction log: commits, checkpoints, and how readers see a version · ACID guarantees, isolation levels and concurrent write conflicts · Schema enforcement, schema evolution and column mapping · Time travel: version and timestamp queries, RESTORE, retention · OPTIMIZE, file compaction and the small-file problem · Z-ordering and liquid clustering: what each solves · VACUUM, retention windows and the cost of getting them wrong · Deletion vectors and their effect on read and write paths · Table constraints, generated columns and identity columns · Deep and shallow clones for testing and recovery

  • Assignments: (1) Force a concurrent-write conflict and resolve it correctly; (2) Take a table with thousands of small files and restore its read performance
  • Capstone: Deliver a table maintenance policy with schedules, retention and measured impact
04Ingestion, CDC and incremental processingLive & Interactive5 hrs · 2 assignments · 1 capstone

Getting data in without reprocessing everything. Auto Loader for incremental file discovery at scale, COPY INTO for simpler cases, MERGE for upserts and deletes, change data feed for propagating changes downstream, and Delta Live Tables where declarative pipelines with expectations fit better than hand-written jobs.

Topics: Auto Loader: file notification vs directory listing, schema inference and evolution · COPY INTO and idempotent batch loads · MERGE INTO: upserts, deletes and matched-clause performance · Change data feed: enabling it and consuming changes downstream · CDC patterns from operational databases into bronze · Slowly changing dimensions type 1 and type 2 in Delta · Delta Live Tables: declarative pipelines, expectations, quality metrics · Streaming tables and materialized views · Idempotency and exactly-once semantics in practice

  • Assignments: (1) Build an Auto Loader pipeline that survives a schema change without failing; (2) Implement SCD type 2 with MERGE and prove correctness against test data
  • Capstone: Deliver a bronze-to-silver CDC pipeline with data quality expectations enforced
05Structured Streaming and real-time pipelinesLive & Interactive5 hrs · 2 assignments · 1 capstone

Continuous processing with the guarantees actually on offer. The Structured Streaming model against the older DStreams approach, checkpoints and offsets, trigger modes, watermarks and late data, stateful operations, and the Kafka integration details that determine whether a stream recovers cleanly after a restart.

Topics: Structured Streaming model versus DStreams · Sources, sinks, checkpoints and offset management · Trigger modes: continuous, fixed interval, availableNow · Event time, watermarks and handling late-arriving data · Stateful aggregations, joins and state store sizing · Kafka integration: offsets, partitions, backpressure, maxOffsetsPerTrigger · Streaming into and out of Delta tables · Restart, replay and recovery semantics · Monitoring streams: metrics, lag and progress reporting

  • Assignments: (1) Build a Kafka-to-Delta stream, kill it mid-batch and prove clean recovery; (2) Add a watermark and demonstrate its effect on late records
  • Capstone: Deliver a production streaming pipeline with monitoring, alerting and a restart runbook
06Workflows and production ETL at scaleLive & Interactive5 hrs · 2 assignments · 1 capstone

Turning notebooks into jobs a team can rely on. Multi-task workflows with dependency graphs, parameterisation, retries and timeouts, failure notification, job clusters versus shared compute, CI/CD from Git through Databricks Asset Bundles, and the environment promotion pattern that keeps production separate.

Topics: Workflows: multi-task jobs, dependencies, conditional and looping tasks · Parameters, task values and passing state between tasks · Retries, timeouts, failure handling and alerting · Job clusters vs all-purpose clusters and the cost difference · Scheduling, concurrency limits and queueing behaviour · Databricks Asset Bundles and infrastructure as code for jobs · Git integration, Repos and CI/CD promotion across workspaces · Testing pipelines: unit tests, data tests and staging data · Observability: system tables, job run history and lineage

  • Assignments: (1) Convert a notebook chain into a parameterised multi-task workflow with retries; (2) Promote a pipeline dev to prod through Asset Bundles with no manual step
  • Capstone: Deliver an ETL pipeline deployed entirely from Git with tests and alerting
07Unity Catalog, governance and securityLive & Interactive5 hrs · 2 assignments · 1 capstone

Access control designed before the tables exist. The metastore and its three-level namespace, storage credentials and external locations, the grant model including row filters and column masks, lineage and audit, and the practical work of migrating a workspace-scoped Hive metastore estate onto Unity Catalog.

Topics: Metastore, catalogs, schemas and the three-level namespace · Storage credentials, external locations and managed vs external tables · Users, groups, service principals and identity federation · GRANT model, ownership and privilege inheritance · Row filters, column masks and dynamic views · Lineage capture, audit logs and system tables · Delta Sharing for sharing data outside the workspace · Migrating from Hive metastore to Unity Catalog · Data classification, tagging and access review practice

  • Assignments: (1) Design a catalog and grant model for three teams with least privilege; (2) Apply a row filter and prove two users see different data from one table
  • Capstone: Deliver a governance design with catalog layout, grants, masking and audit reporting
08Machine learning with SparkML and MLflowLive & Interactive5 hrs · 2 assignments · 1 capstone

Model building on the same platform as the data. MLlib and SparkML pipelines for distributed training, feature engineering and the feature store, hyperparameter tuning with grid, random and Hyperopt search, and MLflow tracking that makes an experiment reproducible rather than a notebook nobody can rerun.

Topics: MLlib and SparkML: transformers, estimators and pipelines · Feature engineering at scale and the feature store · Training distributed models on Spark and when not to · Hyperparameter tuning: grid search, random search and Hyperopt · MLflow tracking: runs, parameters, metrics, artefacts and autologging · Comparing runs and reproducing an experiment months later · Model registry: versions, aliases and stage transitions · Model evaluation, validation and fairness checks · Working with single-node libraries alongside Spark

  • Assignments: (1) Build and tune a classification pipeline with tracked experiments; (2) Reproduce a colleague's model result from MLflow alone
  • Capstone: Deliver a registered, evaluated model with a documented reproducible training run
09MLOps and model servingLive & Interactive5 hrs · 2 assignments · 1 capstone

Getting models into production and keeping them honest. Serving endpoints and their scaling behaviour, batch and streaming inference against Delta tables, CI/CD for model promotion, monitoring for drift and quality regression, and the retraining trigger that closes the loop.

Topics: Model Serving endpoints: deployment, scaling, cold starts and cost · Batch and streaming inference patterns against Delta tables · CI/CD for models: automated testing, approval and promotion · Champion and challenger deployments and traffic splitting · Inference tables, monitoring and drift detection · Data and model quality alerts and retraining triggers · Lineage from feature to model to prediction under Unity Catalog · Cost and latency trade-offs in serving architecture

  • Assignments: (1) Deploy a registered model to an endpoint and load-test its latency; (2) Detect drift on a served model and trigger a retraining workflow
  • Capstone: Deliver an end-to-end MLOps flow from training through serving to monitored retraining
10Cloud integration, scaling and cost controlLive & Interactive5 hrs · 2 assignments · 1 capstone

Operating the platform for a bill you can defend. Connecting to cloud storage and warehouses correctly, cluster policies that constrain what users can start, autoscaling and spot behaviour, SQL warehouse sizing, and cost attribution through tags and system tables so spend can be traced to a team.

Topics: Cloud storage integration: S3, ADLS Gen2 and GCS with proper credentials · Querying and federating external warehouses such as Redshift, BigQuery and Snowflake · Databricks Connect and external development workflows · Cluster policies, instance pools and constraining user choice · Autoscaling behaviour, spot and preemptible instances, and their failure modes · Serverless SQL warehouses: sizing, scaling and concurrency · Photon and instance family selection for cost per unit of work · Tagging, budget policies, system billing tables and cost attribution · Right-sizing large jobs and identifying the top ten spenders

  • Assignments: (1) Write a cluster policy that prevents the three most expensive mistakes; (2) Attribute one month of spend to teams using tags and system tables
  • Capstone: Deliver a cost-optimisation review with measured savings and enforced guardrails

Need this mapped to your stack?

We rebuild the agenda around the tools you actually run.

Request a custom agenda
# hands-on

Labs and capstones your engineers actually build

LAB · PERFORMANCE

Fix the skewed join

Take a job that fails on a skewed join, diagnose it from the Spark UI, apply salting and AQE settings, and record the runtime and cost difference.

sparkskewaqe
LAB · DELTA

Rescue a table full of small files

Degrade a Delta table with thousands of tiny files, then restore read performance with OPTIMIZE, clustering and a VACUUM policy you can justify.

delta lakeoptimizez-order
LAB · INGESTION

CDC into a silver table

Build an Auto Loader bronze layer, apply MERGE-based SCD type 2 into silver, and prove correctness against a test dataset with expectations.

auto loadermergecdc
LAB · STREAMING

Kill the stream, restart it clean

Run a Kafka-to-Delta Structured Streaming job, terminate it mid-batch, and demonstrate exactly-once recovery from checkpoints and offsets.

structured streamingkafkacheckpoints
LAB · GOVERNANCE

Two analysts, one table, different rows

Design a Unity Catalog layout with grants, row filters and column masks so two users query the same table and legitimately see different data.

unity catalogrow filterslineage
CAPSTONE · PLATFORM

Pipeline and model, deployed and costed

Ship a Git-deployed workflow from ingestion to a served model, governed by Unity Catalog, with monitoring, alerting and a defended cost per run.

workflowsmlflowcost
# ecosystem

The tools Databricks sits next to

Apache Spark
Delta Lake
Unity Catalog
MLflow
Apache Kafka
AWS S3
Azure Data Lake Storage
dbt
Terraform
Power BI
Airflow
Python

Who this is for

  • Data engineers building and tuning production pipelines on Databricks
  • Analytics engineers moving from warehouse-only SQL to lakehouse tables
  • Platform engineers responsible for workspace governance, clusters and cost
  • Machine learning engineers using MLflow for tracking, registry and serving
  • SREs and data operations engineers supporting streaming and batch workloads
  • Architects designing a lakehouse migration and its Unity Catalog governance model

Pre-requisites

  • Working SQL — joins, aggregates, window functions and query reasoning
  • Python at a working level, including DataFrame-style APIs such as pandas
  • Basic understanding of distributed processing or a willingness to cover it in module 01
  • Familiarity with cloud object storage and identity concepts on AWS, Azure or GCP
  • A Databricks workspace — trial, community or corporate — plus a cloud account for storage
# pricing

Straightforward pricing

Every plan includes 1 year of full LMS access — not just this course, the entire DevOpsSchool LMS: 20+ courses, 50+ tools, videos, quizzes, assignments and projects.

Self-paced video

₹833/mo

Billed yearly at ₹9,996

Enroll now

1-on-1 mentorship

₹99,999

Full program, private instructor

Enroll 1-on-1

Corporate / private batch

8–30 engineers · custom agenda · onsite or online · PO and GST invoicing

Get a custom quote

Refunds. If we cancel or postpone a cohort, you get a full refund within 15 days. There is no money-back guarantee otherwise.

Terms. Course material remains licensed to the attendee. Read the terms.

Your data. We don't share it with third parties. Privacy policy.

Every attendee gets a verifiable certificate

  • Issued per attendee on completion
  • Verifiable at devopsschool.com/certificates
  • Hard copy available on request
  • Corporate batches receive an attendance and assessment report
DevOpsSchool

Databricks Training

Certificate of completion

# feedback

What engineers say

4.4 / 5 from 26 reviews on Trustpilot.

★★★★★
Great learning experience from a very knowledgeable instructor with well-prepared course notes. The lab exercises on AWS instance work well to learn the hands-on side of the course.
Ando Gg · Trustpilot
★★★★★
Rajesh is a very good trainer I have experienced in DevSecOps training. The number of contents in different topics he has posted on the DevOpsSchool public website are amazing and user friendly for beginners and experienced professionals.
Ashutosh Mishra · Trustpilot
★★★★★
The trainer (Rajesh) provided very good sessions on SRE profession. Not only hands-on learning on the tools but also SRE mindset.
Peter Wang · Trustpilot
★★★★★
Very good training session. Well explained from the basics to the complex concepts. Also tried to cover practicals and demos within the 3 hour sessions. The learning content and videos are of a great deal of help.
Sreekanth Kannoth · Trustpilot
★★★★★
Basics explanation was exemplary from Rajesh where he dealt with complicated topics to be simple. Great learning stuff personally for me.
Krishna Mohan Yelleti · Trustpilot
★★★★★
Very detailed explanation and has lots of patience in attending the questionnaire. Thanks again for your wonderful sessions.
Uttam Samudrala · Trustpilot
# comparison

Why a named practitioner beats a marketplace listing

What mattersYouTube + blogsGeneric online courseFreelance marketplaceDevOpsSchool
Named practitionerNoRarelyVaries per bookingYes — same trainer each time
Production experienceUnknownUnknownUnverified20 years, named employers
Custom agendaNoNoSometimesBuilt from your stack
Onsite deliveryNoNoSometimesYes
Lab environmentNoneSandbox that expiresVariesYour own cloud — skill goes with you
AssessmentNoneQuizRarelyAssignments + capstone per module
Per-attendee certificatesNoSometimesRarelyYes
Corporate invoicingNoLimitedVariesPO and GST
Post-training supportNoneForum, time-limitedNoneLifetime forum access
# questions

Frequently asked

Can the agenda be customised for our stack?
Yes — that is the normal case for a private batch. We start with a discovery call, look at your cloud, ingestion sources, governance position and whether ML is in scope, and rebuild the module list around them. Labs then use data shaped like yours.
Do you deliver onsite?
Yes. Private batches run onsite at your premises, live online, or hybrid. You provide the room and the engineers; we bring the trainer, agenda, labs, assessment and certificates.
What lab environment do we need?
Attendees use a Databricks workspace — a corporate one where policy allows, otherwise a free trial or Community Edition — plus a cloud account for object storage. We guide the setup and keep lab clusters small enough to stay inside trial credits.
Is this a data engineering course or a machine learning course?
Both are covered, and most batches pick one. Modules 01 to 07 form a data engineering track; modules 08 and 09 add the ML and MLOps track. Mixed batches usually run the engineering track with one ML day.
Do you cover Spark fundamentals or assume them?
Module 01 covers the execution model properly, so engineers new to Spark can follow. Module 02 then goes well beyond fundamentals into plans, shuffles and skew, which is where experienced Spark users get value.
Can you help with our cost problem specifically?
Yes. Module 10 is often expanded into a dedicated engagement: cluster policies, instance selection, autoscaling behaviour, SQL warehouse sizing and tag-based attribution against your own billing system tables, with measured savings.
Do you teach Delta Live Tables?
Yes, in module 04, alongside hand-written Structured Streaming. We are explicit about the trade-off — DLT reduces boilerplate and gives you expectations and lineage, but it constrains control, and not every pipeline should use it.
What size are batches?
Private corporate batches run 8 to 30 engineers. Public Live & Interactive cohorts are capped at 10 so everyone gets time with the trainer.
Do attendees get a certificate?
Yes — every attendee receives a completion certificate, verifiable at devopsschool.com/certificates. Corporate batches also receive an attendance and assessment report.
What happens if someone misses a session?
Sessions are recorded and available in the LMS, and attendees keep LMS access for a year. For public cohorts, a missed session can be picked up in a later batch.
What is your refund position?
If we cancel or postpone a cohort, you receive a full refund within 15 days. There is no general money-back guarantee, and GST and gateway fees are not refunded.

Still deciding?

Tell us the team, the stack and the timeline. You'll get a straight answer, not a sales sequence.

Talk to an advisor
# ready when you are

Book a Databricks trainer — or ask a question first.

  • No spam, no drip sequence
  • Syllabus in 60 seconds
  • A human reply within one business day

Prefer to call or email?

More ways to reach us on the contact page.

Talk to an advisorRequest a quote