<p>Hey I am a stat major that is trying to get a job as a data scientist. However most of the jobs I interviewed for ask a ton of data structures/algorithms. I can code but the theory is a little beyond me. Is it feasible to get a CS job with just the important classes? I heard 61b and 170 were just the important ones. Is that enough? Any cs kids have any advice</p>
<p>A is sorta a survey of random stuff, different languages and paradigms, etc.</p>
<p>B expects you to have some knowledge of code going in. My class didn’t go much beyond the sort of stuff my highschool CS classes had taught. Topics are data structures, object oriented programming, etc. Some algorithm stuff, a bit of analysis. Probably the most relevant if you’re looking for how to write code that works and the basics of the fancy stuff.</p>
<p>C goes more into the hardware side of things, how the cache works, the internals of a processor, what makes code go fast.</p>
<p>I haven’t taken 170 yet, but that’s generally at the top of the list of things a CS major should take. It might be tricky to get into though, if you’re not CS.</p>
<p>[Undergraduate</a> L&S CS Students | EECS at UC Berkeley](<a href=“CS Major Information | EECS at UC Berkeley”>CS Major Information | EECS at UC Berkeley)</p>
<p>After 61A, 61B, 61C, 70, the likely most relevant to industry software jobs upper division courses are 170 and 162. Other likely relevant courses are 186, EE122, 161, 169. 164 is not as relevant directly, but touches on the various major areas of CS (theory, software, hardware).</p>
<p>OK, but i have like 1 semester to cram this stuff for interviews. I’m not trying to find a software eng job exactly per se, but more of data scientist one where I analyze data for like facebook/google but still code stuff. My CS background is really informal… just coding here and there on my free time.</p>
<p>Just trying to pass those interviews… then i’ll learn the rest of the stuff on the job hopefully.</p>
<p>You can try to self-study from the course home pages here:
[EECS</a> Course WEB Sites](<a href=“http://www-inst.eecs.berkeley.edu/classes-eecs.html]EECS”>CAS - Central Authentication Service)</p>
<p>I’m somewhat in the same boat as you since I switched from EECS to Math, then decided I wanted to do data science. Currently I’m thinking I might try to get an analyst-type job instead of the software route (don’t know if that’s the right way to do it).
Anyway I’d agree 61b and then 170 are the best for interviews. I think A and C won’t help you much.
Good luck on getting a job : )</p>
<p>I did my last summer internship with a data scientist and basically python (with this additional package called ‘pandas’ which makes python act like the statistical language R) was the primary programming langauge we used, but we also used some “Big Data” programming/scripting languages like the Hadoop framework (java) and Pig (it’s its own scripting language), and then we used some javascript data web apis like D3 to display/create visualizations of all of it when presenting it to others outside of the lab.</p>
<p>So I guess 61A since it teaches python, but 61B and 170 are best for interviews like the person above me said.</p>