4 ms·
It's unclear if you'd taken on programming projects; if so, it sounds like you would've been able to discuss them in detail. Even with a class project, if some
by majormajor 12y ago
It's unclear if you'd taken on programming projects; if so, it sounds like you would've been able to discuss them in detail.
Even with a class project, if someone was interested enough in the class that they can tell you months later "oh, yeah, this project was interesting, we did it with method x because we'd already studied methods y and z and they weren't as well suited for reasons a, b, and c"—even if those reasons were straight from the lectures—then they're already well ahead of most university candidates I've talked to. Most people mostly forget stuff beyond "oh, yeah, we did it this way cause the textbook said to." Similarly for "what else might you do with that?" type questions.
Now, if you haven't taken any classes, and haven't done any software projects for other stuff, yeah, you wouldn't have anything to talk about. But figuring out if someone who's never touched code before is going to be able to do it well is an extremely hard problem -- that person isn't going to make it past any other interview method I've encountered, either.
How would you approach that candidate?
- atom-morgan 12y ago> How would you approach that candidate? One approach for me would be to find past success in other areas. Prior interests where they started from nothing, went through the grind of learning, and excelled. Sports, music, art, whatever. What did they gain from that and what is their learning process going forward? I think that's an important characteristic to have. To have pushed through the process of sucking to being great before and the willingness to do it all over again. It's very easy to avoid this in life.