Mixing
How should I list my programming technologies on a resume?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
15
down vote
favorite
I'm updating my resume, and have realized that many programming skills are very brief and abbreviated.
My old resumes would list them in a bulleted list, however due to all the new technologies I'm adding, this leads to a rather long list of very short items, with a lot of whitespace to the right of the section.
I am wondering if it would be appropriate to list these items in a table instead of a list, or to put them inline in a sentence
For example,
* C#
* WPF
* WCF
* VB.Net
* ASP.Net
* HTML
* CSS
* Javascript
* T-SQL
versus
C# VB.Net HTML
WPF ASP.Net CSS
WCF T-SQL Javascript
versus
C#, WPF, WCF, VB.Net, ASP.Net, HTML, CSS, Javascript, T-SQL
Is one method preferred over others on my resume to make it easier for employers or recruiters to scan through?
resume software-industry skills
edited Jul 31 '14 at 0:48
Ian Holstead
1,0111230
asked May 23 '13 at 14:22
Rachel
6,14184268
 |Â
show 3 more comments
up vote
15
down vote
favorite
I'm updating my resume, and have realized that many programming skills are very brief and abbreviated.
My old resumes would list them in a bulleted list, however due to all the new technologies I'm adding, this leads to a rather long list of very short items, with a lot of whitespace to the right of the section.
I am wondering if it would be appropriate to list these items in a table instead of a list, or to put them inline in a sentence
For example,
* C#
* WPF
* WCF
* VB.Net
* ASP.Net
* HTML
* CSS
* Javascript
* T-SQL
versus
C# VB.Net HTML
WPF ASP.Net CSS
WCF T-SQL Javascript
versus
C#, WPF, WCF, VB.Net, ASP.Net, HTML, CSS, Javascript, T-SQL
Is one method preferred over others on my resume to make it easier for employers or recruiters to scan through?
resume software-industry skills
edited Jul 31 '14 at 0:48
Ian Holstead
1,0111230
asked May 23 '13 at 14:22
Rachel
6,14184268
2
Btw, this isn't at all specific to programming, I think this applies for anyone with a lot of skills (CAD, design, etc).
– Elysian Fields♦
May 23 '13 at 14:37
I list mine in a two column "table" (I quote because it's not formatted as a table, just tabbed out that way). For readability, I would say definitely go with a table. The bulleted list takes up way too much valuable space, and the sentence structure doesn't given enough visibility.
– Dave Johnson
May 23 '13 at 14:42
Maybe it's a good idea to add versions to some of the techs you are familiar with? (C# has changed a bit over time. The abilities of CSS have really changed over time)
– Onno
May 23 '13 at 14:48
Alphabetical list makes it easier to find something they're looking for and it avoids making an impression that one technology is "more important" than another
– Brandin
Jul 31 '14 at 6:15
1
@gnat I agree the questions may be similar, however I prefer the answers given to this one over the one you linked. Of course, I may be biased since I accepted this answer, but if others think so too I'd rather see that one closed as a duplicate to this one instead of vise versa, or the answers merged.
– Rachel
Oct 28 '14 at 11:55
 |Â
show 3 more comments
up vote
15
down vote
favorite
up vote
15
down vote
favorite
I'm updating my resume, and have realized that many programming skills are very brief and abbreviated.
My old resumes would list them in a bulleted list, however due to all the new technologies I'm adding, this leads to a rather long list of very short items, with a lot of whitespace to the right of the section.
I am wondering if it would be appropriate to list these items in a table instead of a list, or to put them inline in a sentence
For example,
* C#
* WPF
* WCF
* VB.Net
* ASP.Net
* HTML
* CSS
* Javascript
* T-SQL
versus
C# VB.Net HTML
WPF ASP.Net CSS
WCF T-SQL Javascript
versus
C#, WPF, WCF, VB.Net, ASP.Net, HTML, CSS, Javascript, T-SQL
Is one method preferred over others on my resume to make it easier for employers or recruiters to scan through?
resume software-industry skills
edited Jul 31 '14 at 0:48
Ian Holstead
1,0111230
asked May 23 '13 at 14:22
Rachel
6,14184268
I'm updating my resume, and have realized that many programming skills are very brief and abbreviated.
My old resumes would list them in a bulleted list, however due to all the new technologies I'm adding, this leads to a rather long list of very short items, with a lot of whitespace to the right of the section.
I am wondering if it would be appropriate to list these items in a table instead of a list, or to put them inline in a sentence
For example,
* C#
* WPF
* WCF
* VB.Net
* ASP.Net
* HTML
* CSS
* Javascript
* T-SQL
versus
C# VB.Net HTML
WPF ASP.Net CSS
WCF T-SQL Javascript
versus
C#, WPF, WCF, VB.Net, ASP.Net, HTML, CSS, Javascript, T-SQL
Is one method preferred over others on my resume to make it easier for employers or recruiters to scan through?
resume software-industry skills
edited Jul 31 '14 at 0:48
Ian Holstead
1,0111230
asked May 23 '13 at 14:22
Rachel
6,14184268
edited Jul 31 '14 at 0:48
Ian Holstead
1,0111230
edited Jul 31 '14 at 0:48
Ian Holstead
1,0111230
edited Jul 31 '14 at 0:48
Ian Holstead
1,0111230
1,0111230
asked May 23 '13 at 14:22
Rachel
6,14184268
asked May 23 '13 at 14:22
Rachel
6,14184268
asked May 23 '13 at 14:22
Rachel
6,14184268
6,14184268
2
Btw, this isn't at all specific to programming, I think this applies for anyone with a lot of skills (CAD, design, etc).
– Elysian Fields♦
May 23 '13 at 14:37
I list mine in a two column "table" (I quote because it's not formatted as a table, just tabbed out that way). For readability, I would say definitely go with a table. The bulleted list takes up way too much valuable space, and the sentence structure doesn't given enough visibility.
– Dave Johnson
May 23 '13 at 14:42
Maybe it's a good idea to add versions to some of the techs you are familiar with? (C# has changed a bit over time. The abilities of CSS have really changed over time)
– Onno
May 23 '13 at 14:48
Alphabetical list makes it easier to find something they're looking for and it avoids making an impression that one technology is "more important" than another
– Brandin
Jul 31 '14 at 6:15
1
@gnat I agree the questions may be similar, however I prefer the answers given to this one over the one you linked. Of course, I may be biased since I accepted this answer, but if others think so too I'd rather see that one closed as a duplicate to this one instead of vise versa, or the answers merged.
– Rachel
Oct 28 '14 at 11:55
 |Â
show 3 more comments
2
Btw, this isn't at all specific to programming, I think this applies for anyone with a lot of skills (CAD, design, etc).
– Elysian Fields♦
May 23 '13 at 14:37
I list mine in a two column "table" (I quote because it's not formatted as a table, just tabbed out that way). For readability, I would say definitely go with a table. The bulleted list takes up way too much valuable space, and the sentence structure doesn't given enough visibility.
– Dave Johnson
May 23 '13 at 14:42
Maybe it's a good idea to add versions to some of the techs you are familiar with? (C# has changed a bit over time. The abilities of CSS have really changed over time)
– Onno
May 23 '13 at 14:48
Alphabetical list makes it easier to find something they're looking for and it avoids making an impression that one technology is "more important" than another
– Brandin
Jul 31 '14 at 6:15
1
@gnat I agree the questions may be similar, however I prefer the answers given to this one over the one you linked. Of course, I may be biased since I accepted this answer, but if others think so too I'd rather see that one closed as a duplicate to this one instead of vise versa, or the answers merged.
– Rachel
Oct 28 '14 at 11:55
2
2
Btw, this isn't at all specific to programming, I think this applies for anyone with a lot of skills (CAD, design, etc).
– Elysian Fields♦
May 23 '13 at 14:37
Btw, this isn't at all specific to programming, I think this applies for anyone with a lot of skills (CAD, design, etc).
– Elysian Fields♦
May 23 '13 at 14:37
I list mine in a two column "table" (I quote because it's not formatted as a table, just tabbed out that way). For readability, I would say definitely go with a table. The bulleted list takes up way too much valuable space, and the sentence structure doesn't given enough visibility.
– Dave Johnson
May 23 '13 at 14:42
I list mine in a two column "table" (I quote because it's not formatted as a table, just tabbed out that way). For readability, I would say definitely go with a table. The bulleted list takes up way too much valuable space, and the sentence structure doesn't given enough visibility.
– Dave Johnson
May 23 '13 at 14:42
Maybe it's a good idea to add versions to some of the techs you are familiar with? (C# has changed a bit over time. The abilities of CSS have really changed over time)
– Onno
May 23 '13 at 14:48
Maybe it's a good idea to add versions to some of the techs you are familiar with? (C# has changed a bit over time. The abilities of CSS have really changed over time)
– Onno
May 23 '13 at 14:48
Alphabetical list makes it easier to find something they're looking for and it avoids making an impression that one technology is "more important" than another
– Brandin
Jul 31 '14 at 6:15
Alphabetical list makes it easier to find something they're looking for and it avoids making an impression that one technology is "more important" than another
– Brandin
Jul 31 '14 at 6:15
1
1
@gnat I agree the questions may be similar, however I prefer the answers given to this one over the one you linked. Of course, I may be biased since I accepted this answer, but if others think so too I'd rather see that one closed as a duplicate to this one instead of vise versa, or the answers merged.
– Rachel
Oct 28 '14 at 11:55
@gnat I agree the questions may be similar, however I prefer the answers given to this one over the one you linked. Of course, I may be biased since I accepted this answer, but if others think so too I'd rather see that one closed as a duplicate to this one instead of vise versa, or the answers merged.
– Rachel
Oct 28 '14 at 11:55
 |Â
show 3 more comments
3 Answers
3
active
oldest
votes
up vote
22
down vote
accepted
I'm no hero when it comes to CVs, but there's a lot of .Net tech in that list. I'd list those in one line. That way you make most of the space available. You could opt to use some kind of matrix style. I'd still make some kind of distinction between the MS tech and the other techniques.
Something like:
.Net technologies and languages:
C#, VB.Net, WPF, WCF, ASP.Net. (IIS 7.5?)
Web technologies and languages:
Javascript, HTML and CSS.
I'm familiar with databases.
T-SQL. (Maybe MSQL2k8?)
If the DB stuff is a bit off you could recatagorize the 'web' to 'other'
If you catagorize the line with list of skills to fit some kind of structure, like: "languages, API's, markup languages, software stacks", the structure should be apparent to any human reader. The automated resume scanners just look for strings anyways, so I can't imagine that you'd get slammed by those on how you lay them out on the page.
I don't know how to do the formatting on SE, but you could even have two columns, each with a title and list the techs in a comma separated format like I just presented. That way you can save space without sacrificing structure.
answered May 23 '13 at 14:44
Onno
876717
this is what i do. But i don't have the cute "i'm familiar with databases". I just say "database technologies", "java", "front-end" & so on
– bharal
May 23 '13 at 15:01
What can I say? I like cute :)
– Onno
May 23 '13 at 15:07
Hrrmmm but there's some overlap. For example, ASP.Net and Silverlight (not listed) are both web technologies and .Net technologies. I like the idea of separating them by category though. I'll play around with different ways of arranging them like that and see what I come up with
– Rachel
May 23 '13 at 15:09
That wasn't immediately apparent in the question. I just ran with the example :)
– Onno
May 23 '13 at 15:11
I use this approach too (but without the cute intros) -- group related technologies, and let the misc fall into an "other" line at the end.
– Monica Cellio♦
May 23 '13 at 15:39
 |Â
show 3 more comments
up vote
4
down vote
I often receive CVs with long lists of skills, and on further questioning find the applicant has only very basic knowledge of a claimed skill. They say "SQL"; they mean "I once saw a database on TV".
When I see such a list, I normally know at least two or three of the technologies in depth and will ask a couple of pointed technical questions. Are you ready for that level of scrutiny? If you are - fair play; but my experience is that most aren't.
I realise that agents and HR can filter by keywords, so sometimes you have to do this. But for my hiring, you get a lot more credit for only claiming skills you truly have.
answered Sep 24 '13 at 17:03
paj28
948514
5
Thank you, however this doesn't actually answer the question and may be better as a comment if it can be shortened. That said, I would not list a skill or technology that I am not very comfortable working with :) I realize this often is not the case though.
– Rachel
Sep 24 '13 at 17:11
2
For a lot of candidates my answer does answer the question - make your list shorter
– paj28
Sep 24 '13 at 18:14
add a comment |Â
up vote
2
down vote
It all boils down to compact, neat and updated
If you are constructing the resume for a particular job then make sure the ones mentioned in the job requirements are easily found. If the requirements spell out Visual Basic for Applications then say Visual Basic for Applications (VBA), if they say VBA don't spell it out. Many companies use software to search for the key words. Also consider putting the most relevant at the start/top of the list so a human doesn't miss it.
Also if they specify a particular version, e.g 10.X , don't say 8.0+.
This is an easy part to let get stale, so you should review it every time you update the resume, or at least every year to make sure that nothing is skipped or out of date.
answered Sep 24 '13 at 12:20
mhoran_psprep
40.3k463144
add a comment |Â
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
22
down vote
accepted
I'm no hero when it comes to CVs, but there's a lot of .Net tech in that list. I'd list those in one line. That way you make most of the space available. You could opt to use some kind of matrix style. I'd still make some kind of distinction between the MS tech and the other techniques.
Something like:
.Net technologies and languages:
C#, VB.Net, WPF, WCF, ASP.Net. (IIS 7.5?)
Web technologies and languages:
Javascript, HTML and CSS.
I'm familiar with databases.
T-SQL. (Maybe MSQL2k8?)
If the DB stuff is a bit off you could recatagorize the 'web' to 'other'
If you catagorize the line with list of skills to fit some kind of structure, like: "languages, API's, markup languages, software stacks", the structure should be apparent to any human reader. The automated resume scanners just look for strings anyways, so I can't imagine that you'd get slammed by those on how you lay them out on the page.
I don't know how to do the formatting on SE, but you could even have two columns, each with a title and list the techs in a comma separated format like I just presented. That way you can save space without sacrificing structure.
answered May 23 '13 at 14:44
Onno
876717
this is what i do. But i don't have the cute "i'm familiar with databases". I just say "database technologies", "java", "front-end" & so on
– bharal
May 23 '13 at 15:01
What can I say? I like cute :)
– Onno
May 23 '13 at 15:07
Hrrmmm but there's some overlap. For example, ASP.Net and Silverlight (not listed) are both web technologies and .Net technologies. I like the idea of separating them by category though. I'll play around with different ways of arranging them like that and see what I come up with
– Rachel
May 23 '13 at 15:09
That wasn't immediately apparent in the question. I just ran with the example :)
– Onno
May 23 '13 at 15:11
I use this approach too (but without the cute intros) -- group related technologies, and let the misc fall into an "other" line at the end.
– Monica Cellio♦
May 23 '13 at 15:39
 |Â
show 3 more comments
up vote
22
down vote
accepted
I'm no hero when it comes to CVs, but there's a lot of .Net tech in that list. I'd list those in one line. That way you make most of the space available. You could opt to use some kind of matrix style. I'd still make some kind of distinction between the MS tech and the other techniques.
Something like:
.Net technologies and languages:
C#, VB.Net, WPF, WCF, ASP.Net. (IIS 7.5?)
Web technologies and languages:
Javascript, HTML and CSS.
I'm familiar with databases.
T-SQL. (Maybe MSQL2k8?)
If the DB stuff is a bit off you could recatagorize the 'web' to 'other'
If you catagorize the line with list of skills to fit some kind of structure, like: "languages, API's, markup languages, software stacks", the structure should be apparent to any human reader. The automated resume scanners just look for strings anyways, so I can't imagine that you'd get slammed by those on how you lay them out on the page.
I don't know how to do the formatting on SE, but you could even have two columns, each with a title and list the techs in a comma separated format like I just presented. That way you can save space without sacrificing structure.
answered May 23 '13 at 14:44
Onno
876717
this is what i do. But i don't have the cute "i'm familiar with databases". I just say "database technologies", "java", "front-end" & so on
– bharal
May 23 '13 at 15:01
What can I say? I like cute :)
– Onno
May 23 '13 at 15:07
Hrrmmm but there's some overlap. For example, ASP.Net and Silverlight (not listed) are both web technologies and .Net technologies. I like the idea of separating them by category though. I'll play around with different ways of arranging them like that and see what I come up with
– Rachel
May 23 '13 at 15:09
That wasn't immediately apparent in the question. I just ran with the example :)
– Onno
May 23 '13 at 15:11
I use this approach too (but without the cute intros) -- group related technologies, and let the misc fall into an "other" line at the end.
– Monica Cellio♦
May 23 '13 at 15:39
 |Â
show 3 more comments
up vote
22
down vote
accepted
up vote
22
down vote
accepted
I'm no hero when it comes to CVs, but there's a lot of .Net tech in that list. I'd list those in one line. That way you make most of the space available. You could opt to use some kind of matrix style. I'd still make some kind of distinction between the MS tech and the other techniques.
Something like:
.Net technologies and languages:
C#, VB.Net, WPF, WCF, ASP.Net. (IIS 7.5?)
Web technologies and languages:
Javascript, HTML and CSS.
I'm familiar with databases.
T-SQL. (Maybe MSQL2k8?)
If the DB stuff is a bit off you could recatagorize the 'web' to 'other'
If you catagorize the line with list of skills to fit some kind of structure, like: "languages, API's, markup languages, software stacks", the structure should be apparent to any human reader. The automated resume scanners just look for strings anyways, so I can't imagine that you'd get slammed by those on how you lay them out on the page.
I don't know how to do the formatting on SE, but you could even have two columns, each with a title and list the techs in a comma separated format like I just presented. That way you can save space without sacrificing structure.
answered May 23 '13 at 14:44
Onno
876717
I'm no hero when it comes to CVs, but there's a lot of .Net tech in that list. I'd list those in one line. That way you make most of the space available. You could opt to use some kind of matrix style. I'd still make some kind of distinction between the MS tech and the other techniques.
Something like:
.Net technologies and languages:
C#, VB.Net, WPF, WCF, ASP.Net. (IIS 7.5?)
Web technologies and languages:
Javascript, HTML and CSS.
I'm familiar with databases.
T-SQL. (Maybe MSQL2k8?)
If the DB stuff is a bit off you could recatagorize the 'web' to 'other'
If you catagorize the line with list of skills to fit some kind of structure, like: "languages, API's, markup languages, software stacks", the structure should be apparent to any human reader. The automated resume scanners just look for strings anyways, so I can't imagine that you'd get slammed by those on how you lay them out on the page.
I don't know how to do the formatting on SE, but you could even have two columns, each with a title and list the techs in a comma separated format like I just presented. That way you can save space without sacrificing structure.
answered May 23 '13 at 14:44
Onno
876717
edited May 24 '13 at 16:01
answered May 23 '13 at 14:44
Onno
876717
answered May 23 '13 at 14:44
Onno
876717
answered May 23 '13 at 14:44
Onno
876717
876717
this is what i do. But i don't have the cute "i'm familiar with databases". I just say "database technologies", "java", "front-end" & so on
– bharal
May 23 '13 at 15:01
What can I say? I like cute :)
– Onno
May 23 '13 at 15:07
Hrrmmm but there's some overlap. For example, ASP.Net and Silverlight (not listed) are both web technologies and .Net technologies. I like the idea of separating them by category though. I'll play around with different ways of arranging them like that and see what I come up with
– Rachel
May 23 '13 at 15:09
That wasn't immediately apparent in the question. I just ran with the example :)
– Onno
May 23 '13 at 15:11
I use this approach too (but without the cute intros) -- group related technologies, and let the misc fall into an "other" line at the end.
– Monica Cellio♦
May 23 '13 at 15:39
 |Â
show 3 more comments
this is what i do. But i don't have the cute "i'm familiar with databases". I just say "database technologies", "java", "front-end" & so on
– bharal
May 23 '13 at 15:01
What can I say? I like cute :)
– Onno
May 23 '13 at 15:07
Hrrmmm but there's some overlap. For example, ASP.Net and Silverlight (not listed) are both web technologies and .Net technologies. I like the idea of separating them by category though. I'll play around with different ways of arranging them like that and see what I come up with
– Rachel
May 23 '13 at 15:09
That wasn't immediately apparent in the question. I just ran with the example :)
– Onno
May 23 '13 at 15:11
I use this approach too (but without the cute intros) -- group related technologies, and let the misc fall into an "other" line at the end.
– Monica Cellio♦
May 23 '13 at 15:39
this is what i do. But i don't have the cute "i'm familiar with databases". I just say "database technologies", "java", "front-end" & so on
– bharal
May 23 '13 at 15:01
this is what i do. But i don't have the cute "i'm familiar with databases". I just say "database technologies", "java", "front-end" & so on
– bharal
May 23 '13 at 15:01
What can I say? I like cute :)
– Onno
May 23 '13 at 15:07
What can I say? I like cute :)
– Onno
May 23 '13 at 15:07
Hrrmmm but there's some overlap. For example, ASP.Net and Silverlight (not listed) are both web technologies and .Net technologies. I like the idea of separating them by category though. I'll play around with different ways of arranging them like that and see what I come up with
– Rachel
May 23 '13 at 15:09
Hrrmmm but there's some overlap. For example, ASP.Net and Silverlight (not listed) are both web technologies and .Net technologies. I like the idea of separating them by category though. I'll play around with different ways of arranging them like that and see what I come up with
– Rachel
May 23 '13 at 15:09
That wasn't immediately apparent in the question. I just ran with the example :)
– Onno
May 23 '13 at 15:11
That wasn't immediately apparent in the question. I just ran with the example :)
– Onno
May 23 '13 at 15:11
I use this approach too (but without the cute intros) -- group related technologies, and let the misc fall into an "other" line at the end.
– Monica Cellio♦
May 23 '13 at 15:39
I use this approach too (but without the cute intros) -- group related technologies, and let the misc fall into an "other" line at the end.
– Monica Cellio♦
May 23 '13 at 15:39
 |Â
