How important is it to have mastery of something like pycharm or anaconda or github?
Should I be going through tutorials/training?
Would I embarrass myself if I didn't know all the ins and outs of these tools in an interview?
And thank you for creating this substack. I am trying to pivot from a career as a pharma scientist to something data related and I find it very interesting.
pycharm - essential. If you use python, you will use pycharm. Anaconda is basically Python with the libraries already installed in it, in other words it's the same thing as Python. Github - my Quant company doesn't use Github, but a few I know do use it. Just make a free account on GitHub, and click around, and upload some of your code there, incase your employers want to verify if you can legitimately code, before calling you in for an interview.
You should be going through the substack from Part 1 all the way to up to date, and should focus specially on the resume, and some of the technical tests. This will give you an idea on what type of content hiring managers are looking for, and what type of questions they will ask you to confirm if you are the real deal or not. An example: if you are the right guy, even though their hiring process is supposed to finish 3/4 weeks from now, if you are THE GUY, they will toss you the offer in a day.
No, you would not embarrass yourself, the idea is to prospect heavily, until you run into a company that is looking for the guy you specialize in. Take a look at my how you can get an edge when applying post.
You are welcome. Good luck, lemme know if there's any more Qs that pop up.
Working through this, I got a couple questions:
How important is it to have mastery of something like pycharm or anaconda or github?
Should I be going through tutorials/training?
Would I embarrass myself if I didn't know all the ins and outs of these tools in an interview?
And thank you for creating this substack. I am trying to pivot from a career as a pharma scientist to something data related and I find it very interesting.
pycharm - essential. If you use python, you will use pycharm. Anaconda is basically Python with the libraries already installed in it, in other words it's the same thing as Python. Github - my Quant company doesn't use Github, but a few I know do use it. Just make a free account on GitHub, and click around, and upload some of your code there, incase your employers want to verify if you can legitimately code, before calling you in for an interview.
You should be going through the substack from Part 1 all the way to up to date, and should focus specially on the resume, and some of the technical tests. This will give you an idea on what type of content hiring managers are looking for, and what type of questions they will ask you to confirm if you are the real deal or not. An example: if you are the right guy, even though their hiring process is supposed to finish 3/4 weeks from now, if you are THE GUY, they will toss you the offer in a day.
No, you would not embarrass yourself, the idea is to prospect heavily, until you run into a company that is looking for the guy you specialize in. Take a look at my how you can get an edge when applying post.
You are welcome. Good luck, lemme know if there's any more Qs that pop up.
Wonderful, thank you!