Hacking Analytics
Published in

Hacking Analytics

ON the evolution of Data Engineering

A few years ago being a data engineer meant managing data in and out of a database, creating pipelines in SQL or Procedural SQL and doing some form of ETL to load data in a data-warehouse, creating data-structures to unify, standardize and (de)normalize datasets for analytical purpose in a non-realtime manner. Some companies were adding to that a more front facing business components that involved building analytic cubes and dashboard for business users.

In 2018 and beyond the role and scope of data engineers has changed quite drastically. The emergence of data…




All around data & analytics topics

Recommended from Medium

Don’t Forget what ‘Deep’ & ‘Learning’ Actually Mean

The last SQL prep sheet for Data Analysis Interview

What the Bleep is Logistic Regression?

Using Neo4j graph database to analyze Twitter data

From zero to one: Building a Data Science company from scratch

From messy to tidy: the case for a data science workflow

Hacks for Getting into Data Science in 6 Months- Part 1: Road map

Coding the Volatility-Adjusted RSI in TradingView.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Julien Kervizic

Julien Kervizic

Living at the interstice of business, data and technology | Head of Data at iptiQ by SwissRe | previously at Facebook, Amazon | julienkervizic@gmail.com

More from Medium

The Data Vice No One Talks About: Data Hoarding.

A pile of appliances.

Want better data? Invest in your data engineers.

Files formats for Data Engineers — (Part 1) — Standards Data Formats

Data Warehousing — Why do I need one?