Take the 2-minute tour ×
The Workplace Stack Exchange is a question and answer site for members of the workforce navigating the professional setting. It's 100% free, no registration required.

Technical Expertise:

Languages & Frameworks:       C, C++, Qt
Development tools:            GCC, GDB, Valgrind, SVN
OS:                           Linux (OpenSUSE)
Concepts::                    UML, Design patterns, Socket programming, Data structures

This is a sample from my example resume.

I know these subjects but I cannot say that I am an expert in these subjects. I do not want to mislead the interviewer by the fancy words like "Technical Expertise".

I want him to question me but not like as if I am a God or a super man!
What heading should be written instead of "Technical Expertise" when I am not an "expert"?

share|improve this question
add comment

3 Answers

up vote 10 down vote accepted

Experience would be the most obvious choice. This way all you are implying is that you have used these technologies and could have varying levels of skill.

Skill would also work as you are identifying specific areas though this doesn't always work as some software may not be seen as a skill.

Proficiencies would be a more formalized term if you wanted something a bit more exotic than experience.

share|improve this answer
    
"Technical Experience" indeed doesn't sound "Godly". Thanks. –  TheIndependentAquarius Jan 29 '13 at 5:22
    
'Experience' is usually taken to mean time spent doing something, and is not the same as expertize. It is possible to have a high level of expertize but little experience, or vica versa. Not that I'm saying I prefer expertize over experience... –  DJClayworth Jan 29 '13 at 15:29
add comment

No the original heading is fine. I think your over thinking this in English "expertize" (or expertise if you don't use the OED) can also mean "Skill or knowledge in a particular area" - This is the sense that it is always used in CV's and resumes.

I might say I have expertize in TCP/IP doesn't meant that I am claiming CCIE level understanding

share|improve this answer
1  
I'm not sure whether to vote this down or not (I haven't), as I agree with the OP that "expertise" refers specifically to an expert level of skill, knowledge or experience - see dictionary.reference.com/browse/expertise . –  Mark Bannister Jan 29 '13 at 13:45
1  
This answer is right. You can have a 'low level of expertize', meaning you are not an expert at something. –  DJClayworth Jan 29 '13 at 14:42
    
+Mark Banister no its not look up the defination in a dictionary –  Neuro Jan 29 '13 at 15:04
1  
@Neuro: look at the link in my previous comment - you will see it is a dictionary reference. It is also bad practise to refer another user to a dictionary in a sentence that displays poor spelling and punctuation. –  Mark Bannister Jan 29 '13 at 19:27
    
I think the word "expertise" might create a communication gap when the interviewer is a non-native English speaker!?! –  TheIndependentAquarius Jan 31 '13 at 5:10
show 3 more comments

Technical recruiter here that has seen many thousands of resumes, and I've never seen "Technical Expertise" used on a resume (I'm in the US). The most accepted sections for that title would be either "Skills", "Technical Skills", "Technologies", or "Technical Experience".

share|improve this answer
1  
Hi Fecak. Thank you for sharing your experiences. Can you please tell us why these terms you list are better? –  jmort253 Feb 4 '13 at 0:58
    
Jmort253 - I never said they were better. If you read my comment, I said I had never seen the term Expertise used, and that the terms I listed were most accepted (common might be more accurate). Expertise, as was stated earlier, may come across as somewhat vain, and having 'expertise' with a technology is different than having 'experience' or exposure. If you use 'Expertise', you might be more reluctant to list a technology that you have light exposure to, but you could list more liberally if you refer to 'Experience' or 'Skill' (skill has a wide implied range). –  fecak Feb 4 '13 at 2:04
1  
Hi Fecak, sorry, I wasn't trying to put words in your mouth, but I suggest putting your explanation from the above comment in your answer as it does help support it even more. In short, it would help ensure your post is more of an answer than just a comment. Hope this helps! :) –  jmort253 Feb 4 '13 at 2:45
    
No offense taken. However, if you reread the question posed (What heading should be written...), what I provided was absolutely a very direct and complete answer to the question posed (list of accepted terms) and not just a comment. –  fecak Feb 4 '13 at 3:06
1  
Hi Fecak, I do think you brought up good points in your answer, and I personally don't plan to take any action on this post, but our faq does say that "answers should be backed up either with a reference, or experiences that happened to you personally. You should always include in your answer information about why you think your answer is correct." I don't want to debate whether or not you've done that here, but I do know that if you add the info from your comment to the answer, there will be less to debate with others, and your answer will be more likely to get upvoted. Good luck! :) –  jmort253 Feb 4 '13 at 4:54
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.