Timeline for Would you show your production code to candidates at the interview?
Current License: CC BY-SA 2.5
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 26, 2010 at 15:38 | comment | added | Tom Anderson | @Wyatt: i wonder if it might be usable even in non-pairing companies. Sit the guy down to solve a problem, acting as his guide, explaining the background, giving him support. Even just having a conversation about how to solve a concrete problem (i imagine you do do this with colleagues, even if you don't pair) could be useful. | |
| Oct 26, 2010 at 15:36 | comment | added | Tom Anderson | @Sri: we only interview one person at a time. I should add that this is not the first-line interview; we start by reading CVs we are sent, then we have a phone interview with potential candidates, then we ask anyone who passes that to come in for a pairing interview. I should also add that we have a fairly focused hiring process; we tend to hire people recommended to us by employees, or people outside the company we trust, or recruitment agents we work with. We're never in the situation of having a hundred applicants to sift through. | |
| Oct 26, 2010 at 14:08 | comment | added | Gopi | But how long will be the interview process? Huge number of people might attend the interview! | |
| Oct 26, 2010 at 12:52 | comment | added | Wyatt Barnett | This would be so awesome to do, if only we did pair programming . . . | |
| Oct 26, 2010 at 12:42 | comment | added | Marek | I like this. What company are you working for? :) | |
| Oct 26, 2010 at 12:19 | history | answered | Tom Anderson | CC BY-SA 2.5 |