<?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: You Speak: What SHOULD a Software Engineer&#8217;s Resume Look Like?</title>
	<atom:link href="http://www.engfers.com/2008/11/17/you-speak_what-should-a-software-engineer-resume-look-like/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.engfers.com/2008/11/17/you-speak_what-should-a-software-engineer-resume-look-like/</link>
	<description>» scrumptions blog &#038; code » nothing more, nothing less</description>
	<lastBuildDate>Tue, 16 Mar 2010 04:29:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: engfer</title>
		<link>http://www.engfers.com/2008/11/17/you-speak_what-should-a-software-engineer-resume-look-like/comment-page-1/#comment-935</link>
		<dc:creator>engfer</dc:creator>
		<pubDate>Fri, 21 Nov 2008 16:11:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.engfers.com/?p=960#comment-935</guid>
		<description>Great so far but we need more!</description>
		<content:encoded><![CDATA[<p>Great so far but we need more!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Stawarz</title>
		<link>http://www.engfers.com/2008/11/17/you-speak_what-should-a-software-engineer-resume-look-like/comment-page-1/#comment-881</link>
		<dc:creator>Scott Stawarz</dc:creator>
		<pubDate>Wed, 19 Nov 2008 05:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.engfers.com/?p=960#comment-881</guid>
		<description>Consider who the target market of the resume is.  

For example:  When submitting the resume to monster.com, careerbuilder.com, and/or other large companies.  Those websites are searched via Human Resource Professionals, Recruiters, or Hiring Managers.  Consequently, your resume should follow Search Engine Optimization rules.  What I mean by that, is if you want to be noticed for Ruby, Visual Studio.NET or whatever, you&#039;ve got to include those keywords in your resume.  Now, how you include them is a different story.  I&#039;ll get to in a second.

Now, when I am emailing a resume, dropping a resume off at a job fair, or snail mailing a resume, again there are different forms the resume can take and look depending on who the target recipient is.  For example, when I go to a job interview, I bring a clean quickly scannable, well-presented paper copy of my resume.  Often times, the job interviewer has a printed text copy that is difficult for them to find the information they need to ask me questions.  Also, by having a printed copy, you can highlight different things using color and other methods that you can not always do in an emailed resume.    

Now, How do you include the necessary keywords?  Again, i think it depends on experience and type of job you are applying for.  So, you have to vary your resume towards your target market.  I do think that a resume should tell your story(s).  It should tell me why I should hire you.  What value do I get from your hiring?  

So, if I am working for a large education institution, and they are creating a new learning management system, I&#039;d want to see you say how you&#039;re past projects and experience can help me solve my business problems.  If you&#039;ve built an LMS, you&#039;d add that to your resume in a concise fashion.  If you haven&#039;t built an LMS, but maybe you built components for a system that can be adapted, you&#039;ll convey that message in your resume and for that matter the cover letter.  

that&#039;s what I want to see.  At the same point, when I&#039;ve been a hiring manager, I am going to need to scan resumes quickly to weed out who is worthy for my interview time.  So, a resume that is personable can stand out from the rest.  Everyone has a story and a uniqueness to them.  I think a good resume should stay out of the way and let Human Uniqueness shine through.</description>
		<content:encoded><![CDATA[<p>Consider who the target market of the resume is.  </p>
<p>For example:  When submitting the resume to monster.com, careerbuilder.com, and/or other large companies.  Those websites are searched via Human Resource Professionals, Recruiters, or Hiring Managers.  Consequently, your resume should follow Search Engine Optimization rules.  What I mean by that, is if you want to be noticed for Ruby, Visual Studio.NET or whatever, you&#8217;ve got to include those keywords in your resume.  Now, how you include them is a different story.  I&#8217;ll get to in a second.</p>
<p>Now, when I am emailing a resume, dropping a resume off at a job fair, or snail mailing a resume, again there are different forms the resume can take and look depending on who the target recipient is.  For example, when I go to a job interview, I bring a clean quickly scannable, well-presented paper copy of my resume.  Often times, the job interviewer has a printed text copy that is difficult for them to find the information they need to ask me questions.  Also, by having a printed copy, you can highlight different things using color and other methods that you can not always do in an emailed resume.    </p>
<p>Now, How do you include the necessary keywords?  Again, i think it depends on experience and type of job you are applying for.  So, you have to vary your resume towards your target market.  I do think that a resume should tell your story(s).  It should tell me why I should hire you.  What value do I get from your hiring?  </p>
<p>So, if I am working for a large education institution, and they are creating a new learning management system, I&#8217;d want to see you say how you&#8217;re past projects and experience can help me solve my business problems.  If you&#8217;ve built an LMS, you&#8217;d add that to your resume in a concise fashion.  If you haven&#8217;t built an LMS, but maybe you built components for a system that can be adapted, you&#8217;ll convey that message in your resume and for that matter the cover letter.  </p>
<p>that&#8217;s what I want to see.  At the same point, when I&#8217;ve been a hiring manager, I am going to need to scan resumes quickly to weed out who is worthy for my interview time.  So, a resume that is personable can stand out from the rest.  Everyone has a story and a uniqueness to them.  I think a good resume should stay out of the way and let Human Uniqueness shine through.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.engfers.com/2008/11/17/you-speak_what-should-a-software-engineer-resume-look-like/comment-page-1/#comment-880</link>
		<dc:creator>John</dc:creator>
		<pubDate>Wed, 19 Nov 2008 02:24:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.engfers.com/?p=960#comment-880</guid>
		<description>A few thoughts:
Keep it short - I don&#039;t have time to sift through 4 pages of bullets.  I&#039;ve also found the best people have the shortest and simplest resumes. Over two pages and the success rate on our interviews goes down dramatically.
Don&#039;t include buzzwords and acronyms like SDLC, ESB, WSAD if you want a job at a tech startup. 
Include independent projects/open source work - I want hardcore geeks who actually ENJOY writing software - convince me that you are one of those people. And unless you wrote them, don&#039;t put MS DOS or Windows 95 on your resume!
Don&#039;t inflate your responsibilities on projects or level of expertise (expect to be asked detailed technical questions about anything you put on your resume).
As for format, I like LaTeX (it shows me that you&#039;re geeky and at least smart enough to figure out how to use something other than MS word).</description>
		<content:encoded><![CDATA[<p>A few thoughts:<br />
Keep it short &#8211; I don&#8217;t have time to sift through 4 pages of bullets.  I&#8217;ve also found the best people have the shortest and simplest resumes. Over two pages and the success rate on our interviews goes down dramatically.<br />
Don&#8217;t include buzzwords and acronyms like SDLC, ESB, WSAD if you want a job at a tech startup.<br />
Include independent projects/open source work &#8211; I want hardcore geeks who actually ENJOY writing software &#8211; convince me that you are one of those people. And unless you wrote them, don&#8217;t put MS DOS or Windows 95 on your resume!<br />
Don&#8217;t inflate your responsibilities on projects or level of expertise (expect to be asked detailed technical questions about anything you put on your resume).<br />
As for format, I like LaTeX (it shows me that you&#8217;re geeky and at least smart enough to figure out how to use something other than MS word).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: engfer</title>
		<link>http://www.engfers.com/2008/11/17/you-speak_what-should-a-software-engineer-resume-look-like/comment-page-1/#comment-870</link>
		<dc:creator>engfer</dc:creator>
		<pubDate>Mon, 17 Nov 2008 23:13:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.engfers.com/?p=960#comment-870</guid>
		<description>Stephan Schmidt recommended this article in a comment on a &lt;a href=&quot;http://www.engfers.com/2008/11/14/what-a-resume-should-not-look-like/#comment-869&quot; rel=&quot;nofollow&quot;&gt;previous post&lt;/a&gt;...

&#187; &lt;b&gt;&lt;a href=&quot;http://jobbank.com/action/ref/resume-writing-overview,10007&quot; rel=&quot;nofollow&quot;&gt;Resume Writing Overview&lt;/a&gt;&lt;/b&gt;</description>
		<content:encoded><![CDATA[<p>Stephan Schmidt recommended this article in a comment on a <a href="http://www.engfers.com/2008/11/14/what-a-resume-should-not-look-like/#comment-869" rel="nofollow">previous post</a>&#8230;</p>
<p>&raquo; <b><a href="http://jobbank.com/action/ref/resume-writing-overview,10007" rel="nofollow">Resume Writing Overview</a></b></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: engfer</title>
		<link>http://www.engfers.com/2008/11/17/you-speak_what-should-a-software-engineer-resume-look-like/comment-page-1/#comment-868</link>
		<dc:creator>engfer</dc:creator>
		<pubDate>Mon, 17 Nov 2008 22:38:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.engfers.com/?p=960#comment-868</guid>
		<description>Stephan Schmidt recommended this article in a comment on a &lt;a href=&quot;http://www.engfers.com/2008/11/14/what-a-resume-should-not-look-like/#comment-832&quot; rel=&quot;nofollow&quot;&gt;previous post&lt;/a&gt;...

&#187; &lt;b&gt;&lt;a href=&quot;http://www.joelonsoftware.com/articles/ResumeRead.html&quot; rel=&quot;nofollow&quot;&gt;Getting Your Resume Read&lt;/a&gt;&lt;/b&gt;</description>
		<content:encoded><![CDATA[<p>Stephan Schmidt recommended this article in a comment on a <a href="http://www.engfers.com/2008/11/14/what-a-resume-should-not-look-like/#comment-832" rel="nofollow">previous post</a>&#8230;</p>
<p>&raquo; <b><a href="http://www.joelonsoftware.com/articles/ResumeRead.html" rel="nofollow">Getting Your Resume Read</a></b></p>
]]></content:encoded>
	</item>
</channel>
</rss>
