4 ms·
As noted in another reply to this question, get them to bring in a project and explain it. Additionally, they could spend some time with the team they'd be wor
by rasur 14y ago
As noted in another reply to this question, get them to bring in a project and explain it.
Additionally, they could spend some time with the team they'd be working in, pairing (or whatever) with other members and really demonstrating their abilities.
It's not really that difficult to get away from the whole "technical question at the interview" problem, and I'd wager that in the long-term it'd be better for all concerned.
- jlgreco 14y agoEh, maybe. Those are fine interviewing techniques, but I am unconvinced that explaining something technical you've done in the past would really be that different (from a stress-induced difficulty standpoint) than FizzBuzz.
- Nursie 14y agoThat's the whole point of the article/test - there are loads of folks (apparently) who can talk about it but not produce even this simple example when asked to. You probably don't want them.
- jlgreco 14y agoYeah, that was my take-away. Any "talk about what you have done" that gets specific enough should be susceptible to the same stress though; I cannot fathom how that wouldn't be the case.
- rasur 14y agoWhich is why I wrote the second part: Drag them in for x days, get them to work with existing staff on existing problems. If you have engaged staff, they will weed out the (clue|use)ful and reject the time-wasters.