When writing a CV, what should I do with 'weak skills'?

Question

I'm presenting writing a new CV, and I've got a set of programming skills I consider to be 'strong' and programming skills that I consider to be 'weak'.

Example

C++ for me would be strong as I know the language syntax well enough I could write a program, compile it, interpret errors, follow good design philosophy etc without needing to regularly look at references.

But SQL, for me, would be weak. Whilst I understand how SQL works, the rough syntax, what the program expects of me datawise, a vague understanding of good practices, I wouldn't be able to utilise it without double-checking references, simply because I use it so rarely.

Personal experience

Clearly I know more than someone who doesn't know SQL, but I feel putting SQL as a skill on my CV might mislead an interviewer into thinking I have a natural capability. I've also had experiences where a skill I've considered 'weak' turned out to exceed the requirements of the interviewer (who assumed my skill was barely above layman).

Question

What do I do with 'weak' skills on a CV? Highlight they're weak? Omit them? Include them with other skills and rely on the interviewer to do due diligence in personal interviews? Or something else?

Answer 1

Depends upon on how you layout your CV. With your SQL example, definitly include it, you have experience in it.

Let's say you just list them, without qualifying them: Include it. If you worked with it, it's often the most prudent to include.

Filter your technologies by how applicable they are to the position in frontend of you.

For experience, think about some phrases you can use. E.g.:

• First experiences
• some experience
• extensive experience
• expert

And by what you write, rate yourself as c++ expert with some sql experience.

As IT people, we often see how much is missing in our knowledge instead of how much we already achieved. Thus the mismatch with past interviewers. The CV is the step to get to the actual interview. Don't lie, but always present yourself in a good light.

Answer 2

You can include what you're best at and what the job requires at the top of your resume, and demote or completely remove skills that aren't necessary. For instance, if a job post doesn't require SQL, you can probably exclude it completely from your resume.

For example, I don't know what you'd be promoting yourself as, but if you're seeking C++ jobs, you can include your expertise in a description about yourself at the top.

"Expert C++ programmer with 5+ years experience on Agile projects".

You could also include relevant keywords at the top of your resume, but just highlighting C++, as well as other skills. If the job mentions SQL but you're not an expert, include it at the bottom, maybe with a list of other skills.

"Full-stack developer with 5+ years in on Agile projects"

• Expert knowledge of C++
• Good design philosophy
• Ability to work independently

[resume stuff here]

• Familiarity with: SQL, Java, Photoshop . . .

If it's something that people in the industry you're targeting would value, I would find a way to include it. If not, just leave it off and focus on what's relevant.

Answer 3

Leaving out something you've come across in your work will put you out of the running with anyplace that uses a keyword scanner to select the first cut from the resume pile. (Whether you'd want to work for a company that does its recruiting that way is another discussion.) On the other hand, overselling it by implying that you're good it isn't a good idea, nor is saying something negative like "I can do SQL, but I suck at it."

I'm not a fan of trying to attach any kind of level (novice, expert) or quantity (some, extensive) to my experience because those terms are very subjective. Good interviewers will ask questions to tease that out to their own satisfaction.

Earlier in my career, I split the language laundry list into two categories: proficient for the things I used daily and some exposure for whatever I didn't spend a lot of time with but might have found some take-aways for use in other work. That worked out well when the lists were shorter and it hadn't been very long since I did daily work in the languages in the proficient category.

Over time, it has become apparent that proficiency is temporary. Since resumes/CVs are about accomplishments, I decided to re-frame it in those terms. Now I list current or recent for what I can do in my sleep, past projects for things I used to be able to do in my sleep and some exposure for everything else. There's nothing misleading in that and, again, anyone wanting more detail will ask.