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.
(Don't take this too negatively... but I can't resist, sir.)
> -------- Original Message --------
> From: Simon North <simonxml -at- gmail -dot- com>
>
> ...we are desperate to find technical writers who are not afraid
> to dive into the code and can write code themselves if need be.
I imagine that it is VERY hard to find that sort of candidate...
considering that what you describe is a software engineer with extensive
writing and production tools experience. NOT a "technical writer" who
can "write code." Especially given the complexity of your company's
products! :)
Of course, if you're listing that "technical writer" job at about $180K,
you might get some quality candidates. But if you're going "senior tech
writer, must be able to read code" at the 'normal' rates... yeah, good
luck.
I once ran into the same situation at a Major Statistical Software
Company, where one of its co-founders wanted to hire a "tech writer who
can do statistics, particularly to make examples of complex models". At
normal, local rates for that company (respectable... for a tech writer).
By the end of the phone interview, I was advising the hiring manager to
pursue mathematics professors with good publication records, and suck up
the time and costs to train him or her on tools and production
processes. I was happy to come on board, and would take night classes in
stats to to become more expert. I even suggested consulting with local
professors to make the examples (I mean, come on... how many are needed,
versus ALL the other documentation of processes and controls?!).
Within a few weeks, the job listing changed. :)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Learn more about Adobe Technical Communication Suite (2015 Release) | http://bit.ly/1FR7zNW
