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: Advice needed for an upcoming interview From:Michael McCallister <workingwriter -at- gmail -dot- com> Date:Tue, 23 Apr 2013 09:46:48 -0500
What Anne and Dan have said are absolutely true. Don't be scared by the
prospect of running that marathon on Thursday. Chances are, that means
you're close to sealing the deal.
To help calm your nerves a little, here's a free excerpt from the O'Reilly
"Mastering Regular Expressions" book: http://cdn.oreilly.com/oreilly/booksamplers/9780596528126_sampler.pdf. Head
over to your public library today, and pick up a copy of this or other
books on regular expressions (Perl books would be helpful in this regard
too). While they are not likely to quiz you on your knowledge of regex, at
least you won't freeze if they mention something in passing.
Have some questions ready for them: Ask them about the workflow processes
they have, whether you'll have access to the bug tracking system, and how
they've documented their API in the past.
Above all, relax! Best of luck!
Mike
Mike McCallister
In stores now: 2nd Edition of "WordPress in Depth" (with Bud Smith)
Notes from the Metaverse: http://metaverse.wordpress.com
On Tue, Apr 23, 2013 at 9:02 AM, Anonymous <anonymous -at- techwhirl -dot- com> wrote:
> *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?
>
> Learn more: http://bit.ly/13xpg5n
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as workingwriter -at- gmail -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> info.
>
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>From our sponsor Doc-to-Help: Want to see a Doc-To-Help web-based Help sample with DISQUS for user commenting?