|
|
|
|
|
by ericb
5395 days ago
|
|
In the actual interview, I find that most give up after spitting out some pseudocode. About 40% have reasonable psuedo code that makes me think they'd get there (but these half-answers don't give me enough confidence to give them a thumbs up). Actual code that works (and running it from a terminal), we are seeing only about 15% tops maybe lower. We have started sending a fizzbuzz-ish question, a relatively easy css question, and a word-problem about performance as pre-interview questions through recruiters. This has dropped our resume inflow dramatically and saved a lot of time, but that's depressing in a way. We are looking for a Rails or PHP dev in waltham (near boston) currently without a lot of luck. The job has a lot of pros, but probably doesn't do itself justice on-paper. |
|
Keep in mind that you may be getting a lot of good people with a lot of pros, but that don't do themselves justice on paper.