It has been lately called that ‘data scientist’ is the sexiest job of the 21st century. However, now, data engineering jobs are poised to give data scientists tough competition. Data Engineering Jobs are getting more popular than Data Science jobs.
So once you’ve decided data engineering is the field for you, you need to understand that becoming a great data engineer is a journey and not a destination. Everyone talks about success stories and what to do for it, but nobody talks about the nuances of what not to do and where not to waste time.
It does not come easy. Industry experts keep complaining that there is a large gap between self-educated data engineer’s skills and real-world work in the field of data engineering.
In this article, I will discuss the common mistakes data engineers make in their learning path(I have made some of them myself). I have also provided tips wherever applicable with the aim of helping you avoid these pitfalls on your data engineering journey.
Mistake #1: Not making data fundamentals strong
Mistake #2: Learning outdated/ legacy skills/technologies
Mistake #3: Missing the required depth/ breadth of topics
Mistake #4: Not doing ample hands-on practice
Mistake #5: Unable to visualize and understand the end to end picture
The first and foremost mistake data engineers make is not making their fundamentals base learning strong enough. A data engineer is expected to be reasonably good in coding/scripting and SQL as well. Without being able to work on simple programs if a data engineer directly jumps to write a complex data pipeline, it is definitely going to be a mess of a code.
Also, a data engineer should be conversant enough in the basics of databases and relational database management systems as well. Not understanding the difference between a primary key and a surrogate key is going to create problems even to define a simple data model.
The second common mistake data engineers do is to learn outdated technologies too much in-depth like learning too much in-depth Map Reduce OR Data warehousing concepts in Kimball /Inmon or some DWBI(Data Warehousing Business Intelligence ) tools which are not being used readily in the industry today. Time is a precious thing, learners can’t afford to miss focus on their learning priorities. It’s better to see the job descriptions and pick the most common skills like Spark, Kafka, NoSQL, Flink, etc rather than spending time and effort on outdated tools and techniques. But, do learn how to create Data models on NoSQL and Data lake systems.
I agree there are too many topics to be studied, there is Spark or Hive. Then, there are Kafka, NoSQL databases like Hbase or MongoDB. In-stream analytics, we have Spark streaming or Flink. On the cloud side, we have AWS, Azure, and GCP. So is it mandatory to be thorough in all of these tools and technologies? Absolutely not.
The need is to be proficient in the fundamental concepts in these data processing tools e.g how Spark internals work, how Kafka Pub-Sub mechanism works, and how NoSQL is different from SQL when to use which one. Preferably, we should go with any one of the options rather than focusing on everything.
Personal recommendation is to just learn one programming language: Scala/Python, Kafka, Spark, MongoDB/Hbase, and finally AWS for Cloud. Sometimes it is better to go with tools used in current projects when you don’t have an option.
This is something of paramount importance. Everyone just completes theory by reading documentations and some videos but no one really does the hard work of actually writing an end-to-end pipeline themselves. This not only leads to surprises and hiccups while working on actual projects but also shows the shallow knowledge when the interviewer starts to grill on the project hand on the part.
The recommendation is to start with a public dataset and a real-time API(e.g. Twitter etc). Ingest the dataset into Storage like HDFS and Kafka. Process it using Spark SQL/DS and Streaming(for real-time API data). Finally, presenting the insights in a visualized form like Tableau will add icing to the cake.
Performance optimization of the initial build of pipelines can further increase your chances of cracking the interviews.
Finally, without knowing the end-to-end pipeline just focusing on ingestion or storage or processing will not make the data engineer understand what is going on with his/ her work. Apart from knowing business impact data engineers should also understand the technical architecture and system design of the data pipelines and supporting frameworks.
Things like DevOps, Platform Infrastructure, and Networking are completely ignored by data engineers. These are critical aspects and supporting frameworks that are definitely important to understand the end-to-end picture. A basic overview of these supporting frameworks is definitely important if not in-depth.
Hope you had a good time reading the 5 common mistakes data engineers make, do share your experiences and any questions on the above.
The media shown in this article are not owned by Analytics Vidhya and is used at the Author’s discretion.
13 Common Mistakes Amateur Data Scientists Make...
Want to Become a Data Engineer? Here’s a ...
9 Books Every Data Engineering Aspirant Must Read!
Most Used Data Engineering Tools
A Quick Overview of Data Engineering
9 Must-Have Skills to Become a Data Engineer!
Step-by-Step Roadmap to Become a Data Engineer ...
Data Engineer Job Description, Responsibilities...
Infographic – 13 Common Mistakes Amateur ...
The DataHour Synopsis: Learning Path to Master ...
We use cookies essential for this site to function well. Please click to help us improve its usefulness with additional cookies. Learn about our use of cookies in our Privacy Policy & Cookies Policy.
Show details
This site uses cookies to ensure that you get the best experience possible. To learn more about how we use cookies, please refer to our Privacy Policy & Cookies Policy.
It is needed for personalizing the website.
Expiry: Session
Type: HTTP
This cookie is used to prevent Cross-site request forgery (often abbreviated as CSRF) attacks of the website
Expiry: Session
Type: HTTPS
Preserves the login/logout state of users across the whole site.
Expiry: Session
Type: HTTPS
Preserves users' states across page requests.
Expiry: Session
Type: HTTPS
Google One-Tap login adds this g_state cookie to set the user status on how they interact with the One-Tap modal.
Expiry: 365 days
Type: HTTP
Used by Microsoft Clarity, to store and track visits across websites.
Expiry: 1 Year
Type: HTTP
Used by Microsoft Clarity, Persists the Clarity User ID and preferences, unique to that site, on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
Expiry: 1 Year
Type: HTTP
Used by Microsoft Clarity, Connects multiple page views by a user into a single Clarity session recording.
Expiry: 1 Day
Type: HTTP
Collects user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
Expiry: 2 Years
Type: HTTP
Use to measure the use of the website for internal analytics
Expiry: 1 Years
Type: HTTP
The cookie is set by embedded Microsoft Clarity scripts. The purpose of this cookie is for heatmap and session recording.
Expiry: 1 Year
Type: HTTP
Collected user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
Expiry: 2 Months
Type: HTTP
This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected includes the number of visitors, the source where they have come from, and the pages visited in an anonymous form.
Expiry: 399 Days
Type: HTTP
Used by Google Analytics, to store and count pageviews.
Expiry: 399 Days
Type: HTTP
Used by Google Analytics to collect data on the number of times a user has visited the website as well as dates for the first and most recent visit.
Expiry: 1 Day
Type: HTTP
Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels.
Expiry: Session
Type: PIXEL
cookies ensure that requests within a browsing session are made by the user, and not by other sites.
Expiry: 6 Months
Type: HTTP
use the cookie when customers want to make a referral from their gmail contacts; it helps auth the gmail account.
Expiry: 2 Years
Type: HTTP
This cookie is set by DoubleClick (which is owned by Google) to determine if the website visitor's browser supports cookies.
Expiry: 1 Year
Type: HTTP
this is used to send push notification using webengage.
Expiry: 1 Year
Type: HTTP
used by webenage to track auth of webenagage.
Expiry: Session
Type: HTTP
Linkedin sets this cookie to registers statistical data on users' behavior on the website for internal analytics.
Expiry: 1 Day
Type: HTTP
Use to maintain an anonymous user session by the server.
Expiry: 1 Year
Type: HTTP
Used as part of the LinkedIn Remember Me feature and is set when a user clicks Remember Me on the device to make it easier for him or her to sign in to that device.
Expiry: 1 Year
Type: HTTP
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries.
Expiry: 6 Months
Type: HTTP
Used to store information about the time a sync with the AnalyticsSyncHistory cookie took place for users in the Designated Countries.
Expiry: 6 Months
Type: HTTP
Cookie used for Sign-in with Linkedin and/or to allow for the Linkedin follow feature.
Expiry: 6 Months
Type: HTTP
allow for the Linkedin follow feature.
Expiry: 1 Year
Type: HTTP
often used to identify you, including your name, interests, and previous activity.
Expiry: 2 Months
Type: HTTP
Tracks the time that the previous page took to load
Expiry: Session
Type: HTTP
Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings
Expiry: Session
Type: HTTP
Tracks percent of page viewed
Expiry: Session
Type: HTTP
Indicates the start of a session for Adobe Experience Cloud
Expiry: Session
Type: HTTP
Provides page name value (URL) for use by Adobe Analytics
Expiry: Session
Type: HTTP
Used to retain and fetch time since last visit in Adobe Analytics
Expiry: 6 Months
Type: HTTP
Remembers a user's display preference/theme setting
Expiry: 6 Months
Type: HTTP
Remembers which users have updated their display / theme preferences
Expiry: 6 Months
Type: HTTP
Used by Google Adsense, to store and track conversions.
Expiry: 3 Months
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
These cookies are used for the purpose of targeted advertising.
Expiry: 6 Hours
Type: HTTP
These cookies are used for the purpose of targeted advertising.
Expiry: 1 Month
Type: HTTP
These cookies are used to gather website statistics, and track conversion rates.
Expiry: 1 Month
Type: HTTP
Aggregate analysis of website visitors
Expiry: 6 Months
Type: HTTP
This cookie is set by Facebook to deliver advertisements when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website.
Expiry: 4 Months
Type: HTTP
Contains a unique browser and user ID, used for targeted advertising.
Expiry: 2 Months
Type: HTTP
Used by LinkedIn to track the use of embedded services.
Expiry: 1 Year
Type: HTTP
Used by LinkedIn for tracking the use of embedded services.
Expiry: 1 Day
Type: HTTP
Used by LinkedIn to track the use of embedded services.
Expiry: 6 Months
Type: HTTP
Use these cookies to assign a unique ID when users visit a website.
Expiry: 6 Months
Type: HTTP
These cookies are set by LinkedIn for advertising purposes, including: tracking visitors so that more relevant ads can be presented, allowing users to use the 'Apply with LinkedIn' or the 'Sign-in with LinkedIn' functions, collecting information about how visitors use the site, etc.
Expiry: 6 Months
Type: HTTP
Used to make a probabilistic match of a user's identity outside the Designated Countries
Expiry: 90 Days
Type: HTTP
Used to collect information for analytics purposes.
Expiry: 1 year
Type: HTTP
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation
Expiry: 1 Day
Type: HTTP
Cookie declaration last updated on 24/03/2023 by Analytics Vidhya.
Cookies are small text files that can be used by websites to make a user's experience more efficient. The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies, we need your permission. This site uses different types of cookies. Some cookies are placed by third-party services that appear on our pages. Learn more about who we are, how you can contact us, and how we process personal data in our Privacy Policy.
Edit
Resend OTP
Resend OTP in 45s