2 ms·
> these technical interviews are skills that you don't really gain on the job I believe that's definitely the case. That's why I shifted my interviews to be as
by wpietri 10y ago
> these technical interviews are skills that you don't really gain on the job
I believe that's definitely the case. That's why I shifted my interviews to be as much like the work as possible. First round was a pair programming interview plus a bit of technical discussion. Second round was kicking around a feature and its implementation with the team.
My goal was also to see people at their best, so I did as much as possible to make them comfortable. E.g., for the programming portion they were welcome to use their own device, their favorite editor, and their strongest language.
I was very happy with the results, and aim to keep moving in that "make it real" direction. I wrote more about my approach here: http://williampietri.com/writing/2015/slightly-less-awful-hiring/ http://williampietri.com/writing/2015/slightly-less-awful-hi...
- Scea91 10y ago> Second round was kicking around a feature and its implementation with the team. I suppose it was a toy feature. Isn't it detrimental to the teams performance if all of them have to be present at the interview?
- Declanomous 10y agoWouldn't it be more detrimental to a team's performance to hire someone who isn't a cultural/productive fit? I think that would make the temporary performance hit when hiring worthwhile.
- wpietri 10y agoExactly. A good hire will add thousands of hours of productivity. A bad hire can be negatively productive, either personally, by harming team performance, or by driving off productive people. Trying to minimize team-minutes spent per candidate on late-stage interviews is a false economy. In practice, I don't try to get absolutely every team member involved, just a quorum. If everybody wants to have a say, that's fine by me, but often once you get past 3 participants somebody will say, "Oh, whatever you folks think is fine by me."