Our interviews are two part. 1) 40 minute test-driven paired programming exercise. In this round the assessor does all the typing asking the candidate questions along the way. It can be in-person or via Webex.
2) on-site paired programming exercise doing a “real” user story. During this exercise we use the same tools and follow the same xp practices we use on the job.
I build developer tools and services at Microsoft (currently Codespaces, Live Share, IntelliCode) and maintain some OSS projects (CodeTour, GistPad, CodeSwing, WikiLens)
So the candidate would end up getting a feel for both the projects they’d be working on, as well as the actual team practices/tools? I love that! Also, since you have a mix of coding from both the interviewer and candidate, you’d need a tool that supported bi-directional control?
Out of curiosity: does you team practice TDD and/or pair programming full-time?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Our interviews are two part. 1) 40 minute test-driven paired programming exercise. In this round the assessor does all the typing asking the candidate questions along the way. It can be in-person or via Webex.
2) on-site paired programming exercise doing a “real” user story. During this exercise we use the same tools and follow the same xp practices we use on the job.
Zero whiteboard if exercises
Zero trick questions
So the candidate would end up getting a feel for both the projects they’d be working on, as well as the actual team practices/tools? I love that! Also, since you have a mix of coding from both the interviewer and candidate, you’d need a tool that supported bi-directional control?
Out of curiosity: does you team practice TDD and/or pair programming full-time?