To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Answers ( 2 )
The biggest piece of advice I could give is to take a course in microeconometrics/labour econometrics as a part of your course. If your course coordinator won’t let you, beg. If they still won’t let you, then go off-line for a week or two and properly digest Mostly Harmless Econometrics (or if your stats isn’t too good yet, Mastering Metrics). If you want to go and work in health analytics, then replace what I just wrote with the equivalent for research design.
Why learn microemet? Basically, many of the big questions in business are of the form “what will happen if we do x”. Predictive models that aren’t informed by causal reasoning do *terribly* at this question–they answer the question “what do we see happening to y when we see x”. Inferring what will happen to y when you fiddle with x is a difficult task when all your data come from a world in which you did not fiddle with x. Too often we come across people with great technical chops who aren’t even aware they’re making mistakes when answering these questions. Don’t be one of these people.
The second biggest piece of advice would be to not become too enamoured by the sexy end of data science (especially predictive algorithms), but *do spend the time learning this stuff in depth*. Often the simple stuff done well is far more useful to real-world decisionmaking.
Third: read very widely.
In my opinion, you should be thinking about looking for work. Try to network and see if there are employers were looking for analytics. This is different from analysts. They could be market research companies, companies are looking for pricing decisions, and even productivity.
Look to companies where the culture and business processes are not instinctual. Rather look for companies that require analysis.
Unfortunately, one becomes more Bible as one becomes more familiar with the tools of analysis. This may be SAS, business objects, or any other reporting environment.
In conclusion, a massive degree in analytics should result in a job sooner or later.