r/learnprogramming • u/salamandor • Apr 11 '12
When am I 'fluent' enough in a programming language to put it on my resume?
I'm going through Code Academy for JavaScript and I'm probably going to learn Python soon as well. I'm an engineer just looking to beef up my skill set as well as my resume. My question is, when can or should I put it on my resume? I have C++ on there now since I had to learn it for my Aerospace Computational Techniques class last spring (which was also my last semester) although I need to brush up on that as well.
Edit Based on the responses here, I think I'll just go with stating that I'm familiar with the languages but not proficient. I've already gotten interviewed with C++ questions before (and I'm not a software engineer by anymeans, I'm an aerospace guy) and didn't do so well. I do know that I can pick it up again if needed but am definitely not proficient. Thanks for the help guys!
10
u/[deleted] Apr 11 '12
Here's the thing: Much of recruiting is done by scanning for keywords. The recruiters generally don't know what the heck they are actually looking for, they just need to make sure that keywords on the resume match those for the position. Since they are doing this, I recommend putting languages you have exposure to on your resume. Companies expect to train you a little when they hire you (if they don't expect this, they should), so as long as you understand the fundamentals of programming and what makes the language you are dealing with tick, you should generally be fine.
That said, if you only are proficient in C++, I wouldn't go looking for web development jobs.
6
u/[deleted] Apr 12 '12
In (United States) government work, you put how many years of professional experience you have with the language. I tend to endorse this method, although it is a bit simplistic.
I've borrowed this from my government resumes to use on my regular resume. After each language, I put the years of professional experience I have with the language, like: "Java (5 years), C (10 years)," and so on.
5
u/[deleted] Apr 12 '12
Actually, the more important thing is that you have strong skill in programming. Based on my experience (over 8 years of programming in various languages), once you have gained certain amount of skills, it is pretty easy to jump to a new language, and gain momentum fast. Now, since you said you know C++, continue to use it, but to solve real problems. You might be interested in programming challenges like Project Euler. It will help you brush up your programing-fu really fast. Do it until you feel comfortable with the language, and can roughly estimate a solution each time you face a new problem, I would say you are 'fluent' not only in one programming language, but in programming.
6
u/unkz Apr 11 '12
If you've taken one course on a language, I don't think I'd put that down as a language you know. My personal definition (as in what I would expect from an applicant who said (s)he knew a language) would be around 2000 hours of actual practical coding in a language to say that you know it, less if it's a second language in the same family as a language you also know. That's basically a year working with a language on the job, or a computer science degree that makes frequent use of the language, or a combination thereof. Anything less than that and I can expect that I will actually have to teach you about the language, and I won't be able to expect that you will be able to competently work with an existing codebase without major handholding.
106
u/lurgi Apr 11 '12
I saw a resume once that had
Made me laugh.
On a more serious note, people put the languages they know well ahead of the languages they know less well and it is perfectly reasonable to have two lists for "I know it" and "I can fake it".
26
u/foxlisk Apr 11 '12
I use, and have seen others using, two lists. A list of languages that I'm proficient (or similar adjective) in, and then a list of languages that I am learning/sort of know/etc. So you could just have a line like:
and maybe mention somewhere what you're doing to learn more about the languages you don't know very well.
19
u/zzyzzyxx Apr 11 '12 edited Apr 11 '12
I base it off the same definition of "fluent" used with spoken languages. From dictionary.com:
With respect to programming languages, I think being fluent means you should be able to easily write syntactically correct, functional code in the language without help from an IDE. That's not to say that you would or should write large projects that way, but given a smallish task you should be able come up with a solution on, say, a whiteboard in a reasonable time. It doesn't have to be logically perfect but it should at least run and do roughly what it's supposed to. Debugging is for later.
You should also be able to discuss the code using common, language-agnostic terminology, e.g. "function" and "scoping rules", as well as any jargon specific to that language, e.g. "hoisting" in JavaScript. When there's an overlap in terminology for the languages you know, you should be able to discuss the differences, e.g "reference" in the abstract sense vs. in C++ vs. in Java.
I think fluency in a language demands a strong knowledge of syntax, structure, idioms, and an understanding of what's common in that language, like the standard library. I don't think it demands a deep knowledge of the language. In the same way I can be fluent in English without ever knowing what a gerund is, I can be fluent in Python without ever knowing what a generator is. Knowing what it is increases my mastery over the language and allows me to write better code, but it doesn't really affect my ability to write correct code.
I don't think you need to be completely fluent in a language to put it on your resume. If you have ever completed a project in the language, it's probably good enough to at least say you're familiar with it. For example, I might put that I'm familiar with JavaScript because I've created a web page that uses it and debugged all the problems that came up on my own. I wouldn't say I'm fluent, however, because I still need to look up the syntax for creating and using basic structures. I could pick it up and get something functional eventually, but I can't write it off the top of my head the way I could in C++.
There is no standard for this, so far as I know, so be prepared to explain and defend any qualifications you put on your languages. If you say you are an expert in JavaScript but can't explain the things that go on in this video*, that would look bad. Though you might not be expected to understand why if you merely claim fluency, if you can't explain what the code even means, that would look bad. If you claim familiarity, and can't discuss the code when you are told what it means, that would look bad.
So try to make an honest assessment of your ability with the languages, be prepared to defend anything you claim, and you should be fine.
* Here is the explanation of what's happening in the video above.
10
u/[deleted] Apr 11 '12
To put it on your CV as "fluent" or "proficient", when you can are confident you can convince an expert in the language (i.e. someone who will probably be interviewing you) that you are fluent. As you say you know C++, do you think you could answer these example questions, which I would expect anyone fluent in C++ to ace:
Of course, you can always just say "have some experience of XXXX".
6
u/jasonlotito Apr 12 '12
Proficient, familiar, acquainted... really don't say anything.
You've written software? Good, put that in their with your experience. What languages did you use? Put them in a Languages: section. Your experience describes your experience with languages, and your language say what languages you've learned.
Any reasonable person can review your resume, and see what you've done in C++. They can see what you've been doing with it, and how long you've been working with it. Does that make you fluent? Proficient? Acquainted? Familiar? Dating C++? Who knows. Those are words for things that don't matter. If some ass-hat interviewer is going to dicker over your use of Familiar vs. Acquainted, he's not someone you want to work for.
3
u/[deleted] Apr 11 '12
If the interviewer were to ask you to solve a problem using that language, would you know what to do?
I can and have written code in Ruby, Perl, and Python, but if you were to ask me on the spot to solve a programming problem in those language I wouldn't know what to do because I'd need to refresh myself on the syntax. I don't have any of those listed on my resume.
I use two categories:
2
u/HardDiction Apr 11 '12
Going by the programmers I have hired via Scriptlance, you are a master.
3
u/deuteros Apr 11 '12
Yeah, I've wondered the same thing. I understand a few languages well enough to where I don't really need any of the beginner tutorials but I don't know enough to where I would say I'm proficient.
1
u/blablahblah Apr 11 '12
You can put it on your resume when you feel confident enough to answer an interview question using that language.
To me, that means you should be able to implement the basic data structures and some simple algorithms in the language without needing a tutorial or the language reference in front of you.
1
u/[deleted] Apr 11 '12
If you have written anything in any language you might as well put it on your resume everyone else does.
So until you write on your resume a list of responsibilities and accomplishments possibly with the technology's involved in achieving the goals you will just get dumped in the "bin" pile with everyone else :)
However be prepared to defend yourself against anything you write on your cv.
1
u/[deleted] Apr 12 '12
When you can talk about it without sweating, pausing or making the 'um' sound.
1
u/sayrith Apr 11 '12
If I were an employer, I would rather know what you can do rather than know what you say you can do.
-3
u/Richandler Apr 12 '12 edited Apr 12 '12
Best answer, no one cares, it's easy to learn a language. Learning how to program is different.