Mixing
Where to put Programming Language that is not in skills set on Resume, but on project portfolio?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
0
down vote
favorite
From this question, it seems that including skills you are currently learning into a resume is not a good idea.
However, if I am currently working on a project using programming language and framework that I am learning as I go, is there anywhere in my resume to write it down? Could I list them as technologies used on that particular project under my Work Experience?
resume
edited Apr 13 '17 at 12:48
Community♦
1
asked Aug 4 '16 at 10:26
Lewis
1,29141222
suggest improvements |Â
up vote
0
down vote
favorite
From this question, it seems that including skills you are currently learning into a resume is not a good idea.
However, if I am currently working on a project using programming language and framework that I am learning as I go, is there anywhere in my resume to write it down? Could I list them as technologies used on that particular project under my Work Experience?
resume
edited Apr 13 '17 at 12:48
Community♦
1
asked Aug 4 '16 at 10:26
Lewis
1,29141222
suggest improvements |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
From this question, it seems that including skills you are currently learning into a resume is not a good idea.
However, if I am currently working on a project using programming language and framework that I am learning as I go, is there anywhere in my resume to write it down? Could I list them as technologies used on that particular project under my Work Experience?
resume
edited Apr 13 '17 at 12:48
Community♦
1
asked Aug 4 '16 at 10:26
Lewis
1,29141222
From this question, it seems that including skills you are currently learning into a resume is not a good idea.
However, if I am currently working on a project using programming language and framework that I am learning as I go, is there anywhere in my resume to write it down? Could I list them as technologies used on that particular project under my Work Experience?
resume
edited Apr 13 '17 at 12:48
Community♦
1
asked Aug 4 '16 at 10:26
Lewis
1,29141222
edited Apr 13 '17 at 12:48
Community♦
1
edited Apr 13 '17 at 12:48
Community♦
1
edited Apr 13 '17 at 12:48
Community♦
1
1
asked Aug 4 '16 at 10:26
Lewis
1,29141222
asked Aug 4 '16 at 10:26
Lewis
1,29141222
asked Aug 4 '16 at 10:26
Lewis
1,29141222
1,29141222
suggest improvements |Â
suggest improvements |Â
3 Answers
3
active
oldest
votes
up vote
2
down vote
accepted
It is quite common to put anything you have at least some experience using in the skills section.
It doesn't imply you are an expert, and won't be understood as such. Anyone reading your resume will understand that. It is only used as a quick gauge of what things you have familiarity with.
So if you are still learning a tool or technology, but have at least gotten far enough that you have a project in progress with some significant code written, there is no problem with listing this as a skill.
If you want to communicate that you are an expert in something in your resume, you need to do more than list it as a skill: you need to detail your specific experience or areas of knowledge.
suggest improvements |Â
up vote
0
down vote
The linked question is about somebody saying his skill is "close to nil". That indeed makes no sense in the skills section.
If you are proficient enough to do a project in it, I would assume it should go into your skills section.
answered Aug 4 '16 at 10:37
nvoigt
42.4k18104146
suggest improvements |Â
up vote
0
down vote
Always put everything relevant to the job for which you are applying in the "skills" section. If you only have limited skill/use of it, put it down as "knowledge of..." but if it is in the body of your resume, it should always be in the skills section.
answered Aug 4 '16 at 12:08
Richard U
77.2k56200307
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();
);
);
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
It is quite common to put anything you have at least some experience using in the skills section.
It doesn't imply you are an expert, and won't be understood as such. Anyone reading your resume will understand that. It is only used as a quick gauge of what things you have familiarity with.
So if you are still learning a tool or technology, but have at least gotten far enough that you have a project in progress with some significant code written, there is no problem with listing this as a skill.
If you want to communicate that you are an expert in something in your resume, you need to do more than list it as a skill: you need to detail your specific experience or areas of knowledge.
suggest improvements |Â
up vote
2
down vote
accepted
It is quite common to put anything you have at least some experience using in the skills section.
It doesn't imply you are an expert, and won't be understood as such. Anyone reading your resume will understand that. It is only used as a quick gauge of what things you have familiarity with.
So if you are still learning a tool or technology, but have at least gotten far enough that you have a project in progress with some significant code written, there is no problem with listing this as a skill.
If you want to communicate that you are an expert in something in your resume, you need to do more than list it as a skill: you need to detail your specific experience or areas of knowledge.
suggest improvements |Â
up vote
2
down vote
accepted
up vote
2
down vote
accepted
It is quite common to put anything you have at least some experience using in the skills section.
It doesn't imply you are an expert, and won't be understood as such. Anyone reading your resume will understand that. It is only used as a quick gauge of what things you have familiarity with.
So if you are still learning a tool or technology, but have at least gotten far enough that you have a project in progress with some significant code written, there is no problem with listing this as a skill.
If you want to communicate that you are an expert in something in your resume, you need to do more than list it as a skill: you need to detail your specific experience or areas of knowledge.
It is quite common to put anything you have at least some experience using in the skills section.
It doesn't imply you are an expert, and won't be understood as such. Anyone reading your resume will understand that. It is only used as a quick gauge of what things you have familiarity with.
So if you are still learning a tool or technology, but have at least gotten far enough that you have a project in progress with some significant code written, there is no problem with listing this as a skill.
If you want to communicate that you are an expert in something in your resume, you need to do more than list it as a skill: you need to detail your specific experience or areas of knowledge.
answered Aug 4 '16 at 11:37
user45590
suggest improvements |Â
suggest improvements |Â
up vote
0
down vote
The linked question is about somebody saying his skill is "close to nil". That indeed makes no sense in the skills section.
If you are proficient enough to do a project in it, I would assume it should go into your skills section.
answered Aug 4 '16 at 10:37
nvoigt
42.4k18104146
suggest improvements |Â
up vote
0
down vote
The linked question is about somebody saying his skill is "close to nil". That indeed makes no sense in the skills section.
If you are proficient enough to do a project in it, I would assume it should go into your skills section.
answered Aug 4 '16 at 10:37
nvoigt
42.4k18104146
suggest improvements |Â
up vote
0
down vote
up vote
0
down vote
The linked question is about somebody saying his skill is "close to nil". That indeed makes no sense in the skills section.
If you are proficient enough to do a project in it, I would assume it should go into your skills section.
answered Aug 4 '16 at 10:37
nvoigt
42.4k18104146
The linked question is about somebody saying his skill is "close to nil". That indeed makes no sense in the skills section.
If you are proficient enough to do a project in it, I would assume it should go into your skills section.
answered Aug 4 '16 at 10:37
nvoigt
42.4k18104146
answered Aug 4 '16 at 10:37
nvoigt
42.4k18104146
answered Aug 4 '16 at 10:37
nvoigt
42.4k18104146
answered Aug 4 '16 at 10:37
nvoigt
42.4k18104146
42.4k18104146
suggest improvements |Â
suggest improvements |Â
up vote
0
down vote
Always put everything relevant to the job for which you are applying in the "skills" section. If you only have limited skill/use of it, put it down as "knowledge of..." but if it is in the body of your resume, it should always be in the skills section.
answered Aug 4 '16 at 12:08
Richard U
77.2k56200307
suggest improvements |Â
up vote
0
down vote
Always put everything relevant to the job for which you are applying in the "skills" section. If you only have limited skill/use of it, put it down as "knowledge of..." but if it is in the body of your resume, it should always be in the skills section.
answered Aug 4 '16 at 12:08
Richard U
77.2k56200307
suggest improvements |Â
up vote
0
down vote
up vote
0
down vote
Always put everything relevant to the job for which you are applying in the "skills" section. If you only have limited skill/use of it, put it down as "knowledge of..." but if it is in the body of your resume, it should always be in the skills section.
answered Aug 4 '16 at 12:08
Richard U
77.2k56200307
Always put everything relevant to the job for which you are applying in the "skills" section. If you only have limited skill/use of it, put it down as "knowledge of..." but if it is in the body of your resume, it should always be in the skills section.
answered Aug 4 '16 at 12:08
Richard U
77.2k56200307
answered Aug 4 '16 at 12:08
Richard U
77.2k56200307
answered Aug 4 '16 at 12:08
Richard U
77.2k56200307
answered Aug 4 '16 at 12:08
Richard U
77.2k56200307
77.2k56200307
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%2f73701%2fwhere-to-put-programming-language-that-is-not-in-skills-set-on-resume-but-on-pr%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
