3 ms·
I have a coding session when I interview a candidate. A very simple problem they have to work on with a junior dev we have on staff. The goal is not to get th
by dudul 10y ago
I have a coding session when I interview a candidate. A very simple problem they have to work on with a junior dev we have on staff. The goal is not to get the answer, it's to work efficiently with the less experienced dev.
I'm sure you know how to write a for loop or a singleton, but guess what? If you are a senior I care about how you interact with somebody who does not know these things.
A 10+ year of XP developer has to be passed being a code monkey and be focusing on carrying the team, not just fire up an IDE and piss out some code.
- cerrelio 10y agoI would go on an interview like this. You actually see the candidate in their role, and not just their mundane ability to vomit up a BFS implementation or some such. You see their interpersonal skills (must have) and their ability to get others to complete things.
- MrQuincle 10y agoCool, that's a nice strategy. And in that case you don't even need to make the problem simple at all! What I also always try to do is give context: "You're now writing a seemingly ad-hoc double for-loop in which you assign some function to each pixel. What you should look up is a Hilbert space." I don't know how to test for that though. :-D
- mindfulgeek 10y agoYes! This makes sense.