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 landing. Then his manager asks for one call where the answer wasn't obvious, he framed it, and he lived with the result. Sam starts three different sentences. None of them finish.


The packet is full of work and empty of decisions. Sam thinks what he's missing is a chair at the architecture review table. It isn't.


In this episode:

- What the architecture review was ever supposed to prove, and why the room was never the proof

- The one test to run on any call you've made, with no meeting, no invite and no template required

- The two paragraphs that turn a design doc from a build plan into a decision somebody can audit nine months later

- How to run the whole thing in a Slack thread on a four-person team with no review process


For Databricks data engineers building a case for senior, especially where architecture reviews are rare or don't exist. You'll walk away able to tell work you did apart from a decision you can prove you owned.


---

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 week.


LinkedIn: linkedin.com/in/jrlasak

Newsletter: dataengineer.wiki


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

Podden och tillhörande omslagsbild på den här sidan tillhör Jakub Lasak. Innehållet i podden är skapat av Jakub Lasak och inte av, eller tillsammans med, Poddtoppen.