experience using specific programming languages, technologies, and frameworks

Question

For listing my experience in certain software development skills, let's say I have had 2 years of VBA development experience, before having a gap where I have mainly been programming in C++ for 3 years, before I have another year of VBA-dominated development work. Would it be more accurate to say I have 3 years of VBA development experience or is it misleading to mention that I have known how to program VBA scripts for 6 years? It would be great to hear your thoughts as software industry professionals.

First additions:

I'm actually a soon-to-be college graduate who has those development skills either in school, work projects, or side projects that I pursue on my own. Knowing this, I would be truthful about the years to my knowledge and make sure that I can answer the interview questions well (something that I have done miserable in internship job interview situation that is still ongoing).

Answer 1

I think generally you can write so. But when you describe the projects you have worked on - specify the time and technology used. In all cases, a good interviewer will capture necessary information during interview.

Answer 2

Personally, after a certain point I'm more concerned with the overall amount of experience than I am with the actual experience with a particular technology. I assume a reasonably experienced and competent programmer will be able to pick up virtually any technology relatively quickly.

If I were you, I would list the various technologies in order of expertise. For each, job you might list the primary technology(ies) that you used in that job to give a better understanding of both the job and how you obtained the experience with the technology. As an interviewer this would give me better information that a list of technologies/years. For example, 4 years of experience with Java in college would count less to me than 1 year of experience with C# in an actual programming job. Similarly, experience programming with a technology is more important than say doing QA in a different technology.

Answer 3

We assume everyone lies on their resume. It's just safer that way. Only once we put them in front of a whiteboard for an interview and see them thinking on their feet do we make the decision. :) Recommendations from people we already know/work with are a plus but hard to come by.

Just make sure you can solve short problems in some language before you go to an interview.

Answer 4

Bear in mind your resume serves two purposes: first, the gatekeeper, often an HR person, will use it to determine if the hiring manager should talk with you at all. This can be a fairly mechanical process where skills represented on the resume are checked off against the hiring manager's shopping list. Second, once you make it to the interview, it will help guide the interviewer's line of questioning.

Hence, strive for brevity on your resume. Get your point across with as little verbiage as possible. If you have three years of a required skill scattered across twelve projects, mention the three years of experience and be done with it. Make sure your resume articulates your skills sufficiently that the hiring manager has reason to invite you in for an interview.