Re:How to freaking hire great developers by having them read...
by fjdbeb76 on Friday July 29, 2022 @02:19PM
(#32280171)
I did this when I looked after interviews.
I'd print off a piece of legacy code that was particularly ugly and ask them to review it.
I'd tell them I wasn't looking for silly stuff like parser errors and instead was just looking for their opinion on the code. How they thought it worked and how they would improve or do it differently.
It was mostly just an interview prompt with a consistent starting point that lead to interesting insights about the interviewee but generally had repeated talking points across candidates.
I'd print off a piece of legacy code that was particularly ugly and ask them to review it.
I'd tell them I wasn't looking for silly stuff like parser errors and instead was just looking for their opinion on the code. How they thought it worked and how they would improve or do it differently.
It was mostly just an interview prompt with a consistent starting point that lead to interesting insights about the interviewee but generally had repeated talking points across candidates.