3 ms·
You mentioned "poor coding skill under pressure". Did you assess that during interviews? Because in my experience, the pressure during an interview is not at al
by henrik_w 13y ago
You mentioned "poor coding skill under pressure". Did you assess that during interviews? Because in my experience, the pressure during an interview is not at all like the pressure while developing software. At an interview, you may have to come up with a solution in, say, half an hour. At work, you can usually sleep on a problem, and come back with a solution the next day, even if you are under pressure to ship a new feature. In other words, nothing like the pressure during an interview.
- eru 13y agoOn the other hand, interview problems are often way easier.
- quanticle 13y agoNot necessarily easier, but definitely less ambiguous. To be honest, in terms of absolute difficulty, I'd say that interview problems have I had to implement quicksort. Only in interview problems have I had to create a new data structure to fit a problem. On the other hand, I've always been able to suss out the requirements for the solution in one or two questions in interviews. In real life, figuring out what the solution should even look like is often a process that takes at least a week.
- walshemj 13y agoPressure is not doing fizbuzz at an interview its when the billing system you are in charge of has its first 5 mill month and the CTO nudges you and says "this had better be right other wise we are both out of a job"
- ijk 13y agoSince, by definition, a PhD has faced down a committee that has the power to say "this had better be right otherwise you've wasted the past five years of your life", and has likely been on grant projects where their funding is similarly on the line, that suggests you should probably try to hire more PhDs, not fewer.