News for hackers. Stuff that matters.
Re:What every PhD should know before interviewing with a tec... by t0mbstone on Friday July 21, 2017 @01:59AM (#14818378)
Maybe the problem is that you are trying to hire a PhD (whose entire value proposition is the notion of a complex, well-thought-out thesis) and you are trying to shoehorn them into the agile workflow, where people produce potentially crappy solutions (albeit something) and quickly iterate.

The whole point of a PhD is to NOT approach problems like that. Someone with a PhD has literally been trained to approach problems in a methodical, thoughtful manner, writing a thesis on the singular topic over a long period of time.

Is the problem here a fundamental problem with the PhD manner of approaching problems, or is it a problem with your startup mentality and hiring processes?

Re:What every PhD should know before interviewing with a tec... by icebraining on Friday July 21, 2017 @02:37AM (#14818510)
You make PhD sound like robots, only able to follow what they've been programmed to do. Persons don't have "entire value propositions", and they may welcome a different environment than what they've been doing in academia.
Re:What every PhD should know before interviewing with a tec... by seanmcdirmid on Friday July 21, 2017 @02:39AM (#14818522)
Ah, well, some PhDs do work with an agile mindset (fail fast with research ideas, most of them suck anyways). PhDs seem to be all over the map in how they approach problems.