Re: Requirements feedback for jobs.postgresql.org. - Mailing list pgsql-www

From Marc G. Fournier
Subject Re: Requirements feedback for jobs.postgresql.org.
Date
Msg-id 20031212145510.Q17041@ganymede.hub.org
Whole thread Raw
In response to Re: Requirements feedback for jobs.postgresql.org.  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Requirements feedback for jobs.postgresql.org.  (Josh Berkus <josh@agliodbs.com>)
Re: Requirements feedback for jobs.postgresql.org.  (Francisco Reyes <francisco@natserv.net>)
List pgsql-www
On Fri, 12 Dec 2003, Josh Berkus wrote:

> > On the first page I would like to better understand what you mean by
> > "Applications will be received by the jobs... and forwarded
> > on to a specified email... to prevent email spiders? I wasn't clear after
> > that what will be emailed to users? The contact info?
>
> In other words:

> Employers will enter jobs and their contact info.  The jobs but *not*
> the contact info will be made public. Applicants will fill out a form,
> and the system will e-mail its contents (and any attached resume) to the
> employer.
>
> There are a few reasons for doing things this way rather than simply posting
> the employer's contact info and letting people contact them on their own.
> These include:
> -- Protection for employers from being bombarded with spam every time they
> post an ad;
> -- Protection for our job listings from being "mined" by an agency or online
> job web site;
> -- Preserving the possibility of eventually turing jobs.postgresql.org into a
> revenue stream to support postgresql.

Altho I agree with all three reasons, in this day and age of heavy spam, I
think 1 is definitely the big one ... but ...

What information is provided about the "employer"?  I take it company name
and such is still provided?

> Certainly we want to stick to a small number of easy-to-understand
> categories.  For example, I was thinking of: Database Administrator
> (DBA), Software Development, Performance Tuning, PostgreSQL Support,
> General System Administrator, Training, and Other.

Will cross-categories be permitted?  Maybe a max of 2 or 3 per job
description, but would provide a bit better coverage where some overlap
may be appropriate?

> > From company to company, local to local, country to country views on a set
> > of job duties may vary and type may just be a point of confusion.
>
> Or may not.   Look, from my perspective, I don't want to even see jobs in the
> "General System Administrator" category; they don't apply to me.   Other
> applicants may *only* be qualified for training.  They should be allowed to
> filter by this, just like applicants will filter by Full-Time, Part-Time, or
> Consultant to match their availability.

Point: there is nothing that stops an applicant from searching other
categories ... if they can't find something under "DBA", but are wondering
if something is available under GSA, they can still go check it out ...


----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org           Yahoo!: yscrappy              ICQ: 7615664

pgsql-www by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Requirements feedback for jobs.postgresql.org.
Next
From: Josh Berkus
Date:
Subject: Re: Requirements feedback for jobs.postgresql.org.