[ETR #101] Why The Hottest Data Job Is A Waste Of Time


Hi fellow data professional!

The best data skills to develop right now might just be cutting and measuring.

While that statement might be a bit facetious, the hot media narrative is to push the idea of blue collar work as a viable fallback if you’re having trouble breaking into a conventional tech role.

Outlets like CNN have touted the fact that data center engineer is the hottest role in tech.

Executives, specifically Nvidia’s Jensen Huang, speculate that data center construction (despite facing massive backlash around the world) will fuel a “blue collar” gold rush.

The inherent problem in this statement is while it might be true it’s not going to apply to entry-level roles.

Being a tradesman has its own barriers to entry that anyone suggesting “pivot to the trades” conveniently omits.

There are strict union requirements, years of grueling apprenticeships and your prize is decades of backbreaking labor.

Long-term there will likely be opportunities for those with these skill sets, but even blue collar roles will be oversaturated and wages deflated.

Choosing to abandon your current path or “pivot” is no light decision and misleading narratives don’t offer comfort for those who may be experiencing doubt in their future job prospects.

For me, choosing to abandon the liberal arts and pursue a data science masters degree was not a light decision.

I’ve talked about criteria for transitioning, so I’ll end with discussing when and why I hit a wall. Maybe this echoes feelings you’re having in your current profession or role.

Or simply validates the very human need for change.

My “wall” consisted of:

  • Un-fulfilling work: Journalism school basically just prepares you to work in local news
  • Lack of job security: With more conglomerations scooping up local affiliates, localized media positions don’t have the best job security
  • Long advancement horizon: To advance to “big” positions usually requires 5-10 years jumping between smaller markets
  • HCOL (high cost of living) relative to low salary: Living in media hubs from New York to LA requires a salary inconsistent with entry-level work; when I interned in NYC I worked two jobs to make ½ rent

Even my “industry leap” happened over 2 years between deciding to go to school for data science and landing my first job.

Inverting these bricks in the wall would provide pretty reasonable expectations for someone seeking to vet a role, org or career path.

Understandably, you’d want work that provides some degree of:

  • Fulfillment
  • Job security (to the extent possible in this economy)
  • Plentiful advancement opportunities over time
  • Salaries consistent with the market and that facilitate living in MCOL or HCOL areas

Any industry experiencing a “boom” is unlikely to provide these traits to new hires.

You might be able to nab a high salary building data centers but what’s the longevity there? What is the switching cost to begin a role which might be entirely new to you?

Professional moves are referred to as “transitions” because they happen gradually.

Before you succumb to hype about one industry booming and another going bust, ask yourself how long it would take you to personally gain a foot hold?

Is your personal wall dense enough with reasons to make a drastic move? Or does it make more sense to take a breath and stay the course?

Either path is fine but facilitate your own discovery; a month from now that headline will probably be different.

Speaking of staying the course, if you are committed to navigating the current data landscape without chasing the latest media hype cycles, you need a predictable, production-grade roadmap.

For the past few months, I’ve been working quietly behind the scenes to centralize my entire data engineering career blueprint. I’m talking about taking 5 years of cloud experience, production code templates, and the exact pathway I used to break out of the media industry, and packing it into a single, high-utility resource.

On June 16th, I’m officially opening the doors to a select group of founding members.

If you want to stop patching together scattered online tutorials and learn how to build architectures that actual engineering managers care about, you'll want early access to this.

👉 Click here to get on the early bird notification list.

More details to come next week.

Thanks for ingesting,

-Zach Quinn

Medium | LinkedIn | Ebooks

Extract. Transform. Read.

Reaching 20k+ readers on Medium and over 3k learners by email, I draw on my 4 years of experience as a Senior Data Engineer to demystify data science, cloud and programming concepts while sharing job hunt strategies so you can land and excel in data-driven roles. Subscribe for 500 words of actionable advice every Thursday.

Read more from Extract. Transform. Read.

Hi fellow data professional! SQL Lite, the database you most likely learned SQL on, is built atop 100k lines of source code. Sound like a lot? Compare that to Chromium, the engine for Google Chrome, which boasts 30+ million lines of code under the hood. Shortly after acquiring Twitter/X, the world's first trillionaire, Elon Musk, famously asked engineers to tell him how many lines of code they wrote per day, igniting a debate among engineers throughout the software and data domains. When I...

Hi fellow data professional! If you read my note on Tuesday you’ll know I’m coming off of the data engineering week from hell that seeped into my personal life, and delayed the launch of something cool I was planning to share with you; if you want to know more about that, scroll to the end of this message. Last week a flagship data source had a major problem and since it’s within my ownership area, I was the one with the knowledge and responsibility to fix it. I wanted to share the experience...

Hi fellow data professional! Hardly a work day goes by without receiving a request from a data analyst. They range from the mundane “Can you add this column?” to the occasional emergency “The data didn’t load all weekend and the leadership call starts in 15 minutes!” At the end of a jam-packed week I received an unusual request: Help with a Python script. My teammate wanted to know: Best practices How to commit to GitHub What the best way to deploy is They admitted the task was simple,...