Mixing
Should I put a past or new/limited software skills on my CV as an engineering intern?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
3
down vote
favorite
I'm a bit stuck if I should put some software listings on my CV under the skills subheading.
For instance:
Adobe Suite
I can probably doodle up a half-decent brochure or leaflet in Adobe Illustrator, but haven't used it in at least two years so there might be a few hours before I get up to full speed.
SQL
Have set up databases and tables in the past integrated with Python and PHP backends. I have a fair grip on the fundamentals, but by no means high-end or professional.
- How much do I need to know to put it on the CV? Should I list the stuff for the sake of demonstrating flexibility and versatility, even though it won't be high-level work at least for the first hours or days?
- I could add 'disclaimers', like (60%) or (3/5) next to each one, but that seems tedious and somewhat unrepresentative perhaps, especially comparing what I could do in the first 10 minutes or if I got a week to get up to speed again. Also seems a bit negative.
Most projects done with these are informal, so I can't really elaborate greatly and/or link to GitHub repos or something.
Background: Central/ Western Europe, Intern, Engineering.
internship skills
asked Sep 10 '15 at 10:59
Antonio
3591312
suggest improvements |Â
up vote
3
down vote
favorite
I'm a bit stuck if I should put some software listings on my CV under the skills subheading.
For instance:
Adobe Suite
I can probably doodle up a half-decent brochure or leaflet in Adobe Illustrator, but haven't used it in at least two years so there might be a few hours before I get up to full speed.
SQL
Have set up databases and tables in the past integrated with Python and PHP backends. I have a fair grip on the fundamentals, but by no means high-end or professional.
- How much do I need to know to put it on the CV? Should I list the stuff for the sake of demonstrating flexibility and versatility, even though it won't be high-level work at least for the first hours or days?
- I could add 'disclaimers', like (60%) or (3/5) next to each one, but that seems tedious and somewhat unrepresentative perhaps, especially comparing what I could do in the first 10 minutes or if I got a week to get up to speed again. Also seems a bit negative.
Most projects done with these are informal, so I can't really elaborate greatly and/or link to GitHub repos or something.
Background: Central/ Western Europe, Intern, Engineering.
internship skills
asked Sep 10 '15 at 10:59
Antonio
3591312
suggest improvements |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I'm a bit stuck if I should put some software listings on my CV under the skills subheading.
For instance:
Adobe Suite
I can probably doodle up a half-decent brochure or leaflet in Adobe Illustrator, but haven't used it in at least two years so there might be a few hours before I get up to full speed.
SQL
Have set up databases and tables in the past integrated with Python and PHP backends. I have a fair grip on the fundamentals, but by no means high-end or professional.
- How much do I need to know to put it on the CV? Should I list the stuff for the sake of demonstrating flexibility and versatility, even though it won't be high-level work at least for the first hours or days?
- I could add 'disclaimers', like (60%) or (3/5) next to each one, but that seems tedious and somewhat unrepresentative perhaps, especially comparing what I could do in the first 10 minutes or if I got a week to get up to speed again. Also seems a bit negative.
Most projects done with these are informal, so I can't really elaborate greatly and/or link to GitHub repos or something.
Background: Central/ Western Europe, Intern, Engineering.
internship skills
asked Sep 10 '15 at 10:59
Antonio
3591312
I'm a bit stuck if I should put some software listings on my CV under the skills subheading.
For instance:
Adobe Suite
I can probably doodle up a half-decent brochure or leaflet in Adobe Illustrator, but haven't used it in at least two years so there might be a few hours before I get up to full speed.
SQL
Have set up databases and tables in the past integrated with Python and PHP backends. I have a fair grip on the fundamentals, but by no means high-end or professional.
- How much do I need to know to put it on the CV? Should I list the stuff for the sake of demonstrating flexibility and versatility, even though it won't be high-level work at least for the first hours or days?
- I could add 'disclaimers', like (60%) or (3/5) next to each one, but that seems tedious and somewhat unrepresentative perhaps, especially comparing what I could do in the first 10 minutes or if I got a week to get up to speed again. Also seems a bit negative.
Most projects done with these are informal, so I can't really elaborate greatly and/or link to GitHub repos or something.
Background: Central/ Western Europe, Intern, Engineering.
internship skills
asked Sep 10 '15 at 10:59
Antonio
3591312
asked Sep 10 '15 at 10:59
Antonio
3591312
asked Sep 10 '15 at 10:59
Antonio
3591312
asked Sep 10 '15 at 10:59
Antonio
3591312
3591312
suggest improvements |Â
suggest improvements |Â
3 Answers
3
active
oldest
votes
up vote
5
down vote
accepted
How much do I need to know to put it on the CV? Should I list the
stuff for the sake of demonstrating flexibility and versatility, even
though it won't be high-level work at least for the first hours or
days?
To me, your current knowledge level is sufficient to include these skills on your CV. Quite often, interns aren't expected to be experts in many skills. And certainly the first few hours of an internship aren't expected to be full-production time.
I could add 'disclaimers', like (60%) or (3/5) next to each one, but
that seems tedious and somewhat unrepresentative perhaps, especially
comparing what I could do in the first 10 minutes or if I got a week
to get up to speed again. Also seems a bit negative.
While some suggest indicating a level of expertise next to each skill (Novice, Expert, etc), I find that unnecessary.
You do need to be ready to explain the depth of your knowledge of the skills you have listed when asked. And if the particular position demands depth in one of these skills you may be asked to demonstrate them (sometimes through answering questions, sometimes on a whiteboard, etc).
When asked, don't lie or exaggerate. But prepare ahead of time as best you can. Think of it as "cramming for a test" so that you can show yourself in your best light.
answered Sep 10 '15 at 11:24
Joe Strazzere
223k105653921
suggest improvements |Â
up vote
1
down vote
Don't go into too much detail on your skill level (5/10 for example) - It's too subjective and complicates things
Add something to your CV if you are confident that you can talk about it in interview and do a job involving that skill. That's it, nothing complicated. Your experience in the workplace (or lack of it) should be clear on your CV, and any competent recruiter will be able to decipher that: eg if you state Illustrator on your CV they will assume you can use it, but won't expect you to be an expert unless you have several roles on your CV which mention it, adding up to a few years experience. If they're in doubt they'll likely ask you about it at interview. In short, if you're generally at a junior, inexperienced level, they will expect any skills to be at roughly that level.
And don't worry about a few hours - we all get rusty. If it takes you a morning or even a day or two to start getting back up to speed, that happens. Even taking a week or two to get into something more complex can be fine... The point is that you can do it and will just be getting back into old habits (and learning those aspects which have changed recent)
answered Sep 11 '15 at 3:29
Jon Story
6,49022045
suggest improvements |Â
up vote
1
down vote
This works well: Comfortable languages/environments: ..., Other languages/environments I enjoy: ... Make sure you can answer 90% of the questions about the comfortable bracket and 30-50% of the enjoyable ones. Also gives definition to the ones you are learning and why you're learning them, whilst providing a solid view that you know your comfortable areas.
I.e. if you want a job in C++, but also have experience with Java. C++ is comfortable, Java is enjoyable.
answered Sep 11 '15 at 9:42
insidesin
180110
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
5
down vote
accepted
How much do I need to know to put it on the CV? Should I list the
stuff for the sake of demonstrating flexibility and versatility, even
though it won't be high-level work at least for the first hours or
days?
To me, your current knowledge level is sufficient to include these skills on your CV. Quite often, interns aren't expected to be experts in many skills. And certainly the first few hours of an internship aren't expected to be full-production time.
I could add 'disclaimers', like (60%) or (3/5) next to each one, but
that seems tedious and somewhat unrepresentative perhaps, especially
comparing what I could do in the first 10 minutes or if I got a week
to get up to speed again. Also seems a bit negative.
While some suggest indicating a level of expertise next to each skill (Novice, Expert, etc), I find that unnecessary.
You do need to be ready to explain the depth of your knowledge of the skills you have listed when asked. And if the particular position demands depth in one of these skills you may be asked to demonstrate them (sometimes through answering questions, sometimes on a whiteboard, etc).
When asked, don't lie or exaggerate. But prepare ahead of time as best you can. Think of it as "cramming for a test" so that you can show yourself in your best light.
answered Sep 10 '15 at 11:24
Joe Strazzere
223k105653921
suggest improvements |Â
up vote
5
down vote
accepted
How much do I need to know to put it on the CV? Should I list the
stuff for the sake of demonstrating flexibility and versatility, even
though it won't be high-level work at least for the first hours or
days?
To me, your current knowledge level is sufficient to include these skills on your CV. Quite often, interns aren't expected to be experts in many skills. And certainly the first few hours of an internship aren't expected to be full-production time.
I could add 'disclaimers', like (60%) or (3/5) next to each one, but
that seems tedious and somewhat unrepresentative perhaps, especially
comparing what I could do in the first 10 minutes or if I got a week
to get up to speed again. Also seems a bit negative.
While some suggest indicating a level of expertise next to each skill (Novice, Expert, etc), I find that unnecessary.
You do need to be ready to explain the depth of your knowledge of the skills you have listed when asked. And if the particular position demands depth in one of these skills you may be asked to demonstrate them (sometimes through answering questions, sometimes on a whiteboard, etc).
When asked, don't lie or exaggerate. But prepare ahead of time as best you can. Think of it as "cramming for a test" so that you can show yourself in your best light.
answered Sep 10 '15 at 11:24
Joe Strazzere
223k105653921
suggest improvements |Â
up vote
5
down vote
accepted
up vote
5
down vote
accepted
How much do I need to know to put it on the CV? Should I list the
stuff for the sake of demonstrating flexibility and versatility, even
though it won't be high-level work at least for the first hours or
days?
To me, your current knowledge level is sufficient to include these skills on your CV. Quite often, interns aren't expected to be experts in many skills. And certainly the first few hours of an internship aren't expected to be full-production time.
I could add 'disclaimers', like (60%) or (3/5) next to each one, but
that seems tedious and somewhat unrepresentative perhaps, especially
comparing what I could do in the first 10 minutes or if I got a week
to get up to speed again. Also seems a bit negative.
While some suggest indicating a level of expertise next to each skill (Novice, Expert, etc), I find that unnecessary.
You do need to be ready to explain the depth of your knowledge of the skills you have listed when asked. And if the particular position demands depth in one of these skills you may be asked to demonstrate them (sometimes through answering questions, sometimes on a whiteboard, etc).
When asked, don't lie or exaggerate. But prepare ahead of time as best you can. Think of it as "cramming for a test" so that you can show yourself in your best light.
answered Sep 10 '15 at 11:24
Joe Strazzere
223k105653921
How much do I need to know to put it on the CV? Should I list the
stuff for the sake of demonstrating flexibility and versatility, even
though it won't be high-level work at least for the first hours or
days?
To me, your current knowledge level is sufficient to include these skills on your CV. Quite often, interns aren't expected to be experts in many skills. And certainly the first few hours of an internship aren't expected to be full-production time.
I could add 'disclaimers', like (60%) or (3/5) next to each one, but
that seems tedious and somewhat unrepresentative perhaps, especially
comparing what I could do in the first 10 minutes or if I got a week
to get up to speed again. Also seems a bit negative.
While some suggest indicating a level of expertise next to each skill (Novice, Expert, etc), I find that unnecessary.
You do need to be ready to explain the depth of your knowledge of the skills you have listed when asked. And if the particular position demands depth in one of these skills you may be asked to demonstrate them (sometimes through answering questions, sometimes on a whiteboard, etc).
When asked, don't lie or exaggerate. But prepare ahead of time as best you can. Think of it as "cramming for a test" so that you can show yourself in your best light.
answered Sep 10 '15 at 11:24
Joe Strazzere
223k105653921
edited Sep 10 '15 at 13:06
answered Sep 10 '15 at 11:24
Joe Strazzere
223k105653921
answered Sep 10 '15 at 11:24
Joe Strazzere
223k105653921
answered Sep 10 '15 at 11:24
Joe Strazzere
223k105653921
223k105653921
suggest improvements |Â
suggest improvements |Â
up vote
1
down vote
Don't go into too much detail on your skill level (5/10 for example) - It's too subjective and complicates things
Add something to your CV if you are confident that you can talk about it in interview and do a job involving that skill. That's it, nothing complicated. Your experience in the workplace (or lack of it) should be clear on your CV, and any competent recruiter will be able to decipher that: eg if you state Illustrator on your CV they will assume you can use it, but won't expect you to be an expert unless you have several roles on your CV which mention it, adding up to a few years experience. If they're in doubt they'll likely ask you about it at interview. In short, if you're generally at a junior, inexperienced level, they will expect any skills to be at roughly that level.
And don't worry about a few hours - we all get rusty. If it takes you a morning or even a day or two to start getting back up to speed, that happens. Even taking a week or two to get into something more complex can be fine... The point is that you can do it and will just be getting back into old habits (and learning those aspects which have changed recent)
answered Sep 11 '15 at 3:29
Jon Story
6,49022045
suggest improvements |Â
up vote
1
down vote
Don't go into too much detail on your skill level (5/10 for example) - It's too subjective and complicates things
Add something to your CV if you are confident that you can talk about it in interview and do a job involving that skill. That's it, nothing complicated. Your experience in the workplace (or lack of it) should be clear on your CV, and any competent recruiter will be able to decipher that: eg if you state Illustrator on your CV they will assume you can use it, but won't expect you to be an expert unless you have several roles on your CV which mention it, adding up to a few years experience. If they're in doubt they'll likely ask you about it at interview. In short, if you're generally at a junior, inexperienced level, they will expect any skills to be at roughly that level.
And don't worry about a few hours - we all get rusty. If it takes you a morning or even a day or two to start getting back up to speed, that happens. Even taking a week or two to get into something more complex can be fine... The point is that you can do it and will just be getting back into old habits (and learning those aspects which have changed recent)
answered Sep 11 '15 at 3:29
Jon Story
6,49022045
suggest improvements |Â
up vote
1
down vote
up vote
1
down vote
Don't go into too much detail on your skill level (5/10 for example) - It's too subjective and complicates things
Add something to your CV if you are confident that you can talk about it in interview and do a job involving that skill. That's it, nothing complicated. Your experience in the workplace (or lack of it) should be clear on your CV, and any competent recruiter will be able to decipher that: eg if you state Illustrator on your CV they will assume you can use it, but won't expect you to be an expert unless you have several roles on your CV which mention it, adding up to a few years experience. If they're in doubt they'll likely ask you about it at interview. In short, if you're generally at a junior, inexperienced level, they will expect any skills to be at roughly that level.
And don't worry about a few hours - we all get rusty. If it takes you a morning or even a day or two to start getting back up to speed, that happens. Even taking a week or two to get into something more complex can be fine... The point is that you can do it and will just be getting back into old habits (and learning those aspects which have changed recent)
answered Sep 11 '15 at 3:29
Jon Story
6,49022045
Don't go into too much detail on your skill level (5/10 for example) - It's too subjective and complicates things
Add something to your CV if you are confident that you can talk about it in interview and do a job involving that skill. That's it, nothing complicated. Your experience in the workplace (or lack of it) should be clear on your CV, and any competent recruiter will be able to decipher that: eg if you state Illustrator on your CV they will assume you can use it, but won't expect you to be an expert unless you have several roles on your CV which mention it, adding up to a few years experience. If they're in doubt they'll likely ask you about it at interview. In short, if you're generally at a junior, inexperienced level, they will expect any skills to be at roughly that level.
And don't worry about a few hours - we all get rusty. If it takes you a morning or even a day or two to start getting back up to speed, that happens. Even taking a week or two to get into something more complex can be fine... The point is that you can do it and will just be getting back into old habits (and learning those aspects which have changed recent)
answered Sep 11 '15 at 3:29
Jon Story
6,49022045
answered Sep 11 '15 at 3:29
Jon Story
6,49022045
answered Sep 11 '15 at 3:29
Jon Story
6,49022045
answered Sep 11 '15 at 3:29
Jon Story
6,49022045
6,49022045
suggest improvements |Â
suggest improvements |Â
up vote
1
down vote
This works well: Comfortable languages/environments: ..., Other languages/environments I enjoy: ... Make sure you can answer 90% of the questions about the comfortable bracket and 30-50% of the enjoyable ones. Also gives definition to the ones you are learning and why you're learning them, whilst providing a solid view that you know your comfortable areas.
I.e. if you want a job in C++, but also have experience with Java. C++ is comfortable, Java is enjoyable.
answered Sep 11 '15 at 9:42
insidesin
180110
suggest improvements |Â
up vote
1
down vote
This works well: Comfortable languages/environments: ..., Other languages/environments I enjoy: ... Make sure you can answer 90% of the questions about the comfortable bracket and 30-50% of the enjoyable ones. Also gives definition to the ones you are learning and why you're learning them, whilst providing a solid view that you know your comfortable areas.
I.e. if you want a job in C++, but also have experience with Java. C++ is comfortable, Java is enjoyable.
answered Sep 11 '15 at 9:42
insidesin
180110
suggest improvements |Â
up vote
1
down vote
up vote
1
down vote
This works well: Comfortable languages/environments: ..., Other languages/environments I enjoy: ... Make sure you can answer 90% of the questions about the comfortable bracket and 30-50% of the enjoyable ones. Also gives definition to the ones you are learning and why you're learning them, whilst providing a solid view that you know your comfortable areas.
I.e. if you want a job in C++, but also have experience with Java. C++ is comfortable, Java is enjoyable.
answered Sep 11 '15 at 9:42
insidesin
180110
This works well: Comfortable languages/environments: ..., Other languages/environments I enjoy: ... Make sure you can answer 90% of the questions about the comfortable bracket and 30-50% of the enjoyable ones. Also gives definition to the ones you are learning and why you're learning them, whilst providing a solid view that you know your comfortable areas.
I.e. if you want a job in C++, but also have experience with Java. C++ is comfortable, Java is enjoyable.
answered Sep 11 '15 at 9:42
insidesin
180110
answered Sep 11 '15 at 9:42
insidesin
180110
answered Sep 11 '15 at 9:42
insidesin
180110
answered Sep 11 '15 at 9:42
insidesin
180110
180110
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%2f54183%2fshould-i-put-a-past-or-new-limited-software-skills-on-my-cv-as-an-engineering-in%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
