<?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: Five Tips for Interviewing</title>
	<atom:link href="http://devin.reams.me/five-tips-for-interviewing/feed/" rel="self" type="application/rss+xml" />
	<link>http://devin.reams.me/five-tips-for-interviewing/</link>
	<description>Thoughts on life, business, and technology.</description>
	<lastBuildDate>Sat, 13 Mar 2010 15:32:36 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nicole</title>
		<link>http://devin.reams.me/five-tips-for-interviewing/comment-page-1/#comment-684</link>
		<dc:creator>Nicole</dc:creator>
		<pubDate>Thu, 12 Oct 2006 04:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://devinreams.com/2006/10/06/five-tips-for-interviewing/#comment-684</guid>
		<description>The questions you note like what the position entails or how soon you&#039;ll be able to participate in new projects are all good ones.  I also like the &quot;If I were hired, what might be some of the first projects on my plate?&quot; question.

This may all seem obvious, but it&#039;s amazing how many candidates ask NO questions.  When a candidate doesn&#039;t ask questions, I assume (correctly or incorrectly) that either a) they&#039;re not interested enough or b) they&#039;re not prepared.  Also, it&#039;s always good to come armed with a few questions because sometimes good questions you have are answered during the course of the interview. But, of course, you still want to have *something* to ask.

I&#039;ve also noticed in interviews that a lot of women (myself included) have the hardest time relaying how qualified they are.  Perhaps we feel it&#039;s unbecoming to say &quot;Hey, I&#039;m pretty damn good at what I do.&quot;  But -- we have to stifle our natural inclination to be modest.  An interview is NOT the time to be modest.</description>
		<content:encoded><![CDATA[<p>The questions you note like what the position entails or how soon you&#8217;ll be able to participate in new projects are all good ones.  I also like the &#8220;If I were hired, what might be some of the first projects on my plate?&#8221; question.</p>
<p>This may all seem obvious, but it&#8217;s amazing how many candidates ask NO questions.  When a candidate doesn&#8217;t ask questions, I assume (correctly or incorrectly) that either a) they&#8217;re not interested enough or b) they&#8217;re not prepared.  Also, it&#8217;s always good to come armed with a few questions because sometimes good questions you have are answered during the course of the interview. But, of course, you still want to have *something* to ask.</p>
<p>I&#8217;ve also noticed in interviews that a lot of women (myself included) have the hardest time relaying how qualified they are.  Perhaps we feel it&#8217;s unbecoming to say &#8220;Hey, I&#8217;m pretty damn good at what I do.&#8221;  But &#8212; we have to stifle our natural inclination to be modest.  An interview is NOT the time to be modest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Devin Reams</title>
		<link>http://devin.reams.me/five-tips-for-interviewing/comment-page-1/#comment-683</link>
		<dc:creator>Devin Reams</dc:creator>
		<pubDate>Mon, 09 Oct 2006 20:01:25 +0000</pubDate>
		<guid isPermaLink="false">http://devinreams.com/2006/10/06/five-tips-for-interviewing/#comment-683</guid>
		<description>Good tips, Nicole. I think the specifics is definitely important when selling yourself (definitely use it in resumes, too).

What are good questions interviewee&#039;s have asked you? Typically I like to ask about what the position entails, or how soon I&#039;ll be able to participate in new projects, things along that line. I&#039;m also keen on asking them about their day-to-day routine, what kind of activities the office may do outside of regular hours (hikes?). Anything else to add?</description>
		<content:encoded><![CDATA[<p>Good tips, Nicole. I think the specifics is definitely important when selling yourself (definitely use it in resumes, too).</p>
<p>What are good questions interviewee&#8217;s have asked you? Typically I like to ask about what the position entails, or how soon I&#8217;ll be able to participate in new projects, things along that line. I&#8217;m also keen on asking them about their day-to-day routine, what kind of activities the office may do outside of regular hours (hikes?). Anything else to add?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicole</title>
		<link>http://devin.reams.me/five-tips-for-interviewing/comment-page-1/#comment-682</link>
		<dc:creator>Nicole</dc:creator>
		<pubDate>Mon, 09 Oct 2006 19:58:17 +0000</pubDate>
		<guid isPermaLink="false">http://devinreams.com/2006/10/06/five-tips-for-interviewing/#comment-682</guid>
		<description>&lt;blockquote&gt;3. Always Use Specifics&lt;/blockquote&gt;

After sitting on interview committees for a couple positions, I decided this is my one most important rule of interviewing.  Don&#039;t make me read between the lines!  I don&#039;t want to hire someone if we have to conjecture in our committee meeting about what the person was really saying.

Committee member X: &quot;Well, Candidate A said he had a big part in the design of this webpage.  But does that mean, he did just the design or did he translate the design into code as well?  Did he do that nice design element on the side?&quot;

Committee member Y: &quot;Shall we take the pessimistic or optimistic route on this one?&quot;

Committee member Nicole: &quot;Why should we conjecture about Candidate A when Candidate B clearly laid out his experience and used specific examples?&quot;

Secondarily, I&#039;d say preparedness is another important one.  Being overly prepared is much better than under prepared.  An interview is the time to be an overachiever.  Not sure if you should create and bring a portfolio piece? Bring it!  Research common interview questions in your field and be prepared to answer them.

Also, *always* have at least one question for the interviewer(s).  It shows you care and, again, speaks to one&#039;s preparedness.</description>
		<content:encoded><![CDATA[<blockquote><p>3. Always Use Specifics</p></blockquote>
<p>After sitting on interview committees for a couple positions, I decided this is my one most important rule of interviewing.  Don&#8217;t make me read between the lines!  I don&#8217;t want to hire someone if we have to conjecture in our committee meeting about what the person was really saying.</p>
<p>Committee member X: &#8220;Well, Candidate A said he had a big part in the design of this webpage.  But does that mean, he did just the design or did he translate the design into code as well?  Did he do that nice design element on the side?&#8221;</p>
<p>Committee member Y: &#8220;Shall we take the pessimistic or optimistic route on this one?&#8221;</p>
<p>Committee member Nicole: &#8220;Why should we conjecture about Candidate A when Candidate B clearly laid out his experience and used specific examples?&#8221;</p>
<p>Secondarily, I&#8217;d say preparedness is another important one.  Being overly prepared is much better than under prepared.  An interview is the time to be an overachiever.  Not sure if you should create and bring a portfolio piece? Bring it!  Research common interview questions in your field and be prepared to answer them.</p>
<p>Also, *always* have at least one question for the interviewer(s).  It shows you care and, again, speaks to one&#8217;s preparedness.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Devin</title>
		<link>http://devin.reams.me/five-tips-for-interviewing/comment-page-1/#comment-681</link>
		<dc:creator>Devin</dc:creator>
		<pubDate>Sun, 08 Oct 2006 19:57:05 +0000</pubDate>
		<guid isPermaLink="false">http://devinreams.com/2006/10/06/five-tips-for-interviewing/#comment-681</guid>
		<description>Well, it seems obvious in hindsight. But. before going in this might not all seem so obvious. You just know an interview is going to ask you questions, right? I know my first ones weren&#039;t great. Heck, I don&#039;t know if they were even good.</description>
		<content:encoded><![CDATA[<p>Well, it seems obvious in hindsight. But. before going in this might not all seem so obvious. You just know an interview is going to ask you questions, right? I know my first ones weren&#8217;t great. Heck, I don&#8217;t know if they were even good.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pearce</title>
		<link>http://devin.reams.me/five-tips-for-interviewing/comment-page-1/#comment-680</link>
		<dc:creator>Pearce</dc:creator>
		<pubDate>Sat, 07 Oct 2006 11:47:44 +0000</pubDate>
		<guid isPermaLink="false">http://devinreams.com/2006/10/06/five-tips-for-interviewing/#comment-680</guid>
		<description>You&#039;ve got really good point there - but you&#039;d think most of them would come obvious to most people, wouldn&#039;t you? Kind of... I dunno, strange, how they don&#039;t come naturally to so many people.</description>
		<content:encoded><![CDATA[<p>You&#8217;ve got really good point there &#8211; but you&#8217;d think most of them would come obvious to most people, wouldn&#8217;t you? Kind of&#8230; I dunno, strange, how they don&#8217;t come naturally to so many people.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
