RE: Why they don't ask for candidates by technology skills.

[John Posada <JPosada -at- book -dot- com>]

>When I hire someone, my number one requirement is that the person is a
quick
>study. That skill, however, is very difficult to ascertain in an interview.

Is it?

Look at the person's portfolio and the resume. If the resume is full of
relatively short gigs of 6 months to a year, and the portfolio covers a wide
range of subjects that aren't related to each other, yet require technical
understanding, then chances are the person can pick stuff up at a decent
speed. 

OTOH, if the portfolio has only users guides or help files, then it would be
taking a chance to throw programmer documentation at them and vice versa.

John Posada

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
Buy or upgrade to RoboHelp X3 today and receive the WebHelp
Merge Module for FREE ($299 value). RoboHelp X3's all-new
features include conditional text, completely re-engineered
printed documentation output, Context-sensitive Help Toolkit,
single-source layouts, and more!
Order online today at http://www.ehelp.com/techwr-l


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