A knowledge of programming in general, an understanding of algorithms, of complexity and basic security issues, will put you ahead of a lot of "consultant programmers" I have met.

Recruiters generally think C and C++ are the same thing, and so do HR departments.

If you enjoy what you do, and are good at it, you'll get better and be an asset to any slave-farm^H^H^H^H^Hcorporation.

Contribute to an open source project or two, perhaps.

Having said that, what university is teaching computer science students only three languages, and all procedural? You should know at least one fuctional, non-procedural language, e.g. pure scheme, ocaml, xslt or xquery, prolog, would all be candidates, even if your university forgot to teach lambda calculus :D

The value of a declarative language isn't that you will get a job programming in LISP (although you might) but rathar that it gives you a different toolset, a different way to think about problems that turns out to be useful in a lot of other places.

Many people include the years they were at University as part of their experience in various programming languages.

For example, if in your first year you learned OCAML, and that's 5 years ago, you have been programming in OCAML since 2003.

This means that any good interviewer will need to narrow down exactly what your relevant skills are, of course, so don't exaggerate and never ever tell an outright lie on your CV. In some (usually large) companies (and in some countries more than others) that can be grounds for dismissal without notice even 15 years later. But do remember you can include open source work and your university courses - they are every bit as relevant as the experience of someone who did not go to college but spent a couple of weeks reading "Lean Perl in 21 days" and then decided to re-write the aircraft navigation system ;-)