Over the last 2 years, this is the most common query I receive from our readers:
Which data science / analytics training should I go for?
The query comes in varied shapes and size, but the inherent question is still the same.
I can empathize with people facing these questions – the number of tools, analytical techniques under application and trainings provider, all have increased many-fold in last few years. If the trends and projections are to be believed, this is probably just the start of a growth phase.
Let’s take an example, as a person switching from software industry, do you learn SAS or do you learn R? Or should you learn Big Data tools and techniques? How about machine learning? Data Visualization tools? Even if you zero in on one of these, the next question which arises is where and how to undergo these trainings?
I am sure most of the person in this situation feel like the person in the image above. This is where a framework can help you.
I aim to provide a framework to you to decide:
You can apply it at various stages of your analytics career to find out what should you be learning next.
The answer to first 2 questions in this framework are in form of levels or steps. You start from level 0 and move one step at a time. So if you are a complete fresher start from Level 0 of tools and level 0 of techniques. But, if you are a fresher with statistics background, start with Level 1 of tools (assuming you know Excel) and Level 1 of techniques (move to level 2 if you know predictive modeling)
Once you have finalized the tools and techniques to learn, move on to step 3 and step 4 of the process.
Level 0: Excel.
If you don’t know excel, you should learn it first. You should be able to play with Pivot tables, do simple data manipulations and apply lookups in Excel.
Level 1: SAS / R / Python
This is going to be your work horse. You can choose any of these languages. For a more detailed comparison, have a look at this article.
Level 2: QlikView / Tableau / D3.js
You should add up your repository with one of the visualization tools.
Level 3: Big Data tools
This in itself can be multiple levels – start with Hadoop stack – HDFS, HBase, Pig, Hive, Spark
Level 4: NoSQL Databases
Again, you can read an overview of NoSQL databases here and start by learning the most popular one – MongoDB.
Exception 1: If you come from MIS / reporting background, you can start from learning visualization tools like QlikView and Tableau (Level 2) and then go to Level 1
Exception 2: If you come from software engineering / web development and know one of the 2 languages – Java or Python, you can start from Big Data tools as well (level 3)
Now that you know, which tool would you want to learn, let us look at the techniques to learn. Again the structure is similar
Level 0: Basics of statistics – Descriptive and Inferential statistics
Level 1: Basic predictive modeling – ANOVA, Regression, Decision trees, Time Series
Level 2: All other remaining machine learning techniques except Neural nets
Level 3: Neural nets and deep learning
How should you learn is dependent on 2 factors:
This image explains the selection:
On one extreme, you have option to join open courses – where you spend low (almost zero) resources, but need high self learning motivation. On the other hand, you have courses run by big universities like Stanford / MIT / North Western, where you will need to spend money and will get help and mentor-ship from experts over longer duration. You can choose the style of your learning depending on where you fit in.
Please note that irrespective of which method and blend you choose, you will need to aid these trainings by hands on projects and practice. No resources or trainings can cover that for you. Here are a few examples of these projects.
For people relying completely on self learning, our learning paths can be of great help. There is one for Python, SAS, Weka and Qlikview each and several more under development.
Now that you know, what to learn and how to learn, you can shortlist various options available. You should talk to people who have undergone that training / course and gather some reviews. You can also use our training listing page and apply filters to shortlist the trainings available for various tools and techniques. We have more than 300 trainings listed here and are in process of adding more trainings and courses.
So, there you go! You should have a way to find out your way through this data science course juggle. Hope you find this framework immensely useful. I have tried to put a framework to the most common query I get from our audience. The idea is to enable you to make the right decision to the extent possible. If you think, you are in a situation which doesn’t get addressed by the framework above, please feel free to ask those questions through comments / discussion portal.
P.S. These are my views. A lot of these recommendations are based on my experience and what I think is the right choice. As you can expect, some of these questions don’t have a right or wrong answer. They are subjective in nature. So, if you have a different opinion about something I have mentioned, please feel free to let me know.
Kunal Jain is the Founder and CEO of Analytics Vidhya, one of the world's leading communities of Al professionals. With over 17 years of experience in the field, Kunal has been instrumental in shaping the global Al landscape. His expertise spans diverse markets, from developed economies like the UK to emerging ones like India, where he has successfully led and delivered complex data-driven solutions. As a recognized thought leader, Kunal has empowered countless individuals to realize their Al ambitions through his visionary approach to Al education and community building. Before founding Analytics Vidhya, Kunal earned both his undergraduate and postgraduate degrees from IIT Bombay and held key roles at Capital One and Aviva Life Insurance across multiple geographies. His passion lies at the intersection of analytics, Al, and fostering a thriving community of data science professionals.
Why most data science trainings fail to deliver...
Learning path & resources to start your da...
Should I become a data scientist (or a business...
How To Have a Career in Data Science (Business ...
8 rules for new age analytics learning!
7 tips to overcome your analytics learning hurd...
Learning Path for Developers & IT Professi...
13 Tips to make you awesome in Data Science / A...
The most comprehensive Data Science learning pl...
How to start a career in Business Analytics?
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
Nicely written article.
Dear Kunal, Thanks a lot for sharing very interesting insights about choosing the right program for analytics and big data. :) Regards, Darshana
Hi Kunal, Very nice and clear article! What I actually missed were basic Unix Shell programming skills. It can be extremely useful to know how to use commands like grep, awk and sed etc to perform essential data cleaning and pre-processing of the data before bringing these data as for ex. a .csv file into Excel or R. Could you expand a bit on what you feel are the advantages of QlikView / Tableau / D3.js beyond for example making the graphics in R? All the best! Ruthger
There are 2 advantages where I think a data visualization tool can come very handy: 1. Understanding and exploration of Huge Data - For example, while working on Avazu CTR Kaggle problem, we were working on 7GB data with anonymized columns. It was becoming time consuming to load this data in R and perform exploratory analysis. With QlikView, we could load the entire data in less than 5 minutes and then perform exploratory analysis very quickly. What helps is quick slice and dice and drill throughs available. So you can quickly identify high and low value population and segregate them in your modeling in R 2. The second application is in finally delivering your insights to the customers. Once your analysis is complete, you can use story-telling feature of these visualization tools to present your findings. You can bookmark the graphs and access them quickly on the go. If people want to explore additional information - it is typically far more easier to do so rather than opening RStudio and then writing / running the codes. Hope this helps you answer the question. Regards, Kunal