<p>Hi CC:</p>
<p>I was wondering what your thoughts are on posting Software Projects on a resume, would it be better to post them all on a personal web page, and have the link on the resume? Is having Software projects on a resume a bit tacky?</p>
<p>I look forward to your thoughts!</p>
<p>Software projects on a resume are not tacky at all. All of the companies I’ve interviewed with love seeing software projects on resumes. By doing projects on your own, you show that you have an interest in software outside of class, and that you have the motivation to complete a project by yourself.</p>
<p>Your resume will have 15-20 seconds before it is either trashed or put aside for further investigation. Given this, here is my suggested course of action:</p>
<p>1) Put a section on your resume devoted to your most interesting/impressive projects. This section has close to the same importance level as “Education” and “Work Experience”, and should probably be put immediately after them.</p>
<p>2) Upload as many projects as possible to GitHub and then put a link to that on your resume. Including your personal website is nice, but a link to GitHub will immediately make it clear that you have some projects available to look at.</p>
<p>Hi Sumzup, </p>
<p>As of now, I have my personal projects listed on my resume, 3 of them to be precise, and I recently created myself a personal webpage. Should I also post a link to my personal web page, and my github account?</p>
<p>May I possibly PM you my resume? So you may constructively criticize it, if need be? The reason for this is because most of my peers that ended up at Google, Microsoft did NOT have projects listed, instead they had a link to their personal websites, despite them completing the same rigorous projects. In almost every 300-level course, 70 percent of the final grade are projects, so I’ll have so many projects by the time I graduate. Given this, I figured a personal link to my web page might draw more attention?</p>
<p>Thank you for your feedback Sumzup, I look forward to your response.</p>
<p>Anyone else, please chime in!</p>
<p>Posting links to both a personal web page and GitHub is fine. To be honest, I have neither on my own resume, and I have been called back for interviews at several top companies (while including a projects section). But it’s definitely something I should improve.</p>
<p>Beyond the whole “glance at resume for 20 seconds” reason for putting projects on a resume, I think another important reason is that there’s nothing else much better. Let’s say that education and work experience take up half of a resume. What do you put in the remaining half? Course lists are out- interviewers and recruiters have told me that they don’t care as much about these. A skills section could be nice, but it’s better to say “I worked on X project using Python and Django” instead of “I know Python and Django”. You can still have that skills section, but it’s nice to know where you applied those skills. I suppose the last potentially useful section would be awards/honors, but this shouldn’t take up more than a few lines.</p>
<p>A projects section can also help out somewhat for interviews as talking points. An interviewer can say “tell me about Project A” and you can immediately jump into why A was so cool and what you learned during it. Questions like “tell me about a time where you struggled with team members and then overcame your issues” could lead into you saying, “Well, in project B on my resume…”.</p>
<p>Anyways, I’d be happy to check out your resume (although it might take a day or two for me to get back to you).</p>