While I suffer the same predicament, I find it amusing that ask "Why can't recruiters read?". A common assumption is that users do not read when trying to accomplish a task.
Whenever they contact me w/ "Leonardo job" or a J2EE job, I remind myself that these users are motivated by incentives to find candidates. Unfortunately, that mixes with their nearly complete lack of familiarity with terms that we take for granted. You could mine that opportunity and build an app that aggregates jobs and candidates, then maps skills. That might look like a wizard to an uninformed recruiter, and it would be a big relief to people like us. I hope this helps. On Thu, Mar 27, 2008 at 12:55 PM, W Evans <[EMAIL PROTECTED]> wrote: > "Hi, is this Will Evans," the unknown voice asked. > > "Yes, it is, who is this?" > > "This is Sarah X from CTR, Clueless Technical Resources, and we had an > opportunity that we think might be a great fit for you." > > "Really - do tell?" > > "We have a great opportunity for a 3 month contract as a J2EE Architect > for > a Fortune 500 company in Des Moines, Iowa." > > "Excellent - you do realize that I have never coded java before, I am > moving > to DC on Saturday...and don't travel for short term contract work..." > > "Can I ask you what your rate is" > > "Um... a three month contract 1000 miles from where I live doing something > I > have never done for a big evil multinational that destroys labor unions > while not offering health care benefits to it's employees....can I get > back > to you on that?" > ------ > Why can't recruiters read? > > I know I have had a resume posted on Monster since about 2003, and I do > update it every 6 months or so even though I have never gotten a job from > monster - but what really burns my goat is that I very clearly say: > 1. I have done IA and IxD work for a really long time > 2. I have no interest in relocating for short term contracts > 3. how much I cost > > Yet they never read that. I want to put together a list of all the "Good" > not evil recruiting firms that actually know the difference between an > interaction designer, information architect, and UI engineer - at least > knows enough to know we aren't Java or .Net engineers. > > Post back to me recruiters that are great -on either side of the hiring > equation. It might be nice to have a list of places to go that "get us" > > -- > ~ will > > "Where you innovate, how you innovate, > and what you innovate are design problems" > ________________________________________________________________ > Welcome to the Interaction Design Association (IxDA)! > To post to this list ....... [EMAIL PROTECTED] > Unsubscribe ................ http://www.ixda.org/unsubscribe > List Guidelines ............ http://www.ixda.org/guidelines > List Help .................. http://www.ixda.org/help > -- Jay A. Morgan Information Architect. Business man. ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