show 3 more comments
up vote
4
down vote
I often receive CVs with long lists of skills, and on further questioning find the applicant has only very basic knowledge of a claimed skill. They say "SQL"; they mean "I once saw a database on TV".
When I see such a list, I normally know at least two or three of the technologies in depth and will ask a couple of pointed technical questions. Are you ready for that level of scrutiny? If you are - fair play; but my experience is that most aren't.
I realise that agents and HR can filter by keywords, so sometimes you have to do this. But for my hiring, you get a lot more credit for only claiming skills you truly have.
answered Sep 24 '13 at 17:03
paj28
948514
5
Thank you, however this doesn't actually answer the question and may be better as a comment if it can be shortened. That said, I would not list a skill or technology that I am not very comfortable working with :) I realize this often is not the case though.
– Rachel
Sep 24 '13 at 17:11
2
For a lot of candidates my answer does answer the question - make your list shorter
– paj28
Sep 24 '13 at 18:14
add a comment |Â
up vote
4
down vote
I often receive CVs with long lists of skills, and on further questioning find the applicant has only very basic knowledge of a claimed skill. They say "SQL"; they mean "I once saw a database on TV".
When I see such a list, I normally know at least two or three of the technologies in depth and will ask a couple of pointed technical questions. Are you ready for that level of scrutiny? If you are - fair play; but my experience is that most aren't.
I realise that agents and HR can filter by keywords, so sometimes you have to do this. But for my hiring, you get a lot more credit for only claiming skills you truly have.
answered Sep 24 '13 at 17:03
paj28
948514
5
Thank you, however this doesn't actually answer the question and may be better as a comment if it can be shortened. That said, I would not list a skill or technology that I am not very comfortable working with :) I realize this often is not the case though.
– Rachel
Sep 24 '13 at 17:11
2
For a lot of candidates my answer does answer the question - make your list shorter
– paj28
Sep 24 '13 at 18:14
add a comment |Â
up vote
4
down vote
up vote
4
down vote
I often receive CVs with long lists of skills, and on further questioning find the applicant has only very basic knowledge of a claimed skill. They say "SQL"; they mean "I once saw a database on TV".
When I see such a list, I normally know at least two or three of the technologies in depth and will ask a couple of pointed technical questions. Are you ready for that level of scrutiny? If you are - fair play; but my experience is that most aren't.
I realise that agents and HR can filter by keywords, so sometimes you have to do this. But for my hiring, you get a lot more credit for only claiming skills you truly have.
answered Sep 24 '13 at 17:03
paj28
948514
I often receive CVs with long lists of skills, and on further questioning find the applicant has only very basic knowledge of a claimed skill. They say "SQL"; they mean "I once saw a database on TV".
When I see such a list, I normally know at least two or three of the technologies in depth and will ask a couple of pointed technical questions. Are you ready for that level of scrutiny? If you are - fair play; but my experience is that most aren't.
I realise that agents and HR can filter by keywords, so sometimes you have to do this. But for my hiring, you get a lot more credit for only claiming skills you truly have.
answered Sep 24 '13 at 17:03
paj28
948514
answered Sep 24 '13 at 17:03
paj28
948514
answered Sep 24 '13 at 17:03
paj28
948514
answered Sep 24 '13 at 17:03
paj28
948514
948514
5
Thank you, however this doesn't actually answer the question and may be better as a comment if it can be shortened. That said, I would not list a skill or technology that I am not very comfortable working with :) I realize this often is not the case though.
– Rachel
Sep 24 '13 at 17:11
2
For a lot of candidates my answer does answer the question - make your list shorter
– paj28
Sep 24 '13 at 18:14
add a comment |Â
5
Thank you, however this doesn't actually answer the question and may be better as a comment if it can be shortened. That said, I would not list a skill or technology that I am not very comfortable working with :) I realize this often is not the case though.
– Rachel
Sep 24 '13 at 17:11
2
For a lot of candidates my answer does answer the question - make your list shorter
– paj28
Sep 24 '13 at 18:14
5
5
Thank you, however this doesn't actually answer the question and may be better as a comment if it can be shortened. That said, I would not list a skill or technology that I am not very comfortable working with :) I realize this often is not the case though.
– Rachel
Sep 24 '13 at 17:11
Thank you, however this doesn't actually answer the question and may be better as a comment if it can be shortened. That said, I would not list a skill or technology that I am not very comfortable working with :) I realize this often is not the case though.
– Rachel
Sep 24 '13 at 17:11
2
2
For a lot of candidates my answer does answer the question - make your list shorter
– paj28
Sep 24 '13 at 18:14
For a lot of candidates my answer does answer the question - make your list shorter
– paj28
Sep 24 '13 at 18:14
add a comment |Â
up vote
2
down vote
It all boils down to compact, neat and updated
If you are constructing the resume for a particular job then make sure the ones mentioned in the job requirements are easily found. If the requirements spell out Visual Basic for Applications then say Visual Basic for Applications (VBA), if they say VBA don't spell it out. Many companies use software to search for the key words. Also consider putting the most relevant at the start/top of the list so a human doesn't miss it.
Also if they specify a particular version, e.g 10.X , don't say 8.0+.
This is an easy part to let get stale, so you should review it every time you update the resume, or at least every year to make sure that nothing is skipped or out of date.
answered Sep 24 '13 at 12:20
mhoran_psprep
40.3k463144
add a comment |Â
up vote
2
down vote
It all boils down to compact, neat and updated
If you are constructing the resume for a particular job then make sure the ones mentioned in the job requirements are easily found. If the requirements spell out Visual Basic for Applications then say Visual Basic for Applications (VBA), if they say VBA don't spell it out. Many companies use software to search for the key words. Also consider putting the most relevant at the start/top of the list so a human doesn't miss it.
Also if they specify a particular version, e.g 10.X , don't say 8.0+.
This is an easy part to let get stale, so you should review it every time you update the resume, or at least every year to make sure that nothing is skipped or out of date.
answered Sep 24 '13 at 12:20
mhoran_psprep
40.3k463144
add a comment |Â
up vote
2
down vote
up vote
2
down vote
It all boils down to compact, neat and updated
If you are constructing the resume for a particular job then make sure the ones mentioned in the job requirements are easily found. If the requirements spell out Visual Basic for Applications then say Visual Basic for Applications (VBA), if they say VBA don't spell it out. Many companies use software to search for the key words. Also consider putting the most relevant at the start/top of the list so a human doesn't miss it.
Also if they specify a particular version, e.g 10.X , don't say 8.0+.
This is an easy part to let get stale, so you should review it every time you update the resume, or at least every year to make sure that nothing is skipped or out of date.
answered Sep 24 '13 at 12:20
mhoran_psprep
40.3k463144
It all boils down to compact, neat and updated
If you are constructing the resume for a particular job then make sure the ones mentioned in the job requirements are easily found. If the requirements spell out Visual Basic for Applications then say Visual Basic for Applications (VBA), if they say VBA don't spell it out. Many companies use software to search for the key words. Also consider putting the most relevant at the start/top of the list so a human doesn't miss it.
Also if they specify a particular version, e.g 10.X , don't say 8.0+.
This is an easy part to let get stale, so you should review it every time you update the resume, or at least every year to make sure that nothing is skipped or out of date.
answered Sep 24 '13 at 12:20
mhoran_psprep
40.3k463144
edited Sep 24 '13 at 12:49
answered Sep 24 '13 at 12:20
mhoran_psprep
40.3k463144
answered Sep 24 '13 at 12:20
mhoran_psprep
40.3k463144
answered Sep 24 '13 at 12:20
mhoran_psprep
40.3k463144
40.3k463144
add a comment |Â
add a comment |Â
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%2f11938%2fhow-should-i-list-my-programming-technologies-on-a-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
2
Btw, this isn't at all specific to programming, I think this applies for anyone with a lot of skills (CAD, design, etc).
– Elysian Fields♦
May 23 '13 at 14:37
I list mine in a two column "table" (I quote because it's not formatted as a table, just tabbed out that way). For readability, I would say definitely go with a table. The bulleted list takes up way too much valuable space, and the sentence structure doesn't given enough visibility.
– Dave Johnson
May 23 '13 at 14:42
Maybe it's a good idea to add versions to some of the techs you are familiar with? (C# has changed a bit over time. The abilities of CSS have really changed over time)
– Onno
May 23 '13 at 14:48
Alphabetical list makes it easier to find something they're looking for and it avoids making an impression that one technology is "more important" than another
– Brandin
Jul 31 '14 at 6:15
1
@gnat I agree the questions may be similar, however I prefer the answers given to this one over the one you linked. Of course, I may be biased since I accepted this answer, but if others think so too I'd rather see that one closed as a duplicate to this one instead of vise versa, or the answers merged.
– Rachel
Oct 28 '14 at 11:55