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.
Keith asks about questions (other than $$) to ask recruiters
who come a'callin' ...
Basically, ask them anything you'd ask during a screening
interview, except the name of the company they're representing.
Some of my favorites, in no particular order:
- Where is the company located?
- Why do they need a TCer?
- What happened to the last contractor who filled this spot?
- Is telecommuting an option?
- Can you provide a basic description of the product and the
information development needs?
- Is this solo work, or team work?
- What's the company's attitude toward TCers?
- What's the environment like?
- What's the duration of the gig?
- Do you (recruiter) specialize in handling TCers?
- How many TCers currently onstaff or on contract?
- How screaming is the need?
- What are the conversion options?
- What are the tools/skillsets necessary to be successful?
- What's the OS environment?
Don't, however, be surprised if at least half the questions cause
the recruiter to hem and haw. They don't seem to be used to being
interviewed about specifics, and a lot of recruiters don't have
the foggiest notion of what we do.
