Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

60%
+1 −0
Q&A What content parts should a technical (IT) CV have?

There are probably about as many ways to write a CV as there are people who have ever read or written at least one. You might want to include at least also an e-mail address in the contact details...

posted 13y ago by Canina‭  ·  edited 3y ago by Canina‭

Answer
#5: Post edited by user avatar Canina‭ · 2021-05-21T09:53:26Z (over 3 years ago)
  • There are probably about as many ways to write a CV as there are people who have ever read or written at least one.
  • You might want to include at least also an e-mail address in the contact details section.
  • One thing you would put into the Additional section (unless you add a specific section for it) is any (professional) references. I simply wrote a fairly generic "references are available upon request" under a separate heading in my CV; don't think I ever had anyone ask for them, though. Just be prepared for that someone _might_ ask.
  • In my CV I list specific work-related skills under each job, then towards the end have a short paragraph listing programming languages and technologies with which I have only non-professional experience, thus making it clear which is which as well as when I most recently worked professionally with each. (So, I have worked professionally with technology X for Y years, but only non-professionally with Z, but could probably get up to speed reasonably quickly if needed. I don't claim any real experience with M68k assembly, for instance, but I wouldn't get a deer-in-the-headlights look looking at such a source code listing either.)
  • Side by side with the generic skills list I also put in notable non-professional experiences. Be careful here, and don't overdo it, but some things that show that you aren't a complete workaholic might be beneficial. This probably depends a lot on the culture where you are applying for jobs.
  • In general, it's probably better to put in a little too much than a little too little, since you will almost certainly tailor the CV to each position (or at the very least company) anyway. It's easier to cut things out than to add more to make it match the position you are applying to, and cutting out is much faster than writing new if you find something interesting, giving you more time to focus on the personal letter where you can "sell" yourself to the company.
  • And like @JohnSmithers said, be honest.
  • There are probably about as many ways to write a CV as there are people who have ever read or written at least one.
  • You might want to include at least also an e-mail address in the contact details section.
  • One thing you would put into the Additional section (unless you add a specific section for it) is any (professional) references. I simply wrote a fairly generic "references are available upon request" under a separate heading in my CV; don't think I ever had anyone ask for them, though. Just be prepared for that someone _might_ ask.
  • In my CV I list specific work-related skills under each job, then towards the end have a short paragraph listing programming languages and technologies with which I have only non-professional experience, thus making it clear which is which as well as when I most recently worked professionally with each. (So, I have worked professionally with technology X for Y years, but only non-professionally with Z, but could probably get up to speed reasonably quickly if needed. I don't claim any real experience with M68k assembly, for instance, but I wouldn't get a deer-in-the-headlights look looking at such a source code listing either.)
  • Side by side with the generic skills list I also put in notable non-professional experiences. Be careful here, and don't overdo it, but some things that show that you aren't a complete workaholic might be beneficial. This probably depends a lot on the culture where you are applying for jobs.
  • In general, it's probably better to put in a little too much than a little too little, since you will almost certainly tailor the CV to each position (or at the very least company) anyway. It's easier to cut things out than to add more to make it match the position you are applying to, and cutting out is much faster than writing new if you find something interesting, giving you more time to focus on the personal letter where you can "sell" yourself to the company.
  • And of course, as pointed out in a previous answer: be honest.
#4: Attribution notice removed by user avatar System‭ · 2019-12-11T18:55:49Z (about 5 years ago)
Source: https://writers.stackexchange.com/a/4887
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#3: Attribution notice added by user avatar System‭ · 2019-12-08T02:09:14Z (about 5 years ago)
Source: https://writers.stackexchange.com/a/4887
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision by (deleted user) · 2019-12-08T02:09:14Z (about 5 years ago)
There are probably about as many ways to write a CV as there are people who have ever read or written at least one.

You might want to include at least also an e-mail address in the contact details section.

One thing you would put into the Additional section (unless you add a specific section for it) is any (professional) references. I simply wrote a fairly generic "references are available upon request" under a separate heading in my CV; don't think I ever had anyone ask for them, though. Just be prepared for that someone _might_ ask.

In my CV I list specific work-related skills under each job, then towards the end have a short paragraph listing programming languages and technologies with which I have only non-professional experience, thus making it clear which is which as well as when I most recently worked professionally with each. (So, I have worked professionally with technology X for Y years, but only non-professionally with Z, but could probably get up to speed reasonably quickly if needed. I don't claim any real experience with M68k assembly, for instance, but I wouldn't get a deer-in-the-headlights look looking at such a source code listing either.)

Side by side with the generic skills list I also put in notable non-professional experiences. Be careful here, and don't overdo it, but some things that show that you aren't a complete workaholic might be beneficial. This probably depends a lot on the culture where you are applying for jobs.

In general, it's probably better to put in a little too much than a little too little, since you will almost certainly tailor the CV to each position (or at the very least company) anyway. It's easier to cut things out than to add more to make it match the position you are applying to, and cutting out is much faster than writing new if you find something interesting, giving you more time to focus on the personal letter where you can "sell" yourself to the company.

And like @JohnSmithers said, be honest.

#1: Imported from external source by user avatar System‭ · 2012-01-25T14:51:20Z (almost 13 years ago)
Original score: 5