3 ms·
You have a long uphill battle, although in most cases, having a PhD and papers you can point out can be useful. For example if I see your application, I'm gonn
by dekhn 13y ago
You have a long uphill battle, although in most cases, having a PhD and papers you can point out can be useful. For example if I see your application, I'm gonna ignore most of your resume and what you said you did in grad school, find your first first author paper (and all subsequent ones), pull them up and skim them, and decide if you have a clue.
cultivate friends who work in the software industry. listen to how they differ from academia. Many people in academia are the world expert in some specific problem, but have trouble transferring that knowledge outside the sphere. Especially bad is people who are stuck in a long-term "this is how it's done" attitude. I find a lot of people in life sciences to be terrible at big data because they embedded poor learning/knowledge and can't unlearn it.
understand what industry does, why, and how. Industry exists to make money. Period. You need to learn how to work in that kind of environment.
spend a lot of time learning to distinguish between "feeder" job positions and "bespoke" job positions, and identifying the latter. Ex-scientists do best with bespoke job positions that match their interests, rather than feeder jobs that dump you in whatever "fungible" SWE position the company thinks you belong in.
you should learn politics and how hiring works. There is no easy way to do this, but your prof probably hires people and has some opinions. I had one prof who had everybody in the group evaluate every resume in detail then rank people by score. if the score was above a threshold, they were invited in for interviews, and scored again (several times). This has been my experience in industry as well. If you understand the metric, and can tailor your application for it, you're in good shape.