Why The Data Customer Isn't Always Right


Extract. Transform. Read.

A newsletter from Pipeline: Your Data Engineering Resource

Hi past, present or future data professional!

Data engineers get bothered a lot; but this is a good thing because stakeholders (a.k.a. our customers) know the value of the service and data we provide. Unfortunately, there can be a disconnect between how long a data engineer thinks something will take and how long a stakeholder is willing to wait, which is why it’s important to prepare responses to common delivery questions.

Fortunately, providing measured responses is a skill that can be developed; if you’re currently working a customer service role (as I did), you’d be surprised how transferable skills like courtesy and conflict resolution can be. Depending on your org (or future org), you’ll likely be expected to interface with data consumers in some way, and if your boss or whole team are out for a period of time, you’ll really be expected to step up your responsibilities.

Despite many departments within your org requesting data, one of your most “demanding” peers might be on your team. To thrive in your first quarter at work and beyond as a data engineer it’s critical to not only develop good relationships with senior team members, but do all you can to avoid being “annoying” and, instead, embrace self-sufficiency.

To avoid annoying you, here are this week’s links as formatted text:

Thanks for ingesting,

-Zach

Pipeline To DE

Top data engineering writer on Medium & Senior Data Engineer in media; I use my skills as a former journalist to demystify data science/programming concepts so beginners to professionals can target, land and excel in data-driven roles.

Read more from Pipeline To DE

Extract. Transform. Read. A newsletter from Pipeline Hi past, present or future data professional! Despite falling into the realm of engineering, data infrastructure construction is a bit like basic art. At times building a data pipeline is as simple as filling in one of those color-by-numbers books. Other times, the process of extracting and ingesting data can be as abstract and disconnected as paint flicked onto a canvas, Jackson Pollack style. No matter the complexity of your build, there...

Extract. Transform. Read. A newsletter from Pipeline Hi past, present or future data professional! To those in the U.S.: Happy Halloween! In the spirit of the spooky season, I’d like to scare—I mean warn—you about 3 truly creepy trends that might give you goosebumps during a job search. A Shady Recruiter “Ghost” Writing Your Resume When in the job market, one of the first things you learn, after how to write a resume, is how to format one. I’m sure you know about headings, bullet points, etc....

Extract. Transform. Read. A newsletter from Pipeline Hi past, present or future data professional! I recently participated in a technical design meeting that was derailed by a single, fundamental question. “Why?” Despite the fact that I worked with the particular data source we were discussing for nearly two years, I fell into the common trap of going “on autopilot” and failing to question the initial need for the data. At this point, you would think asking “why” of years’ worth of work would...