Should I add semester projects to my resume?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty{ margin-bottom:0;
}
up vote
0
down vote
favorite
Will adding projects from my Software Engineering degree to my resume improve my job application?
professionalism resume
edited 18 mins ago
jcmack
7,02711438
asked 4 hours ago
Waqar Ahmad Khan
43
New contributor
Waqar Ahmad Khan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
Will adding projects from my Software Engineering degree to my resume improve my job application?
professionalism resume
edited 18 mins ago
jcmack
7,02711438
asked 4 hours ago
Waqar Ahmad Khan
43
New contributor
Waqar Ahmad Khan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
They would add very little value. But sometimes that's the best you can do.
– Joe Strazzere
3 hours ago
I don't like seeing homework assignments on your resume, because they are very small, very structured (i.e. the entire spec is practically handed to you) and overall tell me very little about your abilities as a software engineer. I want to see big scale projects that you built from the ground with very little guidelines like a capstone project.
– jcmack
15 mins ago
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Will adding projects from my Software Engineering degree to my resume improve my job application?
professionalism resume
edited 18 mins ago
jcmack
7,02711438
asked 4 hours ago
Waqar Ahmad Khan
43
New contributor
Waqar Ahmad Khan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Will adding projects from my Software Engineering degree to my resume improve my job application?
professionalism resume
professionalism resume
edited 18 mins ago
jcmack
7,02711438
asked 4 hours ago
Waqar Ahmad Khan
43
New contributor
Waqar Ahmad Khan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 18 mins ago
jcmack
7,02711438
asked 4 hours ago
Waqar Ahmad Khan
43
New contributor
Waqar Ahmad Khan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 18 mins ago
jcmack
7,02711438
edited 18 mins ago
jcmack
7,02711438
edited 18 mins ago
jcmack
7,02711438
7,02711438
asked 4 hours ago
Waqar Ahmad Khan
43
New contributor
Waqar Ahmad Khan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 4 hours ago
Waqar Ahmad Khan
43
asked 4 hours ago
Waqar Ahmad Khan
43
43
New contributor
Waqar Ahmad Khan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Waqar Ahmad Khan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Waqar Ahmad Khan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
They would add very little value. But sometimes that's the best you can do.
– Joe Strazzere
3 hours ago
I don't like seeing homework assignments on your resume, because they are very small, very structured (i.e. the entire spec is practically handed to you) and overall tell me very little about your abilities as a software engineer. I want to see big scale projects that you built from the ground with very little guidelines like a capstone project.
– jcmack
15 mins ago
add a comment |
They would add very little value. But sometimes that's the best you can do.
– Joe Strazzere
3 hours ago
I don't like seeing homework assignments on your resume, because they are very small, very structured (i.e. the entire spec is practically handed to you) and overall tell me very little about your abilities as a software engineer. I want to see big scale projects that you built from the ground with very little guidelines like a capstone project.
– jcmack
15 mins ago
They would add very little value. But sometimes that's the best you can do.
– Joe Strazzere
3 hours ago
They would add very little value. But sometimes that's the best you can do.
– Joe Strazzere
3 hours ago
I don't like seeing homework assignments on your resume, because they are very small, very structured (i.e. the entire spec is practically handed to you) and overall tell me very little about your abilities as a software engineer. I want to see big scale projects that you built from the ground with very little guidelines like a capstone project.
– jcmack
15 mins ago
I don't like seeing homework assignments on your resume, because they are very small, very structured (i.e. the entire spec is practically handed to you) and overall tell me very little about your abilities as a software engineer. I want to see big scale projects that you built from the ground with very little guidelines like a capstone project.
– jcmack
15 mins ago
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
It depends what type of project it was, what role you had, and how desperate you are to find things to put on your resume.
As a general guideline, include the project if any of these are true:
- You had a big role (ie. "Lead Developer", "Project Manager", etc) and you actually did a something representative of the role. If you were officially the team lead but didn't do any leadership or guiding the efforts, then you don't meet this qualification.
- It was for a real client. When I was in college, I worked a full semester on a group project building out a website for someone. Yes, it was for a friend of someone on our team, but we had a live, external person giving feedback and going through the process with us. Plus, at the end of the day the person did use the website (!).
- It was a project that shows skills and can be viewed as a live product online. ie. You built a CRUD application that hooks up to a database and you deployed it to Azure.
Everything else - Things like a bingo game, algorithm practice exercises, or your midterm assignments - should go into your GitHub repositories. Then put a link to your Github repo in a prominent spot on your resume (right under your name is usually nice).
Obviously, if you have work experience or internships, those go first. Don't go out of your way to push these projects onto the list... They are mainly useful for showcasing real-world projects or hard-core communication/technical experiences when you have no other way to prove yourself.
Good luck!
answered 1 hour ago
c36
565127
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
It depends what type of project it was, what role you had, and how desperate you are to find things to put on your resume.
As a general guideline, include the project if any of these are true:
- You had a big role (ie. "Lead Developer", "Project Manager", etc) and you actually did a something representative of the role. If you were officially the team lead but didn't do any leadership or guiding the efforts, then you don't meet this qualification.
- It was for a real client. When I was in college, I worked a full semester on a group project building out a website for someone. Yes, it was for a friend of someone on our team, but we had a live, external person giving feedback and going through the process with us. Plus, at the end of the day the person did use the website (!).
- It was a project that shows skills and can be viewed as a live product online. ie. You built a CRUD application that hooks up to a database and you deployed it to Azure.
Everything else - Things like a bingo game, algorithm practice exercises, or your midterm assignments - should go into your GitHub repositories. Then put a link to your Github repo in a prominent spot on your resume (right under your name is usually nice).
Obviously, if you have work experience or internships, those go first. Don't go out of your way to push these projects onto the list... They are mainly useful for showcasing real-world projects or hard-core communication/technical experiences when you have no other way to prove yourself.
Good luck!
answered 1 hour ago
c36
565127
add a comment |
up vote
0
down vote
It depends what type of project it was, what role you had, and how desperate you are to find things to put on your resume.
As a general guideline, include the project if any of these are true:
- You had a big role (ie. "Lead Developer", "Project Manager", etc) and you actually did a something representative of the role. If you were officially the team lead but didn't do any leadership or guiding the efforts, then you don't meet this qualification.
- It was for a real client. When I was in college, I worked a full semester on a group project building out a website for someone. Yes, it was for a friend of someone on our team, but we had a live, external person giving feedback and going through the process with us. Plus, at the end of the day the person did use the website (!).
- It was a project that shows skills and can be viewed as a live product online. ie. You built a CRUD application that hooks up to a database and you deployed it to Azure.
Everything else - Things like a bingo game, algorithm practice exercises, or your midterm assignments - should go into your GitHub repositories. Then put a link to your Github repo in a prominent spot on your resume (right under your name is usually nice).
Obviously, if you have work experience or internships, those go first. Don't go out of your way to push these projects onto the list... They are mainly useful for showcasing real-world projects or hard-core communication/technical experiences when you have no other way to prove yourself.
Good luck!
answered 1 hour ago
c36
565127
add a comment |
up vote
0
down vote
up vote
0
down vote
It depends what type of project it was, what role you had, and how desperate you are to find things to put on your resume.
As a general guideline, include the project if any of these are true:
- You had a big role (ie. "Lead Developer", "Project Manager", etc) and you actually did a something representative of the role. If you were officially the team lead but didn't do any leadership or guiding the efforts, then you don't meet this qualification.
- It was for a real client. When I was in college, I worked a full semester on a group project building out a website for someone. Yes, it was for a friend of someone on our team, but we had a live, external person giving feedback and going through the process with us. Plus, at the end of the day the person did use the website (!).
- It was a project that shows skills and can be viewed as a live product online. ie. You built a CRUD application that hooks up to a database and you deployed it to Azure.
Everything else - Things like a bingo game, algorithm practice exercises, or your midterm assignments - should go into your GitHub repositories. Then put a link to your Github repo in a prominent spot on your resume (right under your name is usually nice).
Obviously, if you have work experience or internships, those go first. Don't go out of your way to push these projects onto the list... They are mainly useful for showcasing real-world projects or hard-core communication/technical experiences when you have no other way to prove yourself.
Good luck!
answered 1 hour ago
c36
565127
It depends what type of project it was, what role you had, and how desperate you are to find things to put on your resume.
As a general guideline, include the project if any of these are true:
- You had a big role (ie. "Lead Developer", "Project Manager", etc) and you actually did a something representative of the role. If you were officially the team lead but didn't do any leadership or guiding the efforts, then you don't meet this qualification.
- It was for a real client. When I was in college, I worked a full semester on a group project building out a website for someone. Yes, it was for a friend of someone on our team, but we had a live, external person giving feedback and going through the process with us. Plus, at the end of the day the person did use the website (!).
- It was a project that shows skills and can be viewed as a live product online. ie. You built a CRUD application that hooks up to a database and you deployed it to Azure.
Everything else - Things like a bingo game, algorithm practice exercises, or your midterm assignments - should go into your GitHub repositories. Then put a link to your Github repo in a prominent spot on your resume (right under your name is usually nice).
Obviously, if you have work experience or internships, those go first. Don't go out of your way to push these projects onto the list... They are mainly useful for showcasing real-world projects or hard-core communication/technical experiences when you have no other way to prove yourself.
Good luck!
answered 1 hour ago
c36
565127
answered 1 hour ago
c36
565127
answered 1 hour ago
c36
565127
answered 1 hour ago
c36
565127
565127
add a comment |
add a comment |
Waqar Ahmad Khan is a new contributor. Be nice, and check out our Code of Conduct.
Waqar Ahmad Khan is a new contributor. Be nice, and check out our Code of Conduct.
Waqar Ahmad Khan is a new contributor. Be nice, and check out our Code of Conduct.
Waqar Ahmad Khan is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to The Workplace Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f124167%2fshould-i-add-semester-projects-to-my-resume%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
They would add very little value. But sometimes that's the best you can do.
– Joe Strazzere
3 hours ago
I don't like seeing homework assignments on your resume, because they are very small, very structured (i.e. the entire spec is practically handed to you) and overall tell me very little about your abilities as a software engineer. I want to see big scale projects that you built from the ground with very little guidelines like a capstone project.
– jcmack
15 mins ago