TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:RE: Question of the Day From:"James Barrow" <vrfour -at- verizon -dot- net> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Thu, 16 Nov 2006 12:20:32 -0800
>Gene Kim-Eng wrote:
>>Jim Barrow wrote:
>>If I find the perfect job that's 50 miles away, and a recruiter deems
>>that too far, how would I tactfully do a little arm-twisting to get
>>him/her to send my resume to the client anyway?
>The big question here is why the recruiter thinks so. Is it just
>his/her personal view, or has the client specified that the person hired
>needs to be able to be on-call and able to get to the office within x
>minutes on occaision? I've never heard of this as a requirement for a
>writer, but the world is full of people with odd ideas.
It seems to me that the recruiter was making a judgment call and decided
that "x" miles was too far for me to drive on a daily basis. Sometime these
recruiters qualify their decision not to submit me with "The client needs
someone on-site every day".
What irks me is when I point out that I made similar commutes in the past
with no problems. I guess I just don't like to be what my best interest is.
If I say that a 50 mile trip to and from work is not a problem, then that
should be the end of it.