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.
*Please post your responses to the list, as replies cannot be forwarded to
the anonymous poster.*
I have a job interview on Thursday. I documented an embedded version of the
company's product at a previous position, so I have some familiarity with
it. But self-doubt begins to creep in as the interview approaches,
especially since it's scheduled to last 4 hours and includes a technical VP
and I feel that my technical skills are my weakest attribute (shamefully, I
don't know any programming languages).
Does anyone have advice for how to endure such a long interview? What kind
of questions should I be prepared for, especially from the VP and the SE
that will be interviewing me?
The company's product makes heavy use of both regular expressions and APIs.
There were recently a couple of threads about good API documentation that
are good resources. But how about regular expressions? Any suggestions for
reading up on those?
I am just starting out in this field: if I get this job, it would be only
my third position as a technical writer, so please excuse these rather
nervous and fundamental questions. Any other advice, of course, would also
be greatly appreciated.
Thank you.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>From our sponsor Doc-to-Help: Want to see a Doc-To-Help web-based Help sample with DISQUS for user commenting?
