> Having to look for research position at a company or getting stuck fighting for tenure position
That's something of a false dichotomy. I know lots of PhDs that aren't doing research or faculty jobs.
That's something of a false dichotomy. I know lots of PhDs that aren't doing research or faculty jobs.
In any case, I'd (for selfish reason) encourage you to be open-minded and give applicants with PhD background at least an equal chance. Personally, I never wanted a PhD, but I went for it because I needed to keep my immigrant status legal, and I couldn't pay for a master's degree out of pocket (if I enroll for a PhD program, I get a master's degree for free on the way). The downside of being a PhD student is that it is significantly more difficult for me to find my way back into software positions, which is something I wanted to do eventually; the HR usually throws away my resume with the assumption(s) that I am either only interested in research or am "overqualified" (or that I'd ask for more money), all of which are incorrect for a lot of PhD students, like me, stuck in academia for now. For all HR or recruiters reading this, I'd encourage you all to give PhD students a fair shot for the programming positions at your firms. You might find that these PhD students are more motivated or have more persistence/endurance (as most who survive the PhD experience usually have) or if you're lucky, are better prepared and thoughtful programmers.
The idea that someone has to study 3 months for an interview is ridiculous. I suppose for a PhD student I can understand as they probably need to refresh their memory, but if that's the case then you could argue they shouldn't be passing the interviews without refreshing their memory if we are talking about normal software development roles.