New Skill : When do you?

Pho3nix

Pho3nix

The Legend
Joined
Jul 31, 2009
Messages
32,826
Reaction score
3,033
Location
On the toilet
When do you actually add a new skill onto your CV?
After you've installed the Software and played around a bit :p
After you've created your first project?
Or only after you've created your first management dashboard or production ready version?

Just curious :)
 
I dont have a CV really.

but if I did, I would update it according to the job I was interviewing/applying for :)
 
Pho3nix said:
When do you actually add a new skill onto your CV?
After you've installed the Software and played around a bit :p
After you've created your first project?
Or only after you've created your first management dashboard or production ready version?

Just curious :)
Click to expand...

have a guy here at work who seems to read about something - he adds it onto his cv/linkedin. Tis rather amusing ;-)
 
I would add a technology to my cv if I played around with it, but only if I did enough that I could talk about how I planned/designed and developed something with it - that way you have a story to tell.
 
You have "experience" when you have been paid to do it.

Otherwise it's as relevant as any other education certificates you have.
 
Once you know it well enough for it to become a skill. You don't fire a rifle once and call yourself a marksman.
 
Depends on the job you are seeking. If the recruiter is looking for someone with basics of the technology then you can add as soon as you are confident you can talk the basics. If they are looking for people with installation experience then add when you have done the installation. And so on...
 
It's always better to put it even if you don't know it, that way you'll be forced to learn it when you get the job.
 
abzo said:
It's always better to put it even if you don't know it, that way you'll be forced to learn it when you get the job.
Click to expand...

Except if they question you on it during an interview. Not a good idea...
 
abzo said:
It's always better to put it even if you don't know it, that way you'll be forced to learn it when you get the job.
Click to expand...

So you bull***** your way through all interviews?
 
Mike Hoxbig said:
Once you know it well enough for it to become a skill. You don't fire a rifle once and call yourself a marksman.
Click to expand...
x2

I don't feel comfortable adding something until I've had months of experience with it.

But I also don't usually update my CV THAT often...

abzo said:
It's always better to put it even if you don't know it, that way you'll be forced to learn it when you get the job.
Click to expand...

LOL. You clearly don't interview with the same companies I do.
 
Last edited:
I'll add one on linkedin when I'm comfortable to be quizzed on it/sit and do it/etc and when I feel it's something people will actually endorse me for. Some people I see adding skills on their profiles and I'm not even sure they know the meaning of the word...

In fact linkedin should put a "bull****" button next to "endorse" :)
 
I put the skill, plus the amount of experience I have with it. That way, the person viewing my CV can see that I'm not scared to try out new things, but I'm also not trying to sell a skill I'm not an expert in.
 
Use a skills matrix, with columns for # of months used, level (1 - training only, ... 5 - expert experience) & date last used.
 
kripstoe said:
I HATE those with a passion.
Click to expand...
Lol, I think every IT person who's looked for a job does... Every recruiter wants it in a different format and for you to do the whole thing again in their own format...
 
Hypothetical new employer/CTO asks you to implement said skill in a production environment. Do you sht your pants? If yes...then it doesn't go CV.
 
rorz0r said:
Lol, I think every IT person who's looked for a job does... Every recruiter wants it in a different format and for you to do the whole thing again in their own format...
Click to expand...

I honestly wouldn't mind doing it if it helped in anything. The problem is that job specs drawn up by a bunch of HR retards expect you to be 100% proficient in every available technology. To them, IT means anything to do with a computer except Office, because its what they use.
 
Would it not be better to finish some project at work, then n your cv, you talk about the flow and business impact?

Example:
So one of the projects that i was working on, I created a service in c# for windows to read through text files, line by line, to extract information to populate a few variables and send those variables to my snmp function. blah blah blah..

Is that a good way to avoid technical questions in an interview?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X