[Author Prev][Author Next][Thread Prev][Thread Next]
[Author Index (this month)][Thread Index (this month)][Top of Archive]

Re: Why don't more job interviews use writing tests?

Subject: Re: Why don't more job interviews use writing tests?
From: Iliana Kostova <i_kostadinova -at- prosyst -dot- bg>
To: "TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Thu, 10 Feb 2005 15:31:42 +0200


Mike O. wrote:

Iliana Kostova wrote:

As a publications manager, I tend to always check new applicants on-site by making them write a procedure that a programmer or a system operator should follow in order to successfully use a specific


public API or technology.


If the writer hands in that test without reading the project
requirements and specs, without talking to the developers, without
reviewing the code, without reviewing previous internal communications
about the product, without testing the product hands-on, without
talking to the business SMEs, without researching the customers, the
industry, and target audience - I'd say the writer has failed the test.

Mike O.



__________________________________ Do you Yahoo!? Yahoo! Mail - Easier than ever with enhanced search. Learn more.
http://info.mail.yahoo.com/mail_250



Mike,

During the interview, we explain and illustrate the internal communications, and describe what our products are and who their target users are (e.g. developers, service providers and system integrators).

By public API I meant an API known to almost all (Java) developers, e.g. a J2SE API by Sun Microsystems. It is not being developed or maintained by our company so I am not able to provide no code and requirements specifications to the applicant about this API.

However, I first introduce him or her with our user documentation and next give the applicant a reference source - a specification or a tutorial.

To some extent you are right, especially if the test is related to the company's products - some technical specifications should be provided to the applicant. Otherwise, testing may become useless.

It is a good idea to show the applicant what he or she is supposed to produce and what the other participants in the project lifecycle are.

Regarding the software requirement specifications, as long as the company has a good and controlled quality management system with all accompanying guidelines, there should be no problem in introducing the future technical writer into internal communications and documentation.

Best regards,
Iliana Kostova.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

WEBWORKS FINALDRAFT - EDIT AND REVIEW, REDEFINED
Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo:
http://www.webworks.com/techwr-l

Doc-To-Help 7.5 Professional: New version with new features, improved performance and reliability, plus much more! Download your free trial today at www.componentone.com/techwrlfeb.

---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.


Previous by Author: Re: Why don't more job interviews use writing tests?
Next by Author: Re: New TECHWR-L Poll - Minorities in TW Management
Previous by Thread: Re: Why don't more job interviews use writing tests?
Next by Thread: RE: Why don't more job interviews use writing tests?

[Top of Archive] | [Author Index (this month)] | [Thread Index (this month)]

What this post helpful? Share it with friends and colleagues:

Sponsored Ads