<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "http://docs.oasis-open.org/dita/v1.1/CD01/dtd/topic.dtd">
<?xml-stylesheet type="text/css" href="http://tc.eserver.org/css/dita-view.css"?>

<topic id="tc22026">
<title>Tech Writer Skills</title>
<shortdesc>A college degree in English, journalism, fine arts, or even technical communication does not a technical writer make. That may not seem to ring true, but spending any time at all out there in the field will quickly demonstrate the veracity of the statement. A degree is probably of greatest benefit in gaining access for an interview, and, later, in negotiating salary or bill rate although other factors will be operative in this area too. In my experience, it seems some of the truly talented technical writers I&apos;ve encountered come from the engineering and marketing fields, and there have been a few &apos;re-engineered&apos; programmers that made the transition too. The key rests in an ability to explain technical material and processes in a concise, descriptive way, using non-technical language and eliminating the jargon. I think it&apos;s important to have a special interest or skill in writing, enjoy the writing process. Being a good wordsmith and editor certainly helps too, as does a strong vocabulary.</shortdesc>
<body>
<p>A college degree in English, journalism, fine arts, or even technical communication does not a technical writer make. That may not seem to ring true, but spending any time at all out there in the field will quickly demonstrate the veracity of the statement. A degree is probably of greatest benefit in gaining access for an interview, and, later, in negotiating salary or bill rate although other factors will be operative in this area too. In my experience, it seems some of the truly talented technical writers I&apos;ve encountered come from the engineering and marketing fields, and there have been a few &apos;re-engineered&apos; programmers that made the transition too. The key rests in an ability to explain technical material and processes in a concise, descriptive way, using non-technical language and eliminating the jargon. I think it&apos;s important to have a special interest or skill in writing, enjoy the writing process. Being a good wordsmith and editor certainly helps too, as does a strong vocabulary.</p>
<ul>
<li><a href="http://tc.eserver.org/dir/Careers/Writing/Technical-Writing">All works in 'Careers &gt; Writing &gt; Technical-Writing'</a></li>
<li><a href="http://tc.eserver.org/dir/Careers">All works in 'Careers'</a>, <a href="http://tc.eserver.org/dir/Writing">'Writing'</a>, <a href="http://tc.eserver.org/dir/Technical-Writing">'Technical Writing'</a></li>
</ul>
</body>
<related-links format="html" scope="local">
 <link type="reference" href="http://tc.eserver.org/dir/Careers/Writing/Technical-Writing" role="parent" scope="local"><linktext>All works in 'Careers &gt; Writing &gt; Technical-Writing'</linktext></link>
 <link type="reference" href="http://tc.eserver.org/dir/Careers" role="parent" scope="local"><linktext>All works in 'Careers'</linktext></link>
 <link type="reference" href="http://tc.eserver.org/dir/Writing" role="parent" scope="local"><linktext>All works in 'Writing'</linktext></link>
 <link type="reference" href="http://tc.eserver.org/dir/Technical-Writing" role="parent" scope="local"><linktext>All works in 'Technical Writing'</linktext></link>
 <link type="reference" href="http://tc.eserver.org/publisher/Tech-Writer" role="parent" scope="local"><linktext>All 32 works published by Tech-Writer</linktext></link>
</related-links>
</topic>