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

Subject: RE: Why they don't ask for candidates by technology skills.
From: Samuel -dot- Beard -at- tdcj -dot- state -dot- tx -dot- us
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Wed, 19 Feb 2003 12:54:29 -0600



Hey John,




John Posada
<JPosada -at- book -dot- com> To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Sent by: cc: TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com>
bounce-techwr-l-117504 -at- lists -dot- Subject: RE: Why they don't ask for candidates by technology skills.
raycomm.com


02/19/03 12:12 PM
Please respond to John Posada

ID Number:





>>John wrote:
If a document is classified as ....classified, then you are right. However,
the point would be moot because as a classified document (in the true
definition of the term), the controls involved in creating it preclude you
even having a copy with which to be tempted.

>> I reply:

Exactly my point! At the least, most of those documents were classified
as "Confidential", with most of those much higher levels. Pretty difficult
to legally have anything even remotely close to being from those documents
to show as a writing sample!

>> John continued:
OTOH, IMHO, proprietary...that's more grayscale. My position has been that
if the document contains information that can be garnered by other means
and
as long as you don't use the document from one industry in an interview
with
a company of the same industry, and wherever you are showing it, you don't
leave a copy and don't allow note taking or photocopying, then nobody is
going to ding you.

>> I reply again:

Well, I guess that here it's the standard answer: it depends. Most of
that work was for products that were under development and not yet
released. Example: a telecommunications company working on a new product,
in one case, and a fiber optics company working on new equipment and
technologies in the fiber optics industry, in the other. Both cases, I
wasn't allowed to remove any of the proprietary documentation to use as
samples, even though they weren't "classified".

Any tips on getting around such problems? Short of the standard "Write a
user's manual for something" approach, that is. They would be MOST
appreciated as with the current state of budget shortfalls in the Texas
state budget, I might find myself once again looking for gainful
employment! Hopefully, that won't happen, but one never knows when bean
counters are involved!

Sam Beard








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

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.



Previous by Author: RE: Why they don't ask for candidates by technology skills.
Next by Author: RE: Why they don't ask for candidates by technology skills.
Previous by Thread: RE: Why they don't ask for candidates by technology skills.
Next by Thread: RE: Why they don't ask for candidates by technology skills.


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


Sponsored Ads