Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My brother has come up with an interesting business idea that could be commercialised. For over a month I have been creating the foundation for SaaS. I have been treating this as commercial project so designing using patterns and best practices.

One of the reasons I want to include this in my Resume is my full time job doesn't involve current trendy ASP.Net technologies (e.g Linq/Entity Relationships, jQuery, ASP.Net MVC 3, Silverlight, etc) so the resume lacks impact. In my full time job I work on a 7 year old well designed product and since our data and web layers work well it would be stupid to re-engineer them only because recruiters think Linq, ASP.Net MVC and jQuery are cool.

How can I include my personal project in Resume so that it doesn't sound like experiment or quick'n'dirty pet project?

share|improve this question

closed as off-topic by Snowman, Bart van Ingen Schenau, MichaelT, Kilian Foth, durron597 Apr 7 '15 at 13:06

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions seeking career or education advice are off topic on Programmers. They are only meaningful to the asker and do not generate lasting value for the broader programming community. Furthermore, in most cases, any answer is going to be a subjective opinion that may not take into account all the nuances of a (your) particular circumstance." – Snowman, Bart van Ingen Schenau, Community, Kilian Foth, durron597
If this question can be reworded to fit the rules in the help center, please edit the question.

Same way you include anything else on your resume? Explain the project and put up a demo if you can? – Aaronaught Jun 26 '11 at 3:02
up vote 15 down vote accepted

What's so bad about an experiment? I love resumes that demonstrate the candidate is actively experimenting. As far as quick 'n dirty, you'll prove it isn't by continuing to work on it. Take it from a great idea to a great product. Polish, polish, polish. You can show it's not amateurish by, well, not acting like an amateur. Take the project seriously and you'll be fine. Specific ideas:

  • Include it with your other experience (after you've worked on it for more than a month). Many people list simultaneous jobs on their resume, especially if they're consultants. Consider it the start of your own new business.
  • Include a link to your github or bitbucket repositories. This allows the curious to see the project as a living and growing thing. They'll notice your perseverance and professionalism.
  • Add a "personal passions" block to your resume. Talk about your project. Explain why it's important. Show that you're not including it because the technologies are "trendy". Show that you're including it because you believe in it and believe the technologies are powerful and better than the alternatives.
share|improve this answer
Nothing bad about experiment per say. I just thought hiring managers would not take it serious. – mob1lejunkie Jun 26 '11 at 3:39
By including it as part of your resume it will show you have a passion for programming that extends outside of work – Dave Mess Jun 26 '11 at 21:39

Not the answer you're looking for? Browse other questions tagged or ask your own question.