I usually feel that technical interviewing is, for the most part, random (old post). It is cool that some teams are not only aware of this but do interviewing differently to take care of this.
See how the mono team hires :
http://tirania.org/blog (search for sample interviews)
A resume, plus an interview when you ask the candidate to "implement XX on the whiteboard" and some trick questions have too many problems which are probably worth discussing some other day. In my experience these kinds of interviews that have been popularized in the industry are bad. They evaluate developers on all the wrong dimensions that you need to produce software.
Coming up with what makes sense for each specific group/team takes effort, but who said keeping things real is easy :)
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment