What Is Your 3-Year Data Engineering Plan?


The Latest From Pipeline: Your Data Engineering Resource

Hi past, present or future data professional!

I hope you’ll indulge my sharing of an important career milestone; unfortunately, I’m not retiring with a gold Rolex snug on my wrist.

Instead, this week marks 3 years in data engineering.

I’m excited about this work-iversary because it marks a period of time in which I’ve been working in data engineering longer than my prior non-data job. If you’ve read my work you know I’ve taken an unconventional path to break into data engineering and to advance to a senior role. Ideating, writing and publishing code, projects and stories has been central to my success in standing out as a candidate with nearly zero pre-job experience.

Additionally, here are 3 lessons that have helped me break in, gain proficiency and advance in a competitive and complex role.

  • Breaking in: Don’t undervalue (or oversell) yourself
  • Gaining proficiency: Break, fix and move on
  • Climbing the ladder: Consistency is key; execution is king

To understand how I learned and put these lessons into practice, read the latest here.

And if you want to know one of the most surprising lessons I’ve learned in 3 years, read this.

Until next time–thanks for ingesting,

-Zach Quinn

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! 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,...

Hi fellow data professional! It finally happened. I fell for a job scam. Luckily I realized my naivety after responding to the initial email. But let’s back up. We’ll examine Why this particular attempt was so “real” What made me skeptical How to prevent this from happening to you Established professionals in any field have the privileged problem of receiving unsolicited recruiter inquiries. If it’s from a random firm I typically move it to junk; if it’s a big name company, I give a look...