Mixing
Adding hobby projects to resume?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
4
down vote
favorite
I'm a developer (edit: I should clarify I also do SysAdmin, game design, etc) and hobby projects are a huge part of the industry. Should I add my hobby projects to my resume, and if so how do I format/word it?
For example, I've:
- Running and developing a MUD for 10+ years
- Contributed code to reddit
- Run my own LAMP server for specific users
- Developed a Spiceworks plugin
And if I'm to list these, am I expected to link to the project? For example, the MUD is based on an existing IP I don't have rights to so I get dubious in that regard. (I don't make money off it)
resume
asked Jul 2 '14 at 22:01
Zeno
1486
suggest improvements |Â
up vote
4
down vote
favorite
I'm a developer (edit: I should clarify I also do SysAdmin, game design, etc) and hobby projects are a huge part of the industry. Should I add my hobby projects to my resume, and if so how do I format/word it?
For example, I've:
- Running and developing a MUD for 10+ years
- Contributed code to reddit
- Run my own LAMP server for specific users
- Developed a Spiceworks plugin
And if I'm to list these, am I expected to link to the project? For example, the MUD is based on an existing IP I don't have rights to so I get dubious in that regard. (I don't make money off it)
resume
asked Jul 2 '14 at 22:01
Zeno
1486
possible duplicate of How do I mention my spare time projects in resume?
– gnat
Jul 3 '14 at 7:30
suggest improvements |Â
up vote
4
down vote
favorite
up vote
4
down vote
favorite
I'm a developer (edit: I should clarify I also do SysAdmin, game design, etc) and hobby projects are a huge part of the industry. Should I add my hobby projects to my resume, and if so how do I format/word it?
For example, I've:
- Running and developing a MUD for 10+ years
- Contributed code to reddit
- Run my own LAMP server for specific users
- Developed a Spiceworks plugin
And if I'm to list these, am I expected to link to the project? For example, the MUD is based on an existing IP I don't have rights to so I get dubious in that regard. (I don't make money off it)
resume
asked Jul 2 '14 at 22:01
Zeno
1486
I'm a developer (edit: I should clarify I also do SysAdmin, game design, etc) and hobby projects are a huge part of the industry. Should I add my hobby projects to my resume, and if so how do I format/word it?
For example, I've:
- Running and developing a MUD for 10+ years
- Contributed code to reddit
- Run my own LAMP server for specific users
- Developed a Spiceworks plugin
And if I'm to list these, am I expected to link to the project? For example, the MUD is based on an existing IP I don't have rights to so I get dubious in that regard. (I don't make money off it)
resume
asked Jul 2 '14 at 22:01
Zeno
1486
edited Jul 2 '14 at 23:54
asked Jul 2 '14 at 22:01
Zeno
1486
asked Jul 2 '14 at 22:01
Zeno
1486
asked Jul 2 '14 at 22:01
Zeno
1486
1486
possible duplicate of How do I mention my spare time projects in resume?
– gnat
Jul 3 '14 at 7:30
suggest improvements |Â
possible duplicate of How do I mention my spare time projects in resume?
– gnat
Jul 3 '14 at 7:30
possible duplicate of How do I mention my spare time projects in resume?
– gnat
Jul 3 '14 at 7:30
possible duplicate of How do I mention my spare time projects in resume?
– gnat
Jul 3 '14 at 7:30
suggest improvements |Â
4 Answers
4
active
oldest
votes
up vote
6
down vote
accepted
1'd create a github repository and store the code there (*)
In the README.md file, I'd list the apps and give a short description of each app as well as instructions on how to run it.
I'd create a link in the resume to the github. I'd call the link "Contributions to Open Source" or something like that.
Done.
(*) In response to the OP's comment that the MUD game is not open sourced:
Exclude the MUD from the github. You can mention it in your cover letter and in your interviews in the same breath that you say you are not outsourcing it. However, you should be able to come across as knowledgeable about MUD implementation issues and trade-offs. And coming across as knowledgeable would establish your credibility without you having to disclose your source code.
answered Jul 2 '14 at 23:46
Vietnhi Phuvan
68.9k7118254
Hm. The MUD isn't open-source at all nor is there any plan to for the near future.
– Zeno
Jul 2 '14 at 23:52
I've seen some resumes with "Opensource" or "Github" sections with give a link to the repos, and then a quick blurb about projects the person is active in.
– sevensevens
Aug 3 '14 at 17:56
suggest improvements |Â
up vote
2
down vote
In general, treat the projects as jobs. On the resume, create a section for personal projects, and include:
- Name of project or software product
- Organization (if applicable) that the project was for
- Description of the project and your work on it.
- time range of contribution
- Any reference you can provide to it - URL, github respository - what ever options you can give to let a reviewer access it.
As a resume reader, I don't generally look for examples of the work when we're talking about paid-for job - because I realize that so much of a person's work may not be publicly available. I have, however, googled for the company to see what the business is about.
But personal projects are both under the applicant's control, and also wildly variable. So if I think of the project as a great example of good work, I actually go and look at what I can. Which means that good code, either in execution (like when I visit the MUD) or in a repository, will leave a good impression. And bad code will leave a negative impression.
My strongest recommendation is - don't share a work in progress that will leave a poor impression. For example, getting a tech writing sample from a writer with poor/inconsistent layout, bad grammar, and bugs in the HTML will be worse than no sample at all. Same goes for code - if your website is buggy, if your code is a horror to read, etc... I'm going to be concerned about your judgement.
answered Jul 3 '14 at 13:59
bethlakshmi
70.3k4136277
suggest improvements |Â
up vote
0
down vote
From my experience hobby projects are not really counted as professional experience, or even experience at all, by employers - at least in Finland, where only professional work is counted. Maybe the requirements are less strict in other countries.
So I would say it depends on the general views in your region. There can be differences even within a given country but different locations.
answered Jul 3 '14 at 7:57
Juha Untinen
1,5261018
suggest improvements |Â
up vote
0
down vote
That's something you should definitely do.
Hobby projects shows you are considering development as more than a job, not someone constantly checking the clock to pack up and leave at 6 PM. You enjoy what you are doing and you are open to learn new technologies. That's the number one thing both hiring managers and Development Team Leaders are looking for, even comes in front of work experience on so many occasions.
In fact, you should create a professional website or portal which shows all your hobby projects, at least demos of them, with code samples.
answered Aug 17 '16 at 16:35
Necati Hakan Erdogan
36929
suggest improvements |Â
StackExchange.ready(function ()
$("#show-editor-button input, #show-editor-button button").click(function ()
var showEditor = function()
$("#show-editor-button").hide();
$("#post-form").removeClass("dno");
StackExchange.editor.finallyInit();
;
var useFancy = $(this).data('confirm-use-fancy');
if(useFancy == 'True')
var popupTitle = $(this).data('confirm-fancy-title');
var popupBody = $(this).data('confirm-fancy-body');
var popupAccept = $(this).data('confirm-fancy-accept-button');
$(this).loadPopup(
url: '/post/self-answer-popup',
loaded: function(popup)
var pTitle = $(popup).find('h2');
var pBody = $(popup).find('.popup-body');
var pSubmit = $(popup).find('.popup-submit');
pTitle.text(popupTitle);
pBody.html(popupBody);
pSubmit.val(popupAccept).click(showEditor);
)
else
var confirmText = $(this).data('confirm-text');
if (confirmText ? confirm(confirmText) : true)
showEditor();
);
);
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
6
down vote
accepted
1'd create a github repository and store the code there (*)
In the README.md file, I'd list the apps and give a short description of each app as well as instructions on how to run it.
I'd create a link in the resume to the github. I'd call the link "Contributions to Open Source" or something like that.
Done.
(*) In response to the OP's comment that the MUD game is not open sourced:
Exclude the MUD from the github. You can mention it in your cover letter and in your interviews in the same breath that you say you are not outsourcing it. However, you should be able to come across as knowledgeable about MUD implementation issues and trade-offs. And coming across as knowledgeable would establish your credibility without you having to disclose your source code.
answered Jul 2 '14 at 23:46
Vietnhi Phuvan
68.9k7118254
Hm. The MUD isn't open-source at all nor is there any plan to for the near future.
– Zeno
Jul 2 '14 at 23:52
I've seen some resumes with "Opensource" or "Github" sections with give a link to the repos, and then a quick blurb about projects the person is active in.
– sevensevens
Aug 3 '14 at 17:56
suggest improvements |Â
up vote
6
down vote
accepted
1'd create a github repository and store the code there (*)
In the README.md file, I'd list the apps and give a short description of each app as well as instructions on how to run it.
I'd create a link in the resume to the github. I'd call the link "Contributions to Open Source" or something like that.
Done.
(*) In response to the OP's comment that the MUD game is not open sourced:
Exclude the MUD from the github. You can mention it in your cover letter and in your interviews in the same breath that you say you are not outsourcing it. However, you should be able to come across as knowledgeable about MUD implementation issues and trade-offs. And coming across as knowledgeable would establish your credibility without you having to disclose your source code.
answered Jul 2 '14 at 23:46
Vietnhi Phuvan
68.9k7118254
Hm. The MUD isn't open-source at all nor is there any plan to for the near future.
– Zeno
Jul 2 '14 at 23:52
I've seen some resumes with "Opensource" or "Github" sections with give a link to the repos, and then a quick blurb about projects the person is active in.
– sevensevens
Aug 3 '14 at 17:56
suggest improvements |Â
up vote
6
down vote
accepted
up vote
6
down vote
accepted
1'd create a github repository and store the code there (*)
In the README.md file, I'd list the apps and give a short description of each app as well as instructions on how to run it.
I'd create a link in the resume to the github. I'd call the link "Contributions to Open Source" or something like that.
Done.
(*) In response to the OP's comment that the MUD game is not open sourced:
Exclude the MUD from the github. You can mention it in your cover letter and in your interviews in the same breath that you say you are not outsourcing it. However, you should be able to come across as knowledgeable about MUD implementation issues and trade-offs. And coming across as knowledgeable would establish your credibility without you having to disclose your source code.
answered Jul 2 '14 at 23:46
Vietnhi Phuvan
68.9k7118254
1'd create a github repository and store the code there (*)
In the README.md file, I'd list the apps and give a short description of each app as well as instructions on how to run it.
I'd create a link in the resume to the github. I'd call the link "Contributions to Open Source" or something like that.
Done.
(*) In response to the OP's comment that the MUD game is not open sourced:
Exclude the MUD from the github. You can mention it in your cover letter and in your interviews in the same breath that you say you are not outsourcing it. However, you should be able to come across as knowledgeable about MUD implementation issues and trade-offs. And coming across as knowledgeable would establish your credibility without you having to disclose your source code.
answered Jul 2 '14 at 23:46
Vietnhi Phuvan
68.9k7118254
edited Jul 3 '14 at 11:21
answered Jul 2 '14 at 23:46
Vietnhi Phuvan
68.9k7118254
answered Jul 2 '14 at 23:46
Vietnhi Phuvan
68.9k7118254
answered Jul 2 '14 at 23:46
Vietnhi Phuvan
68.9k7118254
68.9k7118254
Hm. The MUD isn't open-source at all nor is there any plan to for the near future.
– Zeno
Jul 2 '14 at 23:52
I've seen some resumes with "Opensource" or "Github" sections with give a link to the repos, and then a quick blurb about projects the person is active in.
– sevensevens
Aug 3 '14 at 17:56
suggest improvements |Â
Hm. The MUD isn't open-source at all nor is there any plan to for the near future.
– Zeno
Jul 2 '14 at 23:52
I've seen some resumes with "Opensource" or "Github" sections with give a link to the repos, and then a quick blurb about projects the person is active in.
– sevensevens
Aug 3 '14 at 17:56
Hm. The MUD isn't open-source at all nor is there any plan to for the near future.
– Zeno
Jul 2 '14 at 23:52
Hm. The MUD isn't open-source at all nor is there any plan to for the near future.
– Zeno
Jul 2 '14 at 23:52
I've seen some resumes with "Opensource" or "Github" sections with give a link to the repos, and then a quick blurb about projects the person is active in.
– sevensevens
Aug 3 '14 at 17:56
I've seen some resumes with "Opensource" or "Github" sections with give a link to the repos, and then a quick blurb about projects the person is active in.
– sevensevens
Aug 3 '14 at 17:56
suggest improvements |Â
up vote
2
down vote
In general, treat the projects as jobs. On the resume, create a section for personal projects, and include:
- Name of project or software product
- Organization (if applicable) that the project was for
- Description of the project and your work on it.
- time range of contribution
- Any reference you can provide to it - URL, github respository - what ever options you can give to let a reviewer access it.
As a resume reader, I don't generally look for examples of the work when we're talking about paid-for job - because I realize that so much of a person's work may not be publicly available. I have, however, googled for the company to see what the business is about.
But personal projects are both under the applicant's control, and also wildly variable. So if I think of the project as a great example of good work, I actually go and look at what I can. Which means that good code, either in execution (like when I visit the MUD) or in a repository, will leave a good impression. And bad code will leave a negative impression.
My strongest recommendation is - don't share a work in progress that will leave a poor impression. For example, getting a tech writing sample from a writer with poor/inconsistent layout, bad grammar, and bugs in the HTML will be worse than no sample at all. Same goes for code - if your website is buggy, if your code is a horror to read, etc... I'm going to be concerned about your judgement.
answered Jul 3 '14 at 13:59
bethlakshmi
70.3k4136277
suggest improvements |Â
up vote
2
down vote
In general, treat the projects as jobs. On the resume, create a section for personal projects, and include:
- Name of project or software product
- Organization (if applicable) that the project was for
- Description of the project and your work on it.
- time range of contribution
- Any reference you can provide to it - URL, github respository - what ever options you can give to let a reviewer access it.
As a resume reader, I don't generally look for examples of the work when we're talking about paid-for job - because I realize that so much of a person's work may not be publicly available. I have, however, googled for the company to see what the business is about.
But personal projects are both under the applicant's control, and also wildly variable. So if I think of the project as a great example of good work, I actually go and look at what I can. Which means that good code, either in execution (like when I visit the MUD) or in a repository, will leave a good impression. And bad code will leave a negative impression.
My strongest recommendation is - don't share a work in progress that will leave a poor impression. For example, getting a tech writing sample from a writer with poor/inconsistent layout, bad grammar, and bugs in the HTML will be worse than no sample at all. Same goes for code - if your website is buggy, if your code is a horror to read, etc... I'm going to be concerned about your judgement.
answered Jul 3 '14 at 13:59
bethlakshmi
70.3k4136277
suggest improvements |Â
up vote
2
down vote
up vote
2
down vote
In general, treat the projects as jobs. On the resume, create a section for personal projects, and include:
- Name of project or software product
- Organization (if applicable) that the project was for
- Description of the project and your work on it.
- time range of contribution
- Any reference you can provide to it - URL, github respository - what ever options you can give to let a reviewer access it.
As a resume reader, I don't generally look for examples of the work when we're talking about paid-for job - because I realize that so much of a person's work may not be publicly available. I have, however, googled for the company to see what the business is about.
But personal projects are both under the applicant's control, and also wildly variable. So if I think of the project as a great example of good work, I actually go and look at what I can. Which means that good code, either in execution (like when I visit the MUD) or in a repository, will leave a good impression. And bad code will leave a negative impression.
My strongest recommendation is - don't share a work in progress that will leave a poor impression. For example, getting a tech writing sample from a writer with poor/inconsistent layout, bad grammar, and bugs in the HTML will be worse than no sample at all. Same goes for code - if your website is buggy, if your code is a horror to read, etc... I'm going to be concerned about your judgement.
answered Jul 3 '14 at 13:59
bethlakshmi
70.3k4136277
In general, treat the projects as jobs. On the resume, create a section for personal projects, and include:
- Name of project or software product
- Organization (if applicable) that the project was for
- Description of the project and your work on it.
- time range of contribution
- Any reference you can provide to it - URL, github respository - what ever options you can give to let a reviewer access it.
As a resume reader, I don't generally look for examples of the work when we're talking about paid-for job - because I realize that so much of a person's work may not be publicly available. I have, however, googled for the company to see what the business is about.
But personal projects are both under the applicant's control, and also wildly variable. So if I think of the project as a great example of good work, I actually go and look at what I can. Which means that good code, either in execution (like when I visit the MUD) or in a repository, will leave a good impression. And bad code will leave a negative impression.
My strongest recommendation is - don't share a work in progress that will leave a poor impression. For example, getting a tech writing sample from a writer with poor/inconsistent layout, bad grammar, and bugs in the HTML will be worse than no sample at all. Same goes for code - if your website is buggy, if your code is a horror to read, etc... I'm going to be concerned about your judgement.
answered Jul 3 '14 at 13:59
bethlakshmi
70.3k4136277
answered Jul 3 '14 at 13:59
bethlakshmi
70.3k4136277
answered Jul 3 '14 at 13:59
bethlakshmi
70.3k4136277
answered Jul 3 '14 at 13:59
bethlakshmi
70.3k4136277
70.3k4136277
suggest improvements |Â
suggest improvements |Â
up vote
0
down vote
From my experience hobby projects are not really counted as professional experience, or even experience at all, by employers - at least in Finland, where only professional work is counted. Maybe the requirements are less strict in other countries.
So I would say it depends on the general views in your region. There can be differences even within a given country but different locations.
answered Jul 3 '14 at 7:57
Juha Untinen
1,5261018
suggest improvements |Â
up vote
0
down vote
From my experience hobby projects are not really counted as professional experience, or even experience at all, by employers - at least in Finland, where only professional work is counted. Maybe the requirements are less strict in other countries.
So I would say it depends on the general views in your region. There can be differences even within a given country but different locations.
answered Jul 3 '14 at 7:57
Juha Untinen
1,5261018
suggest improvements |Â
up vote
0
down vote
up vote
0
down vote
From my experience hobby projects are not really counted as professional experience, or even experience at all, by employers - at least in Finland, where only professional work is counted. Maybe the requirements are less strict in other countries.
So I would say it depends on the general views in your region. There can be differences even within a given country but different locations.
answered Jul 3 '14 at 7:57
Juha Untinen
1,5261018
From my experience hobby projects are not really counted as professional experience, or even experience at all, by employers - at least in Finland, where only professional work is counted. Maybe the requirements are less strict in other countries.
So I would say it depends on the general views in your region. There can be differences even within a given country but different locations.
answered Jul 3 '14 at 7:57
Juha Untinen
1,5261018
edited Jul 3 '14 at 8:07
answered Jul 3 '14 at 7:57
Juha Untinen
1,5261018
answered Jul 3 '14 at 7:57
Juha Untinen
1,5261018
answered Jul 3 '14 at 7:57
Juha Untinen
1,5261018
1,5261018
suggest improvements |Â
suggest improvements |Â
up vote
0
down vote
That's something you should definitely do.
Hobby projects shows you are considering development as more than a job, not someone constantly checking the clock to pack up and leave at 6 PM. You enjoy what you are doing and you are open to learn new technologies. That's the number one thing both hiring managers and Development Team Leaders are looking for, even comes in front of work experience on so many occasions.
In fact, you should create a professional website or portal which shows all your hobby projects, at least demos of them, with code samples.
answered Aug 17 '16 at 16:35
Necati Hakan Erdogan
36929
suggest improvements |Â
up vote
0
down vote
That's something you should definitely do.
Hobby projects shows you are considering development as more than a job, not someone constantly checking the clock to pack up and leave at 6 PM. You enjoy what you are doing and you are open to learn new technologies. That's the number one thing both hiring managers and Development Team Leaders are looking for, even comes in front of work experience on so many occasions.
In fact, you should create a professional website or portal which shows all your hobby projects, at least demos of them, with code samples.
answered Aug 17 '16 at 16:35
Necati Hakan Erdogan
36929
suggest improvements |Â
up vote
0
down vote
up vote
0
down vote
That's something you should definitely do.
Hobby projects shows you are considering development as more than a job, not someone constantly checking the clock to pack up and leave at 6 PM. You enjoy what you are doing and you are open to learn new technologies. That's the number one thing both hiring managers and Development Team Leaders are looking for, even comes in front of work experience on so many occasions.
In fact, you should create a professional website or portal which shows all your hobby projects, at least demos of them, with code samples.
answered Aug 17 '16 at 16:35
Necati Hakan Erdogan
36929
That's something you should definitely do.
Hobby projects shows you are considering development as more than a job, not someone constantly checking the clock to pack up and leave at 6 PM. You enjoy what you are doing and you are open to learn new technologies. That's the number one thing both hiring managers and Development Team Leaders are looking for, even comes in front of work experience on so many occasions.
In fact, you should create a professional website or portal which shows all your hobby projects, at least demos of them, with code samples.
answered Aug 17 '16 at 16:35
Necati Hakan Erdogan
36929
answered Aug 17 '16 at 16:35
Necati Hakan Erdogan
36929
answered Aug 17 '16 at 16:35
Necati Hakan Erdogan
36929
answered Aug 17 '16 at 16:35
Necati Hakan Erdogan
36929
36929
suggest improvements |Â
suggest improvements |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f28103%2fadding-hobby-projects-to-resume%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
possible duplicate of How do I mention my spare time projects in resume?
– gnat
Jul 3 '14 at 7:30