How to indicate programming experience on a CV

Click For Summary

Discussion Overview

The discussion focuses on how to effectively indicate programming experience on a CV, particularly for REU (Research Experiences for Undergraduates) applications. Participants explore various ways to present their skills in programming languages such as C++, MATLAB, R, Java, and Fortran, considering the nuances of their experience levels and the context of their applications.

Discussion Character

  • Debate/contested
  • Technical explanation
  • Conceptual clarification

Main Points Raised

  • One participant expresses uncertainty about how to categorize their programming experience, suggesting that terms like "beginner" or years of experience may not accurately reflect their skills.
  • Another participant recommends including a brief description of projects to provide context for the programming languages listed on the CV.
  • Some participants argue that the number of lines of code written can indicate skill level, but this is contested by others who point out that complexity and dependency issues in projects may be more relevant than sheer volume.
  • A participant shares their own experience of categorizing programming skills on their CV, indicating proficiency in certain languages and some experience in others, while noting that the level of detail may depend on the specific REU application.
  • Another participant mentions that including specific project details can enhance the CV, contrasting vague statements about proficiency with concrete examples of work done.
  • There is a mention of not being asked about the number of lines of code written in interviews, suggesting variability in what employers prioritize during the hiring process.

Areas of Agreement / Disagreement

Participants express differing views on how to quantify and present programming experience, with no consensus on the best approach. Some advocate for including project descriptions, while others emphasize the importance of complexity over quantity.

Contextual Notes

Participants acknowledge that the effectiveness of their CV may depend on the specific requirements of the REU they are applying for, indicating that there are limitations based on context and audience expectations.

tcbh
Messages
37
Reaction score
0
(I'm putting this here as opposed to the Career forum because it's for REU applications)

I have some experience in C++, MATLAB and R, but I'm not sure how to indicate on the CV how much experience. I'm not an expert in any of them, but I don't know that "beginner" is right either. Years would be misleading too, since I don't program much outside of class and I don't always have classes that require programming.

Would it be too much to include a brief description of how I've used each language?
 
Physics news on Phys.org
tcbh said:
(I'm putting this here as opposed to the Career forum because it's for REU applications)

I have some experience in C++, MATLAB and R, but I'm not sure how to indicate on the CV how much experience. I'm not an expert in any of them, but I don't know that "beginner" is right either. Years would be misleading too, since I don't program much outside of class and I don't always have classes that require programming.

Would it be too much to include a brief description of how I've used each language?

It's hard to say since I don't know exactly what you are applying for, but here is what I think you should include:

a) The languages themselves and the platform if necessary (for example for Java no need for platform or .NET)

b) a simple description of the project that you worked on.

Don't go into lengthy complex statements about the specifics of the project, just state what the project was about (keep it as simple as possible but no simpler).

This will add context to your CV because it gives the reader a real idea of what you might know which will give an idea of whether to interview you or not. If you get the interview, then chances are the employer thinks you are a good candidate and your technical ability (among other things) will be tested there.
 
Also one thing that will give an interviewer a good idea of your skills is the number of lines of code you've written, and the number of lines of code there were in the system that you using.
 
twofish-quant said:
Also one thing that will give an interviewer a good idea of your skills is the number of lines of code you've written, and the number of lines of code there were in the system that you using.

I agree somewhat (especially with the number of lines in the system), but not completely.

You can have projects that have really really large subroutines and as a result have a lot of complexity, but it doesn't necessarily mean that it is more complex than say a more manageable subroutine that makes calls to a half a dozen to a dozen other systems or libraries that interact with one another.

If there are strange dependency issues between say libraries or other repositories, then this can cause really major headaches (as you are probably aware of in your job), and I would consider this a lot more challenging to do this right than do something where although the number of lines is huge, is still not as intensive as far as handling all these weird dependency issues that come about.
 
I recently had this same question, when preparing a CV for a physics graduate program. I didn't find a specific answer anywhere, but I ended up wording it something like this:

Programming Experience
Proficient with Java, Fortran
Some experience with C/C++, Perl, Mathematica, Matlab

and that's about it.

Of course, it depends on what REU you're applying for. If it's more about programming, you may want to include more details as mentioned in other replies.
 
My programming section looked very similar to bcbwilla and I got some quite decent software eng gigs with it. I also had a bit in my CV intro which described a few projects I worked on. It helps a lot if you mention exactly what you did with the language e.g. "wrote a java SOAP client for project X to integrate the CRM and web portal". Just "I am proficient with java" does not mean much at all unless your job is not programming focussed.

I have never been asked nor offered how many lines of code I have written nor did I ever ask others how many lines they wrote. I'm guessing some places may ask this however so be prepared for the question.
 

Similar threads

  • · Replies 4 ·
Replies
4
Views
2K
  • · Replies 3 ·
Replies
3
Views
2K
  • · Replies 11 ·
Replies
11
Views
2K
  • · Replies 3 ·
Replies
3
Views
1K
  • · Replies 12 ·
Replies
12
Views
2K
  • · Replies 5 ·
Replies
5
Views
3K
  • · Replies 2 ·
Replies
2
Views
2K
  • · Replies 2 ·
Replies
2
Views
2K
  • · Replies 7 ·
Replies
7
Views
2K
  • · Replies 7 ·
Replies
7
Views
4K