4 ms·
To your latter point, any time we do technical exercises, we _always_ let the interviewee use their own IDE. Nowadays it's easy because most people have laptops
by erichurkman 10y ago
To your latter point, any time we do technical exercises, we _always_ let the interviewee use their own IDE. Nowadays it's easy because most people have laptops, though we do offer to set one up if they do not have a laptop to bring.
Their choice of toolsets and setup can also be a really interesting discussion topic. More than once during an interview, someone has shown me something really cool that I adopted (new key binding, a new tool, a particular way someone had their terminals split-paned, etc).
- dmoy 10y agoWhat if the candidate doesn't have a machine of their own (company owned)?
- erichurkman 10y agoWe have a laptop they can use and make the offer that they can use it. It hasn't happened often, but I could easily see it being set up with a few different environments already. (Adding that to my todo list.)
- huac 10y agoI've done a couple interviews over screenshare, where I setup my own IDE, and liked that more than the typical Google doc or CoderPad