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.
>For those that I haven't, including one that they said they were extending
>an offer to me but they just changed their minds, I've often gotten the
>feedback that I "wasn't technical enough".
>
>In the context of technical writing as the job, what the hell does that
>mean?
Possible interpretations:
1.) You don't have the tool knowledge that we need.
2.) You don't have enough knowledge of the technology that the
company works in.
3.) We've decided not to hire you, but we don't care to give the
real reason.
If you're hearing this comment repeatedly, you might want to
consider whether you're applying for the right sort of job.
Otherwise, all that really matters is that you're not being
hired. You'll never know when a company is telling you the truth
about why you're not hired anyway.
--
Bruce Byfield, Outlaw Communications
Contributing Editor, Maximum Linux
bbyfield -at- axionet -dot- com | Tel: 604.421.7189
"Better a good run than a bad stand." -James Keelaghan
