As seen on a resume...
That's enough qualifications to do the job of eight people!
I've used most of those (PeopleTools, I don't know), but I definitely wouldn't put them on a resume; because I don't think I know enough.
Is that person implying frequent use or familiarity ? Passing "I've seen what this looks like, read some code, fiddled with it" type answers are certainly possible.. Developer level, I-dont-need-no-stinking-reference-manual type knowledge.. ? umm, wow.
Re:*shrug*
Whammo on 2004-04-07T22:30:20
That's why I extend linguistical concepts to my resumé, based on my (perceived) ability to read (understand) and write (produce) some technology: fluent, literate, conversant, and familiar.
Most interviewers have commented favorably on that approach, although I have had to explain it more often than not.
Re:*shrug*
gav on 2004-04-08T03:48:26
I think I'm going to steal that idea. I split my skills into similar categories, they just didn't sound as impressive. I still think I need an extra category for "acronyms beginning with 'X' I call bullshit my way through", is there a proper linguistical term for that?Re:*shrug*
merlyn on 2004-04-08T11:14:23
I still think I need an extra category for "acronyms beginning with 'X' I call bullshit my way through", is there a proper linguistical term for that?Just mark that down as "fluent", just like the next guy.
Re:I'm with phillup
gav on 2004-04-08T03:53:04
At least he didn't commit the sin of writing "C/C++", though calling HTML a language is almost as bad.
The real shock to me is that somebody would claim that they had working knowledge of so many disparate technologies.Re:I'm with phillup
delegatrix on 2004-04-09T02:33:33
Yeah, I'm always skeptical when too many odd combinations are listed. I think those resume sections need to be targetted for the job under consideration. If the job was such that all those Java, Perl, XML skills are listed, why bother cramming in Dreamweaver, too? I usually don't care if my programmers know MX or not.