| I have a PhD (in mech engineering) and work in industry. My experience was that I basically had to pick up a new physics set and tool set every year as I jumped from algorithm development, to constitutive model development, machine learning, and quantum computing. In all cases they were tackling problems in different areas: new toolset to learn, new math to learn and new physics to learn. I thoroughly enjoy working on research problems, however I felt that there was a lot working on made up problems and forcing a square pegs into round holes so we could declare success to the funding agency when really it was a probably worse way to tackle the problem than industry standard. Pros:
I was forced to ride a learning curve with a new skill set and new area of expertise every year. I have learning to pick up skills very quickly. I took a lot of cross discipline classes in physics, mechanical engineering, mathematics, scientific computing, chemical engineering, and materials engineering. I have a large amount of cross discipline knowledge. I found the work fun and I basically had no boss which was nice. The downside:
I worked 60 hours a week for $20,000/year for 5 years. Lost wages ~ $500,000 The tools and skills I developed for my PhD only peripherally translate to the work I do in industry. Advice:
Get a job, the PhD will be waiting for you in 2 years if you decide you want it then. Plus it sounds like you are thinking about getting a PhD because looking for a job is hard. |
I mostly thought that I had to do a PhD to keep learning. But I was wrong - I learn every day as a developer. I also realized that I liked broad problems rather than narrow. E.g. make a system good enough in all dimensions vs working on "perfect" overload protection.
I wrote more about it here: https://henrikwarne.com/2016/03/07/ph-d-or-professional-prog...