Hacker News Reader

I mean; ask the programmer who is currently working on that computer, what he/she is working on. Then see if the candidate can pick up the work from there, with some hints from the programmer.

View on HN

The engineers working on a team might spend hours in sprint planning meetings, doing research, and working out an approach with their team before they start coding anything. How would you expect to get a fair assessment of someone by dropping them in the middle of someone else's code work, and putting them on the spot?

I understand.

Have you done this during interviews with applicants? Have you received feedback from applicants?

Reply on news.ycombinator.com