I have a PhD in Electrical Engineering and I spent 2 more years as a postdoc working on optical imaging and microscopy. I was fairly successful but I was never really engaged which I attributed to being in academy. So I switched to industry and realize that the jobs in this field are not what I want to do. Now looking back to find out what I like doing, I realize that the times I was having fun was when I was writing code, doing computation and solving problems related to that.<p>Most of my coding is in Matlab which is not used in software industry. I have been doing some side projects on Python and I got fairly good at it. I can also find my way around in Javascript, SQL, noSQL (redis). I used Java as an undergrad.<p>How can I accelerate the process of getting a job as a software guy aside from doing side projects and showcasing it? I would like to get a job ASAP as I can learn much faster if I do it full time.<p>PS. I am in SF Bay Area FWIW
Matlab could be really good to get into research or 'data science' roles, I don't think it's a particularly common skill, but can be very good for more mathematical research oriented coding. Given your background you might want to focus much more on the mathematical side of development, perhaps look at machine learning roles as I'm sure you'll find machine learning easier to pick up than many people.
You can probably find something if you are flexible on salary. It's unlikely a solid shop will hire you for anything above junior level. I have a MS in Engineering and can relate. As a suggestion, don't jump into SE just yet. Use your still-fresh STEM skills to make a lateral jump within Academia. In the 10 years since school, I have lost many of my skills in Math and Statistics. I traded them in for applied engineering skills. In retrospect, my Math and Stats background, when combined with programming (different from Software Engineering) would have been much more interesting work. The field of big-data and analytics is growing and your PhD equips you well for it. Consider looking for a short-term opportunity (1-2years), where you can keep your math sharp. It should be something where you are proximal to good developers and expected to be learning SE practices while working as a subject matter expert (SME) to developers. In a position like this, depending on location, you might even enjoy a higher standard of living, than you would as a junior engineer. Do that for a few years, and when you're ready, you can jump from there.