Well, it is actually a slightly deep question for a new graduate to ask the difference between C & C++.I am not aware of any university that does C++ to any useful extent, and would only look for programming skills in a CompSci graduate, and even then would focus on conceptual stuff not detailed language definitions. We're doing a project with Imperial in London, and I was depressed to hear undergrads use Pascal, and even places where fuckwits haven't taken over the computer lab have less than 10% of the course being programming. ppauper's point about comprehending code is valid, as long it is seen as necessary but not sufficient. Programming is an imperative craft.A programmer does things to a computer, using cunning, guile, trickery, bloody mindedness and a code editor, so a good test would include writing code and debugging as well.What one is trying to determine is the candidate's "internal model" of what he thinks C++ is. I don't care if he knows about templated exceptions as much as I care that when he needs to do it, he can grab Stroustrup and understand it without help from a grown up. There is a critical mass of comprehension that is required to be useful, and I'd be impressed by any undergrad who had it.As it happens, I almost never use SanFranCA2002's cout. Most of my development has been GUI & DLL, so I know some mildly arcane stuff about sockets and streams, but if an interviewer probed hard there my holes would quickly expose me as a fool.