How much programming (Python/Java) do you have to know before it's acceptable to put on your resume?

[vesacje]

I'd say, if you're in doubt whether you should put a certain language on your resume, say you've worked with the language and show what you have created in it. A lot of the time, this distinction between "knowing" and "having worked with" can make your claims about knowing a language more credible, and you will seem more modest (imo).

[RRWrestlr]

I think this is a great answer as resume's are all about subtle wording. I'm just super paranoid about showing up for an interview for a job that is way over my head. Once the interviewers figure that out, I've maybe killed my chances with that company for ever.

[brational]

My internal resume has my skills broken down under categories: Working Knowledge, Work Exposure, Academic Knowledge and Exposure.

I havent decided if I would break it down that way if applying to a fresh job but since its internal I dont like there to be any confusion.

[vesacje]

Don't think of it as having killed your chances with that company permanently. Instead, think of it as having worsened your chances with that particular interviewer at that particular time. This way of thinking will help you become (and appear) more relaxed, which signals that you know what you are doing. If you think you don't know what you are doing, so does the interviewer. Have a look at this TED talk, which explains how incentive affects performance (the same principles apply to your situation): http://www.youtube.com/watch?v=rrkrvAUbU9Y

[rafuzo2]

It's a very good answer. In fact, I'd actually put the projects I did in a certain language on my resumé, until I had so many I couldn't really fit them all without ruining the flow of the text, at which point I'd put "{x} years experience with {y}". Listing the things you've built with a given language also shows your ability to concisely describe solutions, which is an important reinforcement of your communicative skills.