Comments on: Q & A: What Should I Put on My Programming Resume? http://www.softwarebyrob.com/2008/03/27/q-a-what-should-i-put-on-my-programming-resume/ Passionate about Startups and MicroISVs Wed, 08 Sep 2010 21:26:08 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: links for 2008-03-29 « D e j a m e S e r http://www.softwarebyrob.com/2008/03/27/q-a-what-should-i-put-on-my-programming-resume/comment-page-1/#comment-3488 links for 2008-03-29 « D e j a m e S e r Sat, 29 Mar 2008 15:32:45 +0000 http://www.softwarebyrob.com/2008/03/27/q-a-what-should-i-put-on-my-programming-resume/#comment-3488 [...] Q & A: What Should I Put on My Programming Resume? | Software by Rob (tags: career development) [...] [...] Q & A: What Should I Put on My Programming Resume? | Software by Rob (tags: career development) [...]

]]> By: Jim Bonnie http://www.softwarebyrob.com/2008/03/27/q-a-what-should-i-put-on-my-programming-resume/comment-page-1/#comment-3479 Jim Bonnie Fri, 28 Mar 2008 10:15:38 +0000 http://www.softwarebyrob.com/2008/03/27/q-a-what-should-i-put-on-my-programming-resume/#comment-3479 I agree that you need to research the company that you are interviewing with. First to understand their line of business and second to assess the type of technical shop it is. I am currently looking for a place that has better practices to learn from. Unit Testing, TDD, code Coverage, etc. are foreign concepts to many, and I am finding it difficult to introduce these as a newbie myself.I geuss that is where the apprecenticeships and home projects can help. Cool to see that you are in New Haven. I am in Trumbell right now. I agree that you need to research the company that you are interviewing with. First to understand their line of business and second to assess the type of technical shop it is. I am currently looking for a place that has better practices to learn from. Unit Testing, TDD, code Coverage, etc. are foreign concepts to many, and I am finding it difficult to introduce these as a newbie myself.I geuss that is where the apprecenticeships and home projects can help. Cool to see that you are in New Haven. I am in Trumbell right now.

]]> By: JohnE http://www.softwarebyrob.com/2008/03/27/q-a-what-should-i-put-on-my-programming-resume/comment-page-1/#comment-3477 JohnE Fri, 28 Mar 2008 04:31:10 +0000 http://www.softwarebyrob.com/2008/03/27/q-a-what-should-i-put-on-my-programming-resume/#comment-3477 I have been in development for 20 years now and work for http://www.jobbank.com at the moment which has given me some insight into what to look for. More importantly, I have been a primary interviewer for companies in the past. The resume is important. If done with thought, it gets you in the door. Try to show experience more then just having the ability to do basic web. EVERYBODy does basic web development, even those just coming out of college. You need to differentiate yourself. If you do get in through the front door to the interview, a next thing I look for is: "Why have you chosen to interview with this company." You would be surprised at how many people go to an interview with no concept of why. They have nothing to offer or no particular interest. They just want a job. If a person comes through the door and says they are excited to work for this company because of these reasons.... I listen harder. If they look like they can socially interact, I listen harder. Note that the technical aspect is only one piece, but if the other parts are not there, they do not matter. I hope this helps! I have been in development for 20 years now and work for http://www.jobbank.com at the moment which has given me some insight into what to look for.

More importantly, I have been a primary interviewer for companies in the past.

The resume is important. If done with thought, it gets you in the door. Try to show experience more then just having the ability to do basic web. EVERYBODy does basic web development, even those just coming out of college. You need to differentiate yourself.

If you do get in through the front door to the interview, a next thing I look for is: “Why have you chosen to interview with this company.” You would be surprised at how many people go to an interview with no concept of why. They have nothing to offer or no particular interest. They just want a job.

If a person comes through the door and says they are excited to work for this company because of these reasons…. I listen harder. If they look like they can socially interact, I listen harder. Note that the technical aspect is only one piece, but if the other parts are not there, they do not matter.

I hope this helps!

]]>