[quote]carbiduis wrote:
[quote]LoRez wrote:
[quote]carbiduis wrote:
It doesn’t take long for the smugness to be wiped away from a new grad, the professional world is a humbling place
So you turned down candidates with doctorate degrees cause “they know everything”? And you know they were all like this? Stereotype much?
The truth is they were over qualified for the position and you didn’t need a doctorate for the position
There are plenty* of job opportunities for people with graduate degrees and GASP ZERO EXPERIENCE, usually highly technical and large companies.
[/quote]
It’s funny the things people pick up on.
No, we turned down candidates with doctorate degrees because they couldn’t do basic problem solving.[/quote]
maybe you should have looked at someone with a math/science/engineering type degree instead of candidates with doctorates in art history
I defend the highly educated cause people are constantly bashing them, even though there is a reason they were able to make it through the schooling (I’m assuming a math/science/engineering type degree)
it is nuts how many people can get through tough schooling by simply regurgitating information and not processing it. I couldn’t do that and was forced to actually understand the problem solving/application side of things, it made school a lot harder.
[/quote]
I don’t know where you get these assumptions from.
We’ve rejected candidates with Computer Science degrees from MIT, Caltech and UIUC because of inability to solve the programming and design problems we presented them.
For what it’s worth, they at least got to the interview stage and weren’t rejected based on resumes and phone screens alone.
EDIT: While they were certainly able to do fine if you stick to, say, exam material… algorithm design, analysis, statistical modeling… they were very weak with the applied side of things.
It’s one thing to be able to design a scalable system that works in theory and would get the nod of approval in the academic world; it’s quite another to be able to evolve an existing system to become more scalable (which is a hard problem), or to develop a new working scalable system given the actual constraints and failures that happen in operating systems on real hardware (not quite as hard a problem). Basically, there are a lot of implementation details that get glossed over.
Secondly, and somewhat less important, they tended to be very bad with actual coding and debugging. This is a skill that can be learned of course, but there was a surprising lack of attention to detail. (Interestingly, those with just undergrad CS degrees are much stronger at this.)
To be fair, we reject a lot of candidates regardless of background.
It’s more that we’ve seen little positive correlation between academic qualifications and actual job capability – at least if there’s no relevant work experience.