I'm not sure, but if I were the interviewer, there'd be a lot of
questions which would be off topic here. Questions about design
and such, for example. Or the tools he'd used and was familiar
with. There'd also be questions designed to determine how he'd
react in front of something unknown---does he know how to find
information, and can he learn? And I'd also try to determine
whether he'd fit into the team---questions for which there is no
right answer.
On the other hand, a lot of questions here are about real
subtilities of the langauge. Things I wouldn't bother too much
with, because if your code depends on them, then it probably
isn't very understandable anyway. That doesn't mean that such
questions aren't interesting; I would consider the fact that
someone would ask such questions---that he wants to know more
than the minimum required---very positively. But I wouldn't ask
them myself on an interview question unless the role was that of
a C++ guru. And if he's just graduating, he wouldn't even be
considered for such a role. (Perhaps wrongly: I've known at
least two people who would have qualified for such a role even
before graduating.)
--
James Kanze (GABI Software) email:
[email protected]
Conseils en informatique orientée objet/
Beratung in objektorientierter Datenverarbeitung
9 place Sémard, 78210 St.-Cyr-l'École, France, +33 (0)1 30 23 00 34
