Writing Test

[Mary Arrotti]

Well - I'm going to assume if I were taking this test, I'd know whether the job I interviewed for involved documenting software or not and - in general - who the audience was (description included writing requirements vs. product help). 
   
  So, if I were interviewing for a software company & the job description focused on user docs - I'd probably write something like this. Depending upon whether I had time or not, I might expand this or wordsmith it a bit. It's about 92 words now. 
   
   
  By providing clear, concise, and accurate information, a good documentation package should enable users to successfully work with the product. There are required tasks that users must perform or understand in order to be successful. Some of these tasks and examples of corresponding documentation are as follows:
  * Understand new features or changes to product (e.g., release notes, What’s New)
  * Install the product (e.g. installation guide, tutorials)
  * Set up and configure the product (e.g., Help, installation guides, admin guides)
  * Use features within the product (e.g., Help, user guides, tutorials)
  
James Barrow <vrfour at verizon.net> wrote:
  It's a good thing we recently discussed writing tests as part of an
interview, because I had one today. I don't want to tell you what my
concerns were about this test because I don't want to influence you. So
take a look at what I was given and let me know what you would have said.
I'll tell you how I answered in my next post. Here's the test:

"In one paragraph (100 words or less) describe what should be included in a
good documentation package, and explain why it would be good."



 
---------------------------------
Need a quick answer? Get one in minutes from people who know. Ask your question on Yahoo! Answers.