I notice that about 2/3 of these recruiters just lob their jobs postings towards any-old-where, and say only that they want personal help from some unspecified stranger (that would be me) in posting to "your site". I've conversed with some of them, and uniformly they really have no idea what they mean by "site" in this context; they figure you'll work hard to _figure out_ somewhere, as if figuring out where to put their posts is somehow _your_ problem. And they never, ever read documentation.
These people are paid for _what_, again?
(Jim feel free to post this on the SF-LUG page, if you wish. I'm sure she'll get around to you sooner or later, anyway.)
----- Forwarded message from "Marisela Peifer -X (mpeifer - Spherion at Cisco)" mpeifer@cisco.com -----
Date: Mon, 23 Oct 2006 15:09:08 -0700 From: "Marisela Peifer -X (mpeifer - Spherion at Cisco)" mpeifer@cisco.com To: balug-announce-owner@lists.balug.org Subject: Cisco Systems, Inc. is hiring
Hi Chris,
I would like to post to your site and let the users know that Cisco Systems, Inc. is hiring in San Jose, CA. I would appreciate any suggestions from you in this matter.
Title: Software Engineer-Networking (Multiple Openings)
Description: We are looking to hire software engineers ranging from Entry level to Experience level. This is an excellent opportunity to participate in development of software in the Data Center Business Unit (DCBU) for its next generation platform leading storage networking switches. The work involves design and development in customized Linux environment for some key infrastructure components in a variety of director class and fabric switches, to enable a long list of innovative features for Fiber Channel and Ethernet technologies.
You will be part of a fast-paced team responsible for delivering quality code for large complex systems requirements. Open communications, empowerment, innovation, teamwork and customer success are the foundations of the team with "pay for performance" culture. Thus, you set your own limits for learning, achievements and rewards.
You will be responsible for designing, and developing system software for next generation products. High availability, Hitless Software Upgrade, Scalability, Modularity, Usability are key considerations in all design and development work. You will be exposed to great design methodologies using finite state machines and various in-house tools/libraries. Work also involves providing constant feedback to ASIC, hardware and software teams for improvements. Write complete functional and design specs independently. Write portions of product spec. Lead development of subsystems. Design & Develop large portions of software independently and rapidly. Participate in Cisco's Patent Program.
Requirements: Knowledge and experience of complex software design for distributed systems in embedded networking/telecommunications projects. Proven track record of successful projects in similar products/technologies is preferred.
Must be proficient in C programming/debugging in Unix/Linux environment. Must have good software design skills.
Must have excellent oral and written communication skills; professional presentation skills is desired.
(MSCS or MSEE preferred)
Regards, Marisela Peifer Talent Acquisition and Management Cisco Systems, Inc Direct 408.527.5669 mpeifer@cisco.com
blocked::http://www.cisco.com/en/US/hmpgs/index.html
----- End forwarded message ----- ----- Forwarded message from Rick Moen rick@linuxmafia.com -----
Date: Mon, 23 Oct 2006 16:23:10 -0700 To: "Marisela Peifer -X (mpeifer - Spherion at Cisco)" mpeifer@cisco.com Subject: Re: Cisco Systems, Inc. is hiring From: Rick Moen rick@linuxmafia.com
Quoting Marisela Peifer -X (mpeifer - Spherion at Cisco) (mpeifer@cisco.com):
Hi Chris,
I would like to post to your site and let the users know that Cisco Systems, Inc. is hiring in San Jose, CA. I would appreciate any suggestions from you in this matter.
Hi, Marisela.
BALUG doesn't have a real jobs forum, though I can recommend some others nearby -- and balug-announce is mostly for announcements of BALUG events. One exception (see http://lists.balug.org/listinfo.cgi/balug-talk-balug.org): Any firm is welcome post Linux-related jobs listings to the main BALUG list if it simultaneously offers to provide a technical speaker (on a Linux topic) for one of BALUG's monthly meetings in San Francisco.
Aside from that, I can recommend either the SVLUG Jobs mailing list or the equivalent one at BayLISA. URLs are on the page indicated above.
Good hunting!
----- End forwarded message -----
Quality (and/or lack thereof) varies radically among recruiters/agencies. That was especially evident in the dot com boom, but was also quite well before that, ... and continues to be evident after the dot com bubble burst. This likely also well applies also to "internal" recuirters (certainly applies to managers, likely well applies to internal recuirters also - at least speaking over-all).
Some (semi-?)random thoughts on moderation on the list(s). Might we want to tweak the configuration so the "nag" e-mails only go out at most once per day? ... I forget the precise name/description on that option, but that could cut down any flurries of e-mail notifications for those cases (or days) when we get a relative flood of spam e-mail or other e-mail that gets snagged for "moderator approval". I can't really think of too many plausible cases where we'd need to handle incoming e-mail items of such nature in less than 24 hours. I thought about adding myself to the notification list (for the "nag" e-mails) ... but don't really want a flurry of such e-mails when a lot of items that get snagged for moderation come in ... but a max of one notification e-mail per day per list I could reasonably tollerate (and I'd guestimate some other folks that might consider "volunteering" for such duty/monitoring may feel similarly). Anyway, ... just a thought on that, anyway. Anyone have any particular opinions either way on that?
Also, I wouldn't feel any "great need" to spend much time and energy dealing with such "broadcast" job announcement that are, e.g., sent to lots of folks, groups, and/or lists, or Bcced to most recipients or otherwise show signs of likely being a "bulk" e-mailing. Can always queue a bunch of 'em up and if one still feels inclined to reply, e-mail 'em back in a single generic message, and let 'em figure it out ;-). ( Dear recruiter/agency, thank you for your interest in BALUG. Please direct your attention to ... )
Anyway, ... just some thoughts.
Quoting Rick Moen rick@linuxmafia.com:
I notice that about 2/3 of these recruiters just lob their jobs postings towards any-old-where, and say only that they want personal help from some unspecified stranger (that would be me) in posting to "your site". I've conversed with some of them, and uniformly they really have no idea what they mean by "site" in this context; they figure you'll work hard to _figure out_ somewhere, as if figuring out where to put their posts is somehow _your_ problem. And they never, ever read documentation.
These people are paid for _what_, again?
(Jim feel free to post this on the SF-LUG page, if you wish. I'm sure she'll get around to you sooner or later, anyway.)
----- Forwarded message from "Marisela Peifer -X (mpeifer - Spherion at Cisco)" mpeifer@cisco.com -----
Date: Mon, 23 Oct 2006 15:09:08 -0700 From: "Marisela Peifer -X (mpeifer - Spherion at Cisco)" mpeifer@cisco.com
Quoting Michael Paoli (Michael.Paoli@cal.berkeley.edu):
Might we want to tweak the configuration so the "nag" e-mails only go out at most once per day?
Unfortunately, I know of none. There's an option of enabling or suppressing immediate notice of pending _subscribe_ requests (for mailing lists requiring listadmin approval on join requests), such that those are sent only in the daily reminder batch. Or you might be thinking of the digest mode option for _list_ mail sent to subscribers -- as distinct from moderation-needed (nagmail) notices to listadmins/moderators.
We could set "Discard held messages older than this number of days. Use 0 for no automatic discarding." to something other than the zero default -- say, to one day. That would lose most spam, at the risk of occasionally discarding something legitimate.
The above is a poor remedy, attempting to partially compensate for Dreamhost being basically pretty incompetent at its task of spam-rejection at the MTA level. Just to clarify: That is not a complaint, but I think it's helpful to recognise the fact, if only to clarify what exactly Michael's talking about: Most people reading balug-admin will be unaware of this, but the listadmins are called upon to "moderate" some 15-20 held non-subscriber postings per day, aimed at each of our mailing lists, essentially all of those being spam (mostly Japanese).
I personally do a _much_ better job of spam-rejection at my own MTA, and nobody's paying me for that. Dreamhost is screwing up the same task by the numbers, and this is an important (if difficult) part of their _job_.
BALUG is currently, via its moderation messages and spam sent directly to Mailman *-owner and *-bounces mailboxes, the second biggest source of spam in my life, vying for first place with Bay Area FreeBSD User Group's Mailman addresses (a group for which I also do listadmin duty).
I thought I recalled such an option ... perhaps it's buried in the details. Looking again, I see: Should the list moderators get immediate notice of new requests, as well as daily notices about collected ones? [ ] No [X] Yes And was thinking we ought to change that to: [X] No [ ] Yes
From the linked "help" text, we have (_emphasis_ added):
balug-announce Mailing list Configuration Help admin_immed_notify Option admin_immed_notify (general): Should the list moderators get immediate notice of new requests, as well as daily notices about collected ones?
List moderators (and list administrators) are sent daily reminders of requests pending approval, like subscriptions to a moderated list, or _postings that are being held for one reason or another_. Setting this option causes notices to be sent immediately on the arrival of new requests as well.
I was thinking, if no one (or not of the list administrators/moderators) object, we probably ought to change that option to No, and that would cut down the "annoyance" factor of the "nag" e-mails (perhaps also encouraging more folks, as/if needed/warranted to get themselves also added so they get those "nag" e-mails too). Again, I think it's exceedingly rare (if ever) that items that get held for moderation require moderators to know about their being held "immediately", as opposed to having a delay of up to 24 hours before they're modified. So I'd tend to think it's probably more beneficial to flip that immediate notification option to No ... and for all 3 BALUG lists.
Of course I'm also hoping the option behaves as "advertised" (documented).
Quoting Rick Moen rick@linuxmafia.com:
Quoting Michael Paoli (Michael.Paoli@cal.berkeley.edu):
Might we want to tweak the configuration so the "nag" e-mails only go out at most once per day?
Unfortunately, I know of none. There's an option of enabling or suppressing immediate notice of pending _subscribe_ requests (for mailing lists requiring listadmin approval on join requests), such that those are sent only in the daily reminder batch. Or you might be thinking of the digest mode option for _list_ mail sent to subscribers -- as distinct from moderation-needed (nagmail) notices to listadmins/moderators.
We could set "Discard held messages older than this number of days. Use 0 for no automatic discarding." to something other than the zero default -- say, to one day. That would lose most spam, at the risk of occasionally discarding something legitimate.
The above is a poor remedy, attempting to partially compensate for Dreamhost being basically pretty incompetent at its task of spam-rejection at the MTA level. Just to clarify: That is not a complaint, but I think it's helpful to recognise the fact, if only to clarify what exactly Michael's talking about: Most people reading balug-admin will be unaware of this, but the listadmins are called upon to "moderate" some 15-20 held non-subscriber postings per day, aimed at each of our mailing lists, essentially all of those being spam (mostly Japanese).
I personally do a _much_ better job of spam-rejection at my own MTA, and nobody's paying me for that. Dreamhost is screwing up the same task by the numbers, and this is an important (if difficult) part of their _job_.
BALUG is currently, via its moderation messages and spam sent directly to Mailman *-owner and *-bounces mailboxes, the second biggest source of spam in my life, vying for first place with Bay Area FreeBSD User Group's Mailman addresses (a group for which I also do listadmin duty).