Subj : Re: SeekJob keywords (was: How much should I charge for fixed-price...)
To   : comp.lang.lisp,comp.programming,comp.lang.java.programmer
From : .
Date : Thu Aug 25 2005 04:33 pm

On Wed, 24 Aug 2005, Robert Maas, see http://tinyurl.com/uh3t wrote:

> > From: Tim X <t...@spamto.devnul.com>
> > in larger organisations, the initial culling of applications is
> > usually done by some junior staff member from the HR department - they
> > know nothing about programming, computer or IT. They have a list of key
> > words or criteria which they look for - those that have it get to the
> > next stage, those that don't get filed in the round filing cabinet
> > under the desk!
>
> So would you recommend the keywords be listed in logical sections, such
> as programming languages in one list, platforms in another list,
> application areas in another list, etc., or should I just mix all the
> unrelated keywords together in one huge alphabetical list to make it
> easy for the junior staff member to find the keywords he/she is looking
> for?

Robert,

I, personally, write my resume so the company knows who I am and what I
can do for them. If they list requirements I will make it INCREDIBLY easy
for them to see that I meet or exceed their requirements. If the company
uses someone who just scans the resume for keywords then most likely they
are scanning the resume for keywords relating to the requirements for the
position.

If they are just looking for a list of unrelated keywords then why would
you want to work for them.

For example, if you apply for a job at IBM they have you do an online
application. The application will quiz you on your skill set and level of
experience. You will notice that all the technologies they quiz you about
are also listed in the job ad requirements.

> > All of that could have been summarised as something like x years
> > assembler programming.
>
> Which is better keyword for that: assembler or assembly-language?
> Or should both be included in case the junior staff member is looking
> for the other one and doesn't realize they mean the same thing?

I never worry about this sort of thing. If the company is not going to put
forth the effort to know assembler and assembly-language are the same
thing then why would I want to work for them. I'm willing to put a great
deal of effort into applying for a job but I expect the employer to put
some effort into it as well.

-- 
Send e-mail to: darrell dot grainger at utoronto dot ca

.