<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>McCoy Blog &#187; Twitter</title>
	<atom:link href="http://mccoy.co.uk/blog/category/twitter/feed/" rel="self" type="application/rss+xml" />
	<link>http://mccoy.co.uk/blog</link>
	<description></description>
	<lastBuildDate>Sun, 13 May 2012 04:20:34 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>How to advertise a job on twitter</title>
		<link>http://mccoy.co.uk/blog/2009/12/11/how-to-advertise-a-job-on-twitter/</link>
		<comments>http://mccoy.co.uk/blog/2009/12/11/how-to-advertise-a-job-on-twitter/#comments</comments>
		<pubDate>Fri, 11 Dec 2009 12:10:02 +0000</pubDate>
		<dc:creator>Rich</dc:creator>
				<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://mccoy.co.uk/blog/?p=226</guid>
		<description><![CDATA[Many folks are using Twitter to search for and advertise jobs, for some reason its mainly the American and Canadian markets, the others seem to be a little slow on the uptake. There are several things that folks looking to use Twitter to recruit can do to ensure that they attract the right candidates by [...]]]></description>
			<content:encoded><![CDATA[<p>Many folks are using Twitter to search for and advertise jobs, for some reason its mainly the American and Canadian markets, the others seem to be a little slow on the uptake.</p>
<p>There are several things that folks looking to use Twitter to recruit can do to ensure that they attract the right candidates by getting the right information out there.<span id="more-226"></span></p>
<ol>
<li>Include a broad commonly understood Job Title, not every one you want to reach will be following you, even if they are the chances are you may get lost in the chatter, interested parties will set up filters for this term like I do for &#8220;<em>Creative Director</em>&#8221; or &#8220;<em>Art Director&#8221;</em>;</li>
<li>If the role has a specific segment include that too, I wont specifically set up a filter to include the term &#8220;<em>Interactive</em>&#8221; but it will catch my eye as being relevant;</li>
<li>Its also helpful to include a term that indicates that it is a recruitment advertisement Krop do it well in that they preface the posting with <strong>JOB:</strong> but <strong>HIRE:</strong> or <strong>RECRUITING:</strong> are equally as good, although a bit longer and your better of saving those characters and keeping it short. Using these at the start of a post with filtering out the chatter, Caps are good, but I would hesitate about putting the job title in caps as well;</li>
<li>It is also useful to include the <em>location</em>, and if possible <em>who its for</em> and any <em>special requirements</em> such as if its an immediate start or if its in an unusual location if relocation assistance is included;</li>
<li>But the most infuriating omission is failing to <strong>include a next step</strong>, it is off no use to any one so simply state that Studio X is looking for a Creative Director without giving me a link to find out a little more and apply for the post.</li>
<h3>As a template for a job seeker friendly tweet I suggest the following:</h3>
<blockquote><p>JOB: Job Title, studio name, location, qualifying condition if applicable, <a href="http://www.webfellowforhire.com">http://www.webfellowforhire.com</a></p></blockquote>
<p><strong>Further suggestions, responses from recruiters, job offers, well wishers and general passers buy wanting to say hi are most welcome. </strong></ol>
]]></content:encoded>
			<wfw:commentRss>http://mccoy.co.uk/blog/2009/12/11/how-to-advertise-a-job-on-twitter/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

