   How well should you know a language to put it on your resume?
  I'm pretty fluent with java, and so it's easy for me to pick up C++, PHP and a few other languages. I haven't actively coded in the other ones, but I have read the tutorials, so it wouldn't be too hard (I would probably need to reference some stuff just in case). How well would I need to know them in order to put them on my resume?   
Quote:Original post by Vasant56I'm pretty fluent with java, and so it's easy for me to pick up C++, PHP and a few other languages. I haven't actively coded in the other ones, but I have read the tutorials, so it wouldn't be too hard (I would probably need to reference some stuff just in case). How well would I need to know them in order to put them on my resume?You would need to have at least coded with them. Been able to read and generally understand a language is one thing, but writing with it is another thing.   ;  I'd say well enough that you could produce an implementation of a well-known algorithm or structure on demand during a technical interview.  If you get to an interview and they ask you to produce a templated BST just to show you really know C++, your Java experience isn't going to get you too far.   ;  Well i would put down every language i have programmed in, for how long. And then rate myself out of 10. Also giving examples of what i have written in each.   ;  As Dave said, I'd just put every language I know, and then rate my skills with it.If you've read tutorials, so you can at least read the language, you could probably put them as 1/10, or "beginner" or however you want to rate it. Just don't pretend to be expert in a language you've never actively used.   ;  I put down every language I actually coded in, because reading a language and writing can vary quite a bit. I put down C# in my resume because I did make something in it and when asked about my knowledge, I just mentioned how much I knew in it. I probably wouldn't rate my skill in a language on a scale though because if you think you know a language you'd rate yourself high, but chances are you probably don't know to that degree (unless you are very humble). If I were asked how well I know a language, I'd mention what projects I've done with it and maybe what algorithms I had to implement. That is more concrete than a number.   ;  How well should you know a language to put it on your resume? I think a better question to ask is, how fast can you learn a language after putting it on your resume?   ;  On my resume I have three columns for skills. One is expert, the other is intermediate, and the last is novice.  Then I include the years of experience I have on there.  Most of the stuff that I have under Novice are things I haven't used much beyond "Hello World" and a few simple applications.  Under Intermediate I have things which I am confident that I can make algorithms for and even tweak.  Under Expert I have things which I have a deep understanding of and would know how to optimize in complex applications.  Of course all of this is relative to the position for which you are applying.   ;Quote:Original post by mtwHow well should you know a language to put it on your resume? I think a better question to ask is, how fast can you learn a language after putting it on your resume?Winner.  I've actually put "Languages proefficient with: Any, given a 2 weeks notice." once on my resume for internships I did not particularly want, just for the kick of seeing if I would be called in for an interview.  I was, altough I sincerely doubt they read it. [headshake]   ;  1. A blog by some of the HR people at Microsoft. As you can imagine they see a lot of technical resumes/CVs, probably more than most - some good stuff there to see how they think and what they're looking for:http://blogs.msdn.com/jobsblog/2. Something relevent: http://blogs.msdn.com/jobsblog/archive/2005/09/26/474111.aspx3. IMO it's ok to put languages you have actually used to some extent as well as your proficiency level which should indicate how much you've used them. Case in point: I covered Ada and Algol briefly in a "history of computer languages" module when I was at college, but I definately don't know enough of either to code something right now - so I don't put them on my CV/resume because I'd still need to learn a lot to do anything useful with either - particularly "useful" in a job sense. Even closer to your situation: I'm fluent in C++ (though not expert [I'd say there are less than 10 people on this board who are actually expert in C++ - and a few 1000 who think they are]) - but I've *never* put Java on my CV/resume regardless of how close it is to C++, and even a bit of &#106avascript I've done. When I've done something reasonably substantial in Java, then I'll put it on there.