Re: Yet Another Recruiter Question

[Ned Bedinger <doc -at- edwordsmith -dot- com>]

I recently played out a page from the duelling agencies file.

An agency in another state sought me out, hoping to present me to a 
long-running local-to-me project of a big international consulting firm. 
I gave my permission, and then never heard back.  OK, I thought, 
winsome, lose some.

Several months later, a local recruiter sought me out with a position at 
a long-running local-to-us project of a big international consulting 
firm.  Being  aware of the problem caused by letting two different 
agencies submit me for the same job, I dug out the first job 
announcement, and read off the agency name and Job ID to my local 
recruiter.  She then check the Job ID and found that it was the same for 
the new position she was working to fill.  So she called the big 
international consulting firm to ask if there were two positions, or if 
perhaps if the original announcement had been withdrawn and re-issued.  
As it happened, they had re-used the job ID but wanted to hire another 
writer.

So, my diligent local recruiter contacted the out-of-state recruiter to 
see if they had submitted me for the second position. Huh?  <mumble 
mumble>. They said they'd have to get back to her with the answer.  They 
then got back to her the next day to say that yes, they were planning to 
submit me again.  They then had the original recruiter, whom I talked to 
months ago, call me again to say they'd gotten me an interview.

What a pity that my diligent, hard working local recruiter couldn't 
outmaneuver the neglectful one.  The one I eventually went to work for 
was sadly unprepared to work with distant employees, but by rights had 
me first.  I wish I had thought to jump in an tell them to back off if 
they were planning to submit me on the new position, but by the time the 
local recruiter called me to fill me in with the goings-on, it was too 
late.

Ned Bedinger
doc -at- edwordsmith -dot- com




Gene Kim-Eng wrote: