I saw this post from @v_vashishta who described the JB of DS as someone who's resume makes recruiters cry, can cook Michelin 3 start meals with 1 hand, & run an entire #datascience team with the other...
It's funny, because it's true! Job descriptions perpetuate this unicorn.
BUT, here's the cold hard facts:
1. You don't need to be a unicorn. In fact trying to become one will hurt your progress.
3/n
2. You don't need a PhD degree. In fact most of my students don't have computer science backgrounds. YET, they are getting jobs at Apple, Microsoft, Google...
4/n
3. You just need to get your foot in the door. Then everything becomes easier.
Now for those of you that HAVE been trying to become a data scientist, AND have not succeeded after 1-year, then I want to talk with you specifically.
5/n
Taking 1-year or longer is a problem. Here's why.
1. You're losing out financially. Every year it takes you is a 6-figure salary that you've just forfeited.
6/n
2. You're losing out on time. Competition increases & your shot of making it decreases.
7/n
3. AND you're probably going to quit. I mean who wouldn't IF they weren't getting results after over 1-year.
So I'd like to help you.
8/n I'm going to give you 40-minutes of training that consolidates the things I've learned over the course of 5-years learning data science and training elite teams.
I was instantly surprised at how much more intuitive it was for me given my Excel background. Here's what R had:
3/n
👉#R has functions just like #Excel. I could quickly summarize my data using mean(), sd(), sum(), and friends. These functions were very similar to AVERAGE(), STDEV(), and SUM() from Excel.