Re: Job recruitment in comp.databases.*

} } Paul Jones wrote: } > } > People have suggested a comp.database.jobs group. } > I agree, lets stop the noise before it gets too } > much and too ingrained in recruitment agency } > posting methods. } > Paul. } > } } The problem with creating this group though is that this problem is not } confined to the sybase group specifically. Many of these postings are } posted to all of the groups in the comp.databases hierarchy. } } If we are serious about creating this group, we should start soliciting } opinion on the other groups (I'm posting this to *some* of the other big } database groups to kick things off) } } But saying that, I agree with Pablo that the general concensus is to go } with doing nothing, adding "recuiter:" or asking them to stop. If thats } the general opinion, then is it not true this will be the consensus on } other groups (Sybase people aren't a breed unto themselves now, are } they?). } } If there is any form of comp.database.jobs we *need* to have: } } x Solid support from the reading community of the group(s) } x A well defined "charter". } x Participation of the posters. } } The first two I figure are things we can work on over time (The second } will perhaps bring about the first). } } The third is the *most* important. If the recruiters don't participate, } our efforts will be useless. (Of course, support begets votes, which } begets the group...) } } So, recruiters, how do you feel about our feelings - We'd like to have } some way of making your information MORE useful to those who want to } find out about jobs, and reduce the irratation for those who don't want } to? We're assuming you read the groups you post to (as suggested by } established netiquette) } } Non-Sybase groups - Your thoughts on this issue? } Hmmm, I get c.d.informix through a mail server so this is not going to be x-posted. I will forward it to c.d.i. as well. What we determined was to have a fixed format for the job requests - one that immediately makes it apparent what the posting is about. We even came up with a format and posted it - alas as you point out the recruiters don't necessarily follow that format. The nice thing about using that method is that you can have a kill entry to screen them out when your not interested. At the same time they are still there when you want to start reading them. Hang on a sec, let me see if I can find the format we came up with... } > ASG, Inc. is a nationwide contract consulting firm. We also do a fair } > amount of permanent placements. What is the prevailing NETIQUETTE } > regarding jobs postings to this list? } > Karen N. Servance } > Phone 919-467-0505 } > Fax 919-467-2469 } > } > } } Karen post points out that we don't really have a standard for job postings. } Might I suggest for your pleasure and discussion... } } 1 - identify the post as a JOB or OPP{ORTUNITY} in the subject line. } 2 - identify the location briefly in the subject line. } 3 - identify the desired skillset briefly in the subject line. } } e.g. 4gl JOB - Tampa, FL } NewEra JOB - London, UK } esql/c OPP - Cairo, EG{ypt} } } 4 - Restrict job postings to those requiring Informix skillsets. (This is } comp.databases.INFORMIX after all). } } Deletia? Additia? Oh, I remember - it never got farther than that - no interest in policing the recruiters. If we had such a standard across all groups then as informal netcops we could mail it to any recruiters as they became apparent. cheers j. _____________________________________________________________________________ Jack Parker - Hewlett Packard, DMD/IS Boise, Idaho, USA jparker@hpbs3645.boi.hp.com _____________________________________________________________________________ If anything can go wrong, fix it. To hell with Murphy. _____________________________________________________________________________ Any opinions expressed herein are my own and not those of my employers. _____________________________________________________________________________