Build the platform or use the platform: the two Databricks data engineer tracks nobody names

Build the platform or use the platform: the two Databricks data engineer tracks nobody names

Two Databricks engineers sit at adjacent desks. Same title, same pay, same words in the ladder document. Watch a year go by, and they are not doing the same job.


Both get rated strong. Both get told they're ready for more scope. Nobody says the useful thing: the evidence those two are stacking isn't interchangeable, and one of those years makes no sense on the other one's promotion packet.


In this episode:

- Why the data engineering ladder quietly forks, and why that fork is missing from every ladder document

- The five-minute question that tells you which track your last year of Databricks work actually built toward

- How each track reaches staff, and the very different proof each demands

- Where each track stalls a good year, and what to say in your next one on one to get moved off it


This episode is for Databricks data engineers past the junior stage who keep getting strong reviews and vague answers about what's next. Whether you write the cluster policies and ingestion frameworks or ship the tables the business argues from, you'll walk away able to name your track and ask for the work that gets you to the next rung.


---

Helping 18,000+ Databricks data engineers become seniors: interview like seniors, execute like seniors, think like seniors.


Follow The Databricks Data Engineer for new episodes every Monday, Wednesday, and Friday.


LinkedIn: linkedin.com/in/jrlasak

Newsletter: dataengineer.wiki


#DataEngineering #Databricks #DataEngineer #CareerGrowth #ApacheSpark #DeltaLake

Det här avsnittet är hämtat från ett öppet RSS-flöde och publiceras inte av Podme. Det kan innehålla reklam.

Avsnitt(27)

Can You Reach Senior Databricks Engineer Without Ever Leading an Architecture Review?

Can You Reach Senior Databricks Engineer Without Ever Leading an Architecture Review?

Sam is four years into a Databricks role, up for senior this cycle. Merged pull requests on the ingestion layer. The nightly job he rescued at three in the morning when the orders table stopped landin...

28 Sep 11min

Why Databricks serverless exists, and which of your jobs should stay on classic clusters

Why Databricks serverless exists, and which of your jobs should stay on classic clusters

Open the workspace. Start a cluster. Get coffee. Come back, and sometimes it's ready. If you've been doing this a few years you can feel that wait in your shoulders, and it's the least interesting par...

21 Sep 12min

How Databricks engineers lose the final round (and the 4 places it happens)

How Databricks engineers lose the final round (and the 4 places it happens)

You cleared the recruiter screen. You cleared the Databricks technical round, and cleared it well. Then the final round, then the email that says strong candidate, tough decision. You go back looking ...

14 Sep 10min

The real reason your Databricks week never got simpler - it isn't the lakehouse

The real reason your Databricks week never got simpler - it isn't the lakehouse

Your org finished the migration. Two systems became one. The nightly copy nobody wanted to own is gone, and so is the quarterly meeting where finance and the data science team each showed up with a re...

7 Sep 11min

The Databricks incident where the most senior engineer never touched the keyboard

The Databricks incident where the most senior engineer never touched the keyboard

Thursday, just after two in the afternoon. The first message doesn't come from an alert, it comes from a person in revenue operations: the biggest region jumped overnight and nobody sold anything new....

31 Aug 11min

9 Databricks decisions that reveal your real seniority (and one that only looks senior)

9 Databricks decisions that reveal your real seniority (and one that only looks senior)

Three in the morning. The nightly job that loads the orders table died halfway. Half the tasks are green, and the rerun button is right there. What you do in the next ten seconds says more about your ...

24 Aug 11min

The Databricks job market in 2026: there are two of them, and only one answers

The Databricks job market in 2026: there are two of them, and only one answers

One engineer tells you hiring is back and recruiters are warm again. The next one is sixty applications deep and hearing nothing. Same month, same platform, sometimes the same city.That sounds like no...

17 Aug 11min

Databricks broadcast joins: when the memo beats the meeting (and when it kills a task)

Databricks broadcast joins: when the memo beats the meeting (and when it kills a task)

Two engineers on the same team join the same big orders table to the same small lookup table. Same cluster, same data, one line of code different. Sarah's finishes in the time it takes to get a coffee...

10 Aug 10min

Populärt inom Teknik

natets-morka-sida
uppgang-och-fall
elbilsveckan
bilar-med-sladd
market-makers
rss-laddstationen-med-elbilen-i-sverige
skogsforum-podcast
rss-en-ai-till-kaffet
rss-elektrikerpodden
rss-technokratin
rss-ai-med-jonas-benjamin
rss-uppgang-och-fall
rss-sakerhetspodcasten
rss-veckans-ai
rss-snacka-om-ai
bli-saker-podden
developers-mer-an-bara-kod
rss-powerboat-sverige-podcast
rss-it-sakerhetspodden
rss-fabriken-2