<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: What Doc Managers Look for in a Résumé</title>
	<atom:link href="http://managingwriters.com/2009/03/04/what-doc-managers-look-for-in-a-resume/feed/" rel="self" type="application/rss+xml" />
	<link>http://managingwriters.com/2009/03/04/what-doc-managers-look-for-in-a-resume/</link>
	<description>A Real-World Guide to Managing Technical Documentation</description>
	<lastBuildDate>Tue, 25 Oct 2011 21:41:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Richard Hamilton</title>
		<link>http://managingwriters.com/2009/03/04/what-doc-managers-look-for-in-a-resume/#comment-79</link>
		<dc:creator>Richard Hamilton</dc:creator>
		<pubDate>Wed, 07 Oct 2009 17:03:14 +0000</pubDate>
		<guid isPermaLink="false">http://rlhamilton.wordpress.com/?p=153#comment-79</guid>
		<description>MM,

If I&#039;m evaluating the resume of someone who claims to be an expert in layout/design or in the particular tool the resume was written in, then I will look at those things. I will also in most cases consider the overall look of the resume; after all, it&#039;s easy to get an acceptable look from any word processor, so there&#039;s no excuse for having a truly ugly resume. 

At the same time, for writers, I&#039;m much more interested in the structure and writing. Chance are they will be using a corporate style guide that will make any design skills moot. Yes, if the resume was written using the tool that person will need to use on the job, I may dive deeper, but that will only happen for candidates I&#039;m serious about interviewing.

Regarding the second part, I do expect technical writers to use styles and clean formatting when using tools that allow it. Most of my recent teams have used XML, so I&#039;m more concerned about good semantic markup. But for a job that uses Word or asimilar word processor, I expect them to use the styles and formatting defined by whatever style guide we are using.

All that said, if you can&#039;t write, I don&#039;t care how well you format, I&#039;m not interested.</description>
		<content:encoded><![CDATA[<p>MM,</p>
<p>If I&#8217;m evaluating the resume of someone who claims to be an expert in layout/design or in the particular tool the resume was written in, then I will look at those things. I will also in most cases consider the overall look of the resume; after all, it&#8217;s easy to get an acceptable look from any word processor, so there&#8217;s no excuse for having a truly ugly resume. </p>
<p>At the same time, for writers, I&#8217;m much more interested in the structure and writing. Chance are they will be using a corporate style guide that will make any design skills moot. Yes, if the resume was written using the tool that person will need to use on the job, I may dive deeper, but that will only happen for candidates I&#8217;m serious about interviewing.</p>
<p>Regarding the second part, I do expect technical writers to use styles and clean formatting when using tools that allow it. Most of my recent teams have used XML, so I&#8217;m more concerned about good semantic markup. But for a job that uses Word or asimilar word processor, I expect them to use the styles and formatting defined by whatever style guide we are using.</p>
<p>All that said, if you can&#8217;t write, I don&#8217;t care how well you format, I&#8217;m not interested.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MM</title>
		<link>http://managingwriters.com/2009/03/04/what-doc-managers-look-for-in-a-resume/#comment-78</link>
		<dc:creator>MM</dc:creator>
		<pubDate>Mon, 05 Oct 2009 21:49:02 +0000</pubDate>
		<guid isPermaLink="false">http://rlhamilton.wordpress.com/?p=153#comment-78</guid>
		<description>I&#039;m curious about how closely you look at resumes in terms of formatting. Specifically I&#039;m thinking about the use or not of Styles, extra paragraph breaks, use of spaces when tabs would be cleaner... Do you expect technical writers to use Styles and clean formatting? Do you turn on hidden characters to check, or do you think this stuff is unimportant (ie. I&#039;m being overly fussy)?</description>
		<content:encoded><![CDATA[<p>I&#8217;m curious about how closely you look at resumes in terms of formatting. Specifically I&#8217;m thinking about the use or not of Styles, extra paragraph breaks, use of spaces when tabs would be cleaner&#8230; Do you expect technical writers to use Styles and clean formatting? Do you turn on hidden characters to check, or do you think this stuff is unimportant (ie. I&#8217;m being overly fussy)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jenny</title>
		<link>http://managingwriters.com/2009/03/04/what-doc-managers-look-for-in-a-resume/#comment-75</link>
		<dc:creator>Jenny</dc:creator>
		<pubDate>Fri, 06 Mar 2009 16:27:03 +0000</pubDate>
		<guid isPermaLink="false">http://rlhamilton.wordpress.com/?p=153#comment-75</guid>
		<description>Thanks for your response. That&#039;s really interesting! Having worked in XML myself, I think that the use of Styles and clean formatting is a good indication of whether a writer could work well in a structured environment. Great post, thanks!</description>
		<content:encoded><![CDATA[<p>Thanks for your response. That&#8217;s really interesting! Having worked in XML myself, I think that the use of Styles and clean formatting is a good indication of whether a writer could work well in a structured environment. Great post, thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rlhamilton</title>
		<link>http://managingwriters.com/2009/03/04/what-doc-managers-look-for-in-a-resume/#comment-77</link>
		<dc:creator>rlhamilton</dc:creator>
		<pubDate>Fri, 06 Mar 2009 15:05:50 +0000</pubDate>
		<guid isPermaLink="false">http://rlhamilton.wordpress.com/?p=153#comment-77</guid>
		<description>I do expect technical writers to use styles and clean formatting, but to tell the truth, I haven&#039;t applied that expectation to resumes. That&#039;s partly neglect, but also a result of having seen many more resumes in hard-copy or pdf form, rather than Word or some similar form.

Also, almost all of my recent hires (last 5 years or so) have been to write XML, so I&#039;m more interested in good use of XML.

That said, if I were hiring someone who claimed to be an expert in the same word processor that his or her resume was written it, I would want to look and would not consider that overly fussy.</description>
		<content:encoded><![CDATA[<p>I do expect technical writers to use styles and clean formatting, but to tell the truth, I haven&#8217;t applied that expectation to resumes. That&#8217;s partly neglect, but also a result of having seen many more resumes in hard-copy or pdf form, rather than Word or some similar form.</p>
<p>Also, almost all of my recent hires (last 5 years or so) have been to write XML, so I&#8217;m more interested in good use of XML.</p>
<p>That said, if I were hiring someone who claimed to be an expert in the same word processor that his or her resume was written it, I would want to look and would not consider that overly fussy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jenny</title>
		<link>http://managingwriters.com/2009/03/04/what-doc-managers-look-for-in-a-resume/#comment-76</link>
		<dc:creator>Jenny</dc:creator>
		<pubDate>Fri, 06 Mar 2009 06:46:21 +0000</pubDate>
		<guid isPermaLink="false">http://rlhamilton.wordpress.com/?p=153#comment-76</guid>
		<description>I&#039;m curious about how closely you look at resumes in terms of formatting. Specifically I&#039;m thinking about the use or not of Styles, extra paragraph breaks, use of spaces when tabs would be cleaner... Do you expect technical writers to use Styles and clean formatting? Do you turn on hidden characters to check, or do you think this stuff is unimportant (ie. I&#039;m being overly fussy)?</description>
		<content:encoded><![CDATA[<p>I&#8217;m curious about how closely you look at resumes in terms of formatting. Specifically I&#8217;m thinking about the use or not of Styles, extra paragraph breaks, use of spaces when tabs would be cleaner&#8230; Do you expect technical writers to use Styles and clean formatting? Do you turn on hidden characters to check, or do you think this stuff is unimportant (ie. I&#8217;m being overly fussy)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alistair Christie</title>
		<link>http://managingwriters.com/2009/03/04/what-doc-managers-look-for-in-a-resume/#comment-74</link>
		<dc:creator>Alistair Christie</dc:creator>
		<pubDate>Thu, 05 Mar 2009 16:29:24 +0000</pubDate>
		<guid isPermaLink="false">http://rlhamilton.wordpress.com/?p=153#comment-74</guid>
		<description>A very useful article, thanks. We&#039;re hiring right now, so I&#039;ve been reading lots of resumes recently.

It never ceases to amaze me the number of resumes (&quot;CVs&quot; to us Brits) that are full of careless mistakes. I got one recently where the writer claimed to have &quot;an obsessive eye for detail&quot; and then made a spelling mistake in the very next sentence.

I can forgive some grammatical errors and bad judgement in layout/organisation, but I find it very hard to see past simple spelling mistakes in the CV of someone who is trying to get a job as a technical writer.</description>
		<content:encoded><![CDATA[<p>A very useful article, thanks. We&#8217;re hiring right now, so I&#8217;ve been reading lots of resumes recently.</p>
<p>It never ceases to amaze me the number of resumes (&#8220;CVs&#8221; to us Brits) that are full of careless mistakes. I got one recently where the writer claimed to have &#8220;an obsessive eye for detail&#8221; and then made a spelling mistake in the very next sentence.</p>
<p>I can forgive some grammatical errors and bad judgement in layout/organisation, but I find it very hard to see past simple spelling mistakes in the CV of someone who is trying to get a job as a technical writer.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

