logoalt Hacker News

ludicrousdisplalast Sunday at 10:43 AM1 replyview on HN

If I was asked to review code in an interview, I'd prefer it be printed out on a sheet of A2 or A3 paper that I could look over and write on.

Regardless, there should be a hard rule that if you show code (either working code or example code) to a candidate then it needs to stay visible for at least five minutes. No skipping ahead to the next slide or switching windows after 2 seconds.


Replies

makeitdoublelast Sunday at 11:13 AM

For live debugging/fixing we were sharing a dedicated GitHub repo, and the candidate would share his screen while doing it. It was kinda of a mess, so I switched to a more static approach of sharing a MR and have the candidate explain what it does, and potentially comment on it.

TBH I wouldn't do that face to face, it's so unnatural I'd prefer white boarding or straight handing them a computer.

That's also where using an online coding platform where the candidate can run the code works a lot better, less preparation on either side, less surprises.

show 1 reply