Episode 57
How To Get Hired As A Data Engineer - w/ Sam
One of the twenty most-watched Ready Set Do episodes on YouTube right now.
Data engineering is the role people find after they get tired of vague 'learn data' advice. Sam makes the path concrete: what the job really asks for, which tools matter, and how to get hired without pretending you woke up fluent in all of it.
Who this is for
- You are trying to get hired without sounding like everybody else in the pile.
- You would rather hear Sam's version while the mess is still fresh than get another polished hindsight sermon.
Key takeaways
- Get Hired As A Data Engineer - w/ Sam
- Switching to Tech from a Communications Background
- Data engineering is the role people find after they get tired of vague 'learn data' advice.
- Sam makes the path concrete: what the job really asks for, which tools matter, and how to get hired without pretending you woke up fluent in all of it.
- Sam explains the bronze, silver, and gold convention often called medallion architecture. Bronze holds raw data, silver...
- Analysts commonly explain what happened through dashboards and business reporting, while data scientists may build...
Need the cleaner version?
I pulled the sharpest parts of this lane into a guide so you do not have to reconstruct the answer from memory later.
Fast scan timestamps
Read the complete transcript
The edited transcript keeps the speakers' ideas, timestamps, and specific details while removing repetition and filler.
Transcript-backed moments
A few lines worth stealing before you hand over the full hour.
Sam's opening argument is that data engineering is one of the least purely engineering jobs with engineering in its name. Moving data is only part of the work. A strong data engineer also makes product decisions, manages stakeholders, explains tradeoffs, and helps other teams understand why a pipeline should be designed a particular way.
The boundary between data engineering and analytics is not clean. A capable analyst may become a credible data engineer after adding software-engineering skills, because both roles need to understand data and its business meaning. The emphasis changes: engineers think more about source systems, movement, storage, reliability, and the form in which downstream users receive data.
A data engineer may first encounter information after an application has written it to an object store such as Amazon S3. From there, the engineer moves raw data into a usable platform or table format, applies transformations, and creates dependable inputs for analysts and data scientists. The exact ownership boundary varies by company rather than following one universal job description.
Sam explains the bronze, silver, and gold convention often called medallion architecture. Bronze holds raw data, silver contains cleaned or transformed data, and gold contains curated outputs ready for a business use such as a dashboard. Data engineers often build the pipelines between these layers, although analysts may share responsibility depending on the organization.
Analysts commonly explain what happened through dashboards and business reporting, while data scientists may build predictive or prescriptive models. Those roles still overlap: a data scientist needs analytical judgment, and an engineer needs enough business context to deliver the right data. The useful distinction is the problem each person owns, not a rigid list of tools.
Show notes
Data engineering is the role people find after they get tired of vague 'learn data' advice. Sam makes the path concrete: what the job really asks for, which tools matter, and how to get hired without pretending you woke up fluent in all of it. If data science has started to feel crowded, this is a cleaner door in.
More in Get Hired
Same mess. Different guest. Pick the next conversation that feels closest to your real life.