Extract. Transform. Read.

A newsletter from Pipeline​

Hi past, present or future data professional!

When you apply to data analysis, data engineering or data science jobs, you likely consider factors like company name, culture and compensation. Caught up in the excitement of a fresh opportunity or compelling offer you’re neglecting an important part of your day-to-day reality in a new role: What stage of data maturity the organization is in. If you’re looking for experience building something new from the ground up, you likely won’t find it in a company that has a years-old established cloud infrastructure. If you’re inexperienced, you might also feel lost in a company that is still conceptualizing how it is going to establish and scale its data infra.

While I personally arrived at a team and organization in its mid-life stage, I’ve had opportunities to discuss, examine and advise those who are considering how they can make an impact at an earlier-stage company in both full-time and contract roles. This compelled me, after a transatlantic flight, to compile a framework you can use to conceptualize anything from an in-house data solution to full-fledged infrastructure.

Phase 1

Discovery - Extensive, purposeful requirements gathering to make sure you are providing a solution and, more importantly, a service, to an end user.

Phase 2

Design - You can’t begin a journey or a complex technical build without a road map; take time to make a wish list of must-have data sources and sketch your architecture before writing line 1 of code.

Phase 3

Ingestion - Build your pipelines according to best practices with a keen eye on cost and consumption; expect this to take 6-12 months depending on your work situation.

Phase 4

Downstream Build - Going hand-in-hand with requirements gathering, consider how your target audience will use what you’ve built; might it be better to simplify or aggregate data sources in something like a view?

Phase 5

Quality Assurance And Ongoing Tasks - Even though your pipelines and dashboards will be automated initially, nothing in data engineering is 100% automated. Components will break. You’ll be expected to fix them. And assure it doesn’t happen again.

These 5 phases aren’t meant to be strict rules for building data infra. But they should get you thinking about how to build something purposefully so you can spend your time dealing with angry code–not stakeholders.

Dive into the framework here.

Here are this week’s links:

• ​Why I Nearly Turned Down A 30k Raise And A Data Engineering Job​
• ​6 Months Ago I Built My Own Data Infra. Why I'm Now Tearing It Down.​
• ​Data Engineering Requirements Gathering​
• ​How Data Engineers Can Use SQL to Estimate BigQuery Storage Costs​
• ​The Simple Reason Your Data Pipelines Will Never Be 100% Automated​
• ​From 0 To Data Solution In 5 Phases To Land Contracts & Wow Bosses​

Until next time–thanks for ingesting,

-Zach Quinn