Is it good idea to shorten URLs in a CV?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
21
down vote
favorite
I want to place some links to projects I worked on in my CV. However some of these URLs are rather long. Is it good idea to shorten these URLs using on-line URL shorteners?
Is it common practice? Could CV full of URLs like "http://tinyurl.com/cqvga" potentially turn off potential employers?
resume
migrated from programmers.stackexchange.com Apr 29 '12 at 13:57
This question came from our site for professionals, academics, and students working within the systems development life cycle.
 |Â
show 3 more comments
up vote
21
down vote
favorite
I want to place some links to projects I worked on in my CV. However some of these URLs are rather long. Is it good idea to shorten these URLs using on-line URL shorteners?
Is it common practice? Could CV full of URLs like "http://tinyurl.com/cqvga" potentially turn off potential employers?
resume
migrated from programmers.stackexchange.com Apr 29 '12 at 13:57
This question came from our site for professionals, academics, and students working within the systems development life cycle.
1
That particular shortened URL might turn off many potential employers.
â Blrfl
Apr 29 '12 at 13:07
@Blfrl OK, used actual tinyurl instead as an example :)
â MatÃÂj Zábský
Apr 29 '12 at 13:17
1
Why would you want to? Why do you have URL's on your CV to begin with?
â IDrinkandIKnowThings
Apr 29 '12 at 13:59
Printed or electronic?
â Rarity
Apr 29 '12 at 16:08
4
If you have your own domain name, you can provide your own personalised URL shortener there. If the page you want isexample.net/blog/2012/04/05/this-post-has-a-long-title/
you could give the urlexample.net/tiny
, and have a redirect.
â TRiG
May 14 '12 at 19:22
 |Â
show 3 more comments
up vote
21
down vote
favorite
up vote
21
down vote
favorite
I want to place some links to projects I worked on in my CV. However some of these URLs are rather long. Is it good idea to shorten these URLs using on-line URL shorteners?
Is it common practice? Could CV full of URLs like "http://tinyurl.com/cqvga" potentially turn off potential employers?
resume
I want to place some links to projects I worked on in my CV. However some of these URLs are rather long. Is it good idea to shorten these URLs using on-line URL shorteners?
Is it common practice? Could CV full of URLs like "http://tinyurl.com/cqvga" potentially turn off potential employers?
resume
edited Apr 30 '12 at 8:53
yannis
4,21873464
4,21873464
asked Apr 29 '12 at 12:38
MatÃÂj Zábský
21126
21126
migrated from programmers.stackexchange.com Apr 29 '12 at 13:57
This question came from our site for professionals, academics, and students working within the systems development life cycle.
migrated from programmers.stackexchange.com Apr 29 '12 at 13:57
This question came from our site for professionals, academics, and students working within the systems development life cycle.
1
That particular shortened URL might turn off many potential employers.
â Blrfl
Apr 29 '12 at 13:07
@Blfrl OK, used actual tinyurl instead as an example :)
â MatÃÂj Zábský
Apr 29 '12 at 13:17
1
Why would you want to? Why do you have URL's on your CV to begin with?
â IDrinkandIKnowThings
Apr 29 '12 at 13:59
Printed or electronic?
â Rarity
Apr 29 '12 at 16:08
4
If you have your own domain name, you can provide your own personalised URL shortener there. If the page you want isexample.net/blog/2012/04/05/this-post-has-a-long-title/
you could give the urlexample.net/tiny
, and have a redirect.
â TRiG
May 14 '12 at 19:22
 |Â
show 3 more comments
1
That particular shortened URL might turn off many potential employers.
â Blrfl
Apr 29 '12 at 13:07
@Blfrl OK, used actual tinyurl instead as an example :)
â MatÃÂj Zábský
Apr 29 '12 at 13:17
1
Why would you want to? Why do you have URL's on your CV to begin with?
â IDrinkandIKnowThings
Apr 29 '12 at 13:59
Printed or electronic?
â Rarity
Apr 29 '12 at 16:08
4
If you have your own domain name, you can provide your own personalised URL shortener there. If the page you want isexample.net/blog/2012/04/05/this-post-has-a-long-title/
you could give the urlexample.net/tiny
, and have a redirect.
â TRiG
May 14 '12 at 19:22
1
1
That particular shortened URL might turn off many potential employers.
â Blrfl
Apr 29 '12 at 13:07
That particular shortened URL might turn off many potential employers.
â Blrfl
Apr 29 '12 at 13:07
@Blfrl OK, used actual tinyurl instead as an example :)
â MatÃÂj Zábský
Apr 29 '12 at 13:17
@Blfrl OK, used actual tinyurl instead as an example :)
â MatÃÂj Zábský
Apr 29 '12 at 13:17
1
1
Why would you want to? Why do you have URL's on your CV to begin with?
â IDrinkandIKnowThings
Apr 29 '12 at 13:59
Why would you want to? Why do you have URL's on your CV to begin with?
â IDrinkandIKnowThings
Apr 29 '12 at 13:59
Printed or electronic?
â Rarity
Apr 29 '12 at 16:08
Printed or electronic?
â Rarity
Apr 29 '12 at 16:08
4
4
If you have your own domain name, you can provide your own personalised URL shortener there. If the page you want is
example.net/blog/2012/04/05/this-post-has-a-long-title/
you could give the url example.net/tiny
, and have a redirect.â TRiG
May 14 '12 at 19:22
If you have your own domain name, you can provide your own personalised URL shortener there. If the page you want is
example.net/blog/2012/04/05/this-post-has-a-long-title/
you could give the url example.net/tiny
, and have a redirect.â TRiG
May 14 '12 at 19:22
 |Â
show 3 more comments
6 Answers
6
active
oldest
votes
up vote
27
down vote
accepted
No, I would not recommend shortened URLs in your CV.
Whether you're putting URLs to public profiles or to online projects on your CV, it's important to remember that people may or may not click on them at all -- and if it's a paper CV, people are unlikely to type them in -- at least on the first review of your materials.
However, what people may look for (and I know I do), is some indication of what those URLs are -- in this case, the domain name is a rhetorical device (it provides ethos). In other words, on first review of your materials I might not look at your LinkedIn or StackExchange profiles or GitHub repositories (for example), but knowing that you have a LinkedIn profile, you participate in the StackExchange community, and you contribute to or maintain open source repositories means something.
If you only use shortened URLs, I have no idea what is behind those shortened links, and thus the information that could be doing some good is doing no good at all.
Similarly, assume that I care enough to look at the information itself. If it's an online or electronic CV, I'll click the link; if it's a paper CV, I'll take the time to type the links. However, if you use shortened URLs, I have no idea where I'll be sent to. The cost-benefit analysis of typing a LinkedIn or SE URL and knowing where I'm going, versus a shorter link to somewhere unknown, just doesn't work out in the applicant's favor.
1
+1 If an applicant sent me a resume with shortened urls I would discard it immediately. If my barracuda ever stops one because I did not know what I was clicking then that is my failure to protect my company. And even worse if it misses one that we needed it to catch.
â IDrinkandIKnowThings
Apr 30 '12 at 12:32
add a comment |Â
up vote
11
down vote
Nobody, and I mean nobody will take the time to type in a URL that they see on a printed CV. So, from that perspective I say no because there's no point in putting the URLs there to begin with.
If you have an electronic CV, there's no point in shortening them because the user isn't going to type the URL in, either.
17
You just gave me a great idea
â Goran Jovic
Apr 29 '12 at 13:39
add a comment |Â
up vote
7
down vote
Speaking as someone who deals with this periodically, here's my impression about how I deal with URLs in a resume:
- I get an electronic copy of the resume and click or copy/paste. This generally only happens if you are fairly far through our process, since by that point you would have interviewed with HR and gotten through a phone screen.
- If it is clear you own the site I'll sometimes go to the parent page and see what else you have to say. This I'll occasionally type in, but I won't type anything beyond "blog.example.com" or github.com/yourname.
At no point do I type a full path, and I would pretty much never bother to type in bit.ly/whatever. I might click on it, but then the shortened URL doesn't buy you anything.
So the question is, who is your target when you put a shortened URL on your resume? You are targeting the person who a) wants to see whatever it is you are linking to but b) doesn't have an electronic copy of the resume and c) doesn't care about the information that gets lost when a resume is shortened (e.g., am I looking at a professional blog?) d) is better at typing a shorter-but-random string than a longer-but-nonrandom-string.
That seems like a relatively low margin game. Maybe in your industry or area that might be worth it, but I have trouble thinking that it would be a good idea in the general case.
add a comment |Â
up vote
2
down vote
To add a minor point to all of the excellent cautions above: there is no guarantee that a shortened URL is persistent. TinyURL and bit.ly seem to be doing fine right now, but I still remember my surprise when Tr.im shut down in 2009.
While this is a valid consideration for long-term documents, I'm not sure I'd consider a CV delivered to a company, particularly in response to a specific open position, "long term" by any means.
â Michael Kjörling
May 2 '12 at 8:49
1
@MichaelKjörling True, but in situations when resumes sit in job bank databases and are not updated, or recruiters get hold of electronic copies with old data, it is relevant (I've gotten plenty of resumes with outdated data, including dead URLs).
â jcmeloni
May 2 '12 at 10:35
1
@jcmeloni, In the age of recruiters spamming and cold-calling anyone they find on Dice.com, long after a resume has been removed from there, some might consider this a feature, not a bug.
â Stephan Branczyk
Jan 31 '14 at 12:29
add a comment |Â
up vote
1
down vote
The shortened URLs don't look professional and most people like me don't trust shortened URLs, although tinyurl
provides a preview, but I don't think anyone would do extra work for it.
Another drawback of using shortned URL is they are case sensitive in some of the site such as bit.ly and tinyurl, and people normally use lowercase while typing the url, ignoring the actual case, so it's another reason to use long URLs.
Another point of view may be (not sure if its true everywhere or not) but once an interviewer told me that they treat shortened URLs like internet memes and shorthands (like using 'U' instead of 'you').
If your project URls are too long, you can have a blog explaining your projects and can put the blog link in your CV. Another way would be to buy a good domain name and put a redirect in it. It might impress your interviewer too.
add a comment |Â
up vote
0
down vote
It might make a good impression if one is able to describe ones work in words (the fewer the better, as HR people don't have time anyway).
On the other hand, it might be of good service to the reader to include a single link to a webpage, e.g. johndoe.com/projects, where one can check out all the details.
If the CV is a .pdf, I would always use the URL as the link text, e.g. johndoe.com/projects and not "john's projects". This ensures that the link is valuable when the document is printed out.
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();
);
);
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
27
down vote
accepted
No, I would not recommend shortened URLs in your CV.
Whether you're putting URLs to public profiles or to online projects on your CV, it's important to remember that people may or may not click on them at all -- and if it's a paper CV, people are unlikely to type them in -- at least on the first review of your materials.
However, what people may look for (and I know I do), is some indication of what those URLs are -- in this case, the domain name is a rhetorical device (it provides ethos). In other words, on first review of your materials I might not look at your LinkedIn or StackExchange profiles or GitHub repositories (for example), but knowing that you have a LinkedIn profile, you participate in the StackExchange community, and you contribute to or maintain open source repositories means something.
If you only use shortened URLs, I have no idea what is behind those shortened links, and thus the information that could be doing some good is doing no good at all.
Similarly, assume that I care enough to look at the information itself. If it's an online or electronic CV, I'll click the link; if it's a paper CV, I'll take the time to type the links. However, if you use shortened URLs, I have no idea where I'll be sent to. The cost-benefit analysis of typing a LinkedIn or SE URL and knowing where I'm going, versus a shorter link to somewhere unknown, just doesn't work out in the applicant's favor.
1
+1 If an applicant sent me a resume with shortened urls I would discard it immediately. If my barracuda ever stops one because I did not know what I was clicking then that is my failure to protect my company. And even worse if it misses one that we needed it to catch.
â IDrinkandIKnowThings
Apr 30 '12 at 12:32
add a comment |Â
up vote
27
down vote
accepted
No, I would not recommend shortened URLs in your CV.
Whether you're putting URLs to public profiles or to online projects on your CV, it's important to remember that people may or may not click on them at all -- and if it's a paper CV, people are unlikely to type them in -- at least on the first review of your materials.
However, what people may look for (and I know I do), is some indication of what those URLs are -- in this case, the domain name is a rhetorical device (it provides ethos). In other words, on first review of your materials I might not look at your LinkedIn or StackExchange profiles or GitHub repositories (for example), but knowing that you have a LinkedIn profile, you participate in the StackExchange community, and you contribute to or maintain open source repositories means something.
If you only use shortened URLs, I have no idea what is behind those shortened links, and thus the information that could be doing some good is doing no good at all.
Similarly, assume that I care enough to look at the information itself. If it's an online or electronic CV, I'll click the link; if it's a paper CV, I'll take the time to type the links. However, if you use shortened URLs, I have no idea where I'll be sent to. The cost-benefit analysis of typing a LinkedIn or SE URL and knowing where I'm going, versus a shorter link to somewhere unknown, just doesn't work out in the applicant's favor.
1
+1 If an applicant sent me a resume with shortened urls I would discard it immediately. If my barracuda ever stops one because I did not know what I was clicking then that is my failure to protect my company. And even worse if it misses one that we needed it to catch.
â IDrinkandIKnowThings
Apr 30 '12 at 12:32
add a comment |Â
up vote
27
down vote
accepted
up vote
27
down vote
accepted
No, I would not recommend shortened URLs in your CV.
Whether you're putting URLs to public profiles or to online projects on your CV, it's important to remember that people may or may not click on them at all -- and if it's a paper CV, people are unlikely to type them in -- at least on the first review of your materials.
However, what people may look for (and I know I do), is some indication of what those URLs are -- in this case, the domain name is a rhetorical device (it provides ethos). In other words, on first review of your materials I might not look at your LinkedIn or StackExchange profiles or GitHub repositories (for example), but knowing that you have a LinkedIn profile, you participate in the StackExchange community, and you contribute to or maintain open source repositories means something.
If you only use shortened URLs, I have no idea what is behind those shortened links, and thus the information that could be doing some good is doing no good at all.
Similarly, assume that I care enough to look at the information itself. If it's an online or electronic CV, I'll click the link; if it's a paper CV, I'll take the time to type the links. However, if you use shortened URLs, I have no idea where I'll be sent to. The cost-benefit analysis of typing a LinkedIn or SE URL and knowing where I'm going, versus a shorter link to somewhere unknown, just doesn't work out in the applicant's favor.
No, I would not recommend shortened URLs in your CV.
Whether you're putting URLs to public profiles or to online projects on your CV, it's important to remember that people may or may not click on them at all -- and if it's a paper CV, people are unlikely to type them in -- at least on the first review of your materials.
However, what people may look for (and I know I do), is some indication of what those URLs are -- in this case, the domain name is a rhetorical device (it provides ethos). In other words, on first review of your materials I might not look at your LinkedIn or StackExchange profiles or GitHub repositories (for example), but knowing that you have a LinkedIn profile, you participate in the StackExchange community, and you contribute to or maintain open source repositories means something.
If you only use shortened URLs, I have no idea what is behind those shortened links, and thus the information that could be doing some good is doing no good at all.
Similarly, assume that I care enough to look at the information itself. If it's an online or electronic CV, I'll click the link; if it's a paper CV, I'll take the time to type the links. However, if you use shortened URLs, I have no idea where I'll be sent to. The cost-benefit analysis of typing a LinkedIn or SE URL and knowing where I'm going, versus a shorter link to somewhere unknown, just doesn't work out in the applicant's favor.
edited Apr 13 '17 at 12:48
Communityâ¦
1
1
answered Apr 29 '12 at 15:43
jcmeloni
21.6k87393
21.6k87393
1
+1 If an applicant sent me a resume with shortened urls I would discard it immediately. If my barracuda ever stops one because I did not know what I was clicking then that is my failure to protect my company. And even worse if it misses one that we needed it to catch.
â IDrinkandIKnowThings
Apr 30 '12 at 12:32
add a comment |Â
1
+1 If an applicant sent me a resume with shortened urls I would discard it immediately. If my barracuda ever stops one because I did not know what I was clicking then that is my failure to protect my company. And even worse if it misses one that we needed it to catch.
â IDrinkandIKnowThings
Apr 30 '12 at 12:32
1
1
+1 If an applicant sent me a resume with shortened urls I would discard it immediately. If my barracuda ever stops one because I did not know what I was clicking then that is my failure to protect my company. And even worse if it misses one that we needed it to catch.
â IDrinkandIKnowThings
Apr 30 '12 at 12:32
+1 If an applicant sent me a resume with shortened urls I would discard it immediately. If my barracuda ever stops one because I did not know what I was clicking then that is my failure to protect my company. And even worse if it misses one that we needed it to catch.
â IDrinkandIKnowThings
Apr 30 '12 at 12:32
add a comment |Â
up vote
11
down vote
Nobody, and I mean nobody will take the time to type in a URL that they see on a printed CV. So, from that perspective I say no because there's no point in putting the URLs there to begin with.
If you have an electronic CV, there's no point in shortening them because the user isn't going to type the URL in, either.
17
You just gave me a great idea
â Goran Jovic
Apr 29 '12 at 13:39
add a comment |Â
up vote
11
down vote
Nobody, and I mean nobody will take the time to type in a URL that they see on a printed CV. So, from that perspective I say no because there's no point in putting the URLs there to begin with.
If you have an electronic CV, there's no point in shortening them because the user isn't going to type the URL in, either.
17
You just gave me a great idea
â Goran Jovic
Apr 29 '12 at 13:39
add a comment |Â
up vote
11
down vote
up vote
11
down vote
Nobody, and I mean nobody will take the time to type in a URL that they see on a printed CV. So, from that perspective I say no because there's no point in putting the URLs there to begin with.
If you have an electronic CV, there's no point in shortening them because the user isn't going to type the URL in, either.
Nobody, and I mean nobody will take the time to type in a URL that they see on a printed CV. So, from that perspective I say no because there's no point in putting the URLs there to begin with.
If you have an electronic CV, there's no point in shortening them because the user isn't going to type the URL in, either.
answered Apr 29 '12 at 13:18
Bryan Oakley
562410
562410
17
You just gave me a great idea
â Goran Jovic
Apr 29 '12 at 13:39
add a comment |Â
17
You just gave me a great idea
â Goran Jovic
Apr 29 '12 at 13:39
17
17
You just gave me a great idea
â Goran Jovic
Apr 29 '12 at 13:39
You just gave me a great idea
â Goran Jovic
Apr 29 '12 at 13:39
add a comment |Â
up vote
7
down vote
Speaking as someone who deals with this periodically, here's my impression about how I deal with URLs in a resume:
- I get an electronic copy of the resume and click or copy/paste. This generally only happens if you are fairly far through our process, since by that point you would have interviewed with HR and gotten through a phone screen.
- If it is clear you own the site I'll sometimes go to the parent page and see what else you have to say. This I'll occasionally type in, but I won't type anything beyond "blog.example.com" or github.com/yourname.
At no point do I type a full path, and I would pretty much never bother to type in bit.ly/whatever. I might click on it, but then the shortened URL doesn't buy you anything.
So the question is, who is your target when you put a shortened URL on your resume? You are targeting the person who a) wants to see whatever it is you are linking to but b) doesn't have an electronic copy of the resume and c) doesn't care about the information that gets lost when a resume is shortened (e.g., am I looking at a professional blog?) d) is better at typing a shorter-but-random string than a longer-but-nonrandom-string.
That seems like a relatively low margin game. Maybe in your industry or area that might be worth it, but I have trouble thinking that it would be a good idea in the general case.
add a comment |Â
up vote
7
down vote
Speaking as someone who deals with this periodically, here's my impression about how I deal with URLs in a resume:
- I get an electronic copy of the resume and click or copy/paste. This generally only happens if you are fairly far through our process, since by that point you would have interviewed with HR and gotten through a phone screen.
- If it is clear you own the site I'll sometimes go to the parent page and see what else you have to say. This I'll occasionally type in, but I won't type anything beyond "blog.example.com" or github.com/yourname.
At no point do I type a full path, and I would pretty much never bother to type in bit.ly/whatever. I might click on it, but then the shortened URL doesn't buy you anything.
So the question is, who is your target when you put a shortened URL on your resume? You are targeting the person who a) wants to see whatever it is you are linking to but b) doesn't have an electronic copy of the resume and c) doesn't care about the information that gets lost when a resume is shortened (e.g., am I looking at a professional blog?) d) is better at typing a shorter-but-random string than a longer-but-nonrandom-string.
That seems like a relatively low margin game. Maybe in your industry or area that might be worth it, but I have trouble thinking that it would be a good idea in the general case.
add a comment |Â
up vote
7
down vote
up vote
7
down vote
Speaking as someone who deals with this periodically, here's my impression about how I deal with URLs in a resume:
- I get an electronic copy of the resume and click or copy/paste. This generally only happens if you are fairly far through our process, since by that point you would have interviewed with HR and gotten through a phone screen.
- If it is clear you own the site I'll sometimes go to the parent page and see what else you have to say. This I'll occasionally type in, but I won't type anything beyond "blog.example.com" or github.com/yourname.
At no point do I type a full path, and I would pretty much never bother to type in bit.ly/whatever. I might click on it, but then the shortened URL doesn't buy you anything.
So the question is, who is your target when you put a shortened URL on your resume? You are targeting the person who a) wants to see whatever it is you are linking to but b) doesn't have an electronic copy of the resume and c) doesn't care about the information that gets lost when a resume is shortened (e.g., am I looking at a professional blog?) d) is better at typing a shorter-but-random string than a longer-but-nonrandom-string.
That seems like a relatively low margin game. Maybe in your industry or area that might be worth it, but I have trouble thinking that it would be a good idea in the general case.
Speaking as someone who deals with this periodically, here's my impression about how I deal with URLs in a resume:
- I get an electronic copy of the resume and click or copy/paste. This generally only happens if you are fairly far through our process, since by that point you would have interviewed with HR and gotten through a phone screen.
- If it is clear you own the site I'll sometimes go to the parent page and see what else you have to say. This I'll occasionally type in, but I won't type anything beyond "blog.example.com" or github.com/yourname.
At no point do I type a full path, and I would pretty much never bother to type in bit.ly/whatever. I might click on it, but then the shortened URL doesn't buy you anything.
So the question is, who is your target when you put a shortened URL on your resume? You are targeting the person who a) wants to see whatever it is you are linking to but b) doesn't have an electronic copy of the resume and c) doesn't care about the information that gets lost when a resume is shortened (e.g., am I looking at a professional blog?) d) is better at typing a shorter-but-random string than a longer-but-nonrandom-string.
That seems like a relatively low margin game. Maybe in your industry or area that might be worth it, but I have trouble thinking that it would be a good idea in the general case.
answered Apr 29 '12 at 16:46
Hrafn
66443
66443
add a comment |Â
add a comment |Â
up vote
2
down vote
To add a minor point to all of the excellent cautions above: there is no guarantee that a shortened URL is persistent. TinyURL and bit.ly seem to be doing fine right now, but I still remember my surprise when Tr.im shut down in 2009.
While this is a valid consideration for long-term documents, I'm not sure I'd consider a CV delivered to a company, particularly in response to a specific open position, "long term" by any means.
â Michael Kjörling
May 2 '12 at 8:49
1
@MichaelKjörling True, but in situations when resumes sit in job bank databases and are not updated, or recruiters get hold of electronic copies with old data, it is relevant (I've gotten plenty of resumes with outdated data, including dead URLs).
â jcmeloni
May 2 '12 at 10:35
1
@jcmeloni, In the age of recruiters spamming and cold-calling anyone they find on Dice.com, long after a resume has been removed from there, some might consider this a feature, not a bug.
â Stephan Branczyk
Jan 31 '14 at 12:29
add a comment |Â
up vote
2
down vote
To add a minor point to all of the excellent cautions above: there is no guarantee that a shortened URL is persistent. TinyURL and bit.ly seem to be doing fine right now, but I still remember my surprise when Tr.im shut down in 2009.
While this is a valid consideration for long-term documents, I'm not sure I'd consider a CV delivered to a company, particularly in response to a specific open position, "long term" by any means.
â Michael Kjörling
May 2 '12 at 8:49
1
@MichaelKjörling True, but in situations when resumes sit in job bank databases and are not updated, or recruiters get hold of electronic copies with old data, it is relevant (I've gotten plenty of resumes with outdated data, including dead URLs).
â jcmeloni
May 2 '12 at 10:35
1
@jcmeloni, In the age of recruiters spamming and cold-calling anyone they find on Dice.com, long after a resume has been removed from there, some might consider this a feature, not a bug.
â Stephan Branczyk
Jan 31 '14 at 12:29
add a comment |Â
up vote
2
down vote
up vote
2
down vote
To add a minor point to all of the excellent cautions above: there is no guarantee that a shortened URL is persistent. TinyURL and bit.ly seem to be doing fine right now, but I still remember my surprise when Tr.im shut down in 2009.
To add a minor point to all of the excellent cautions above: there is no guarantee that a shortened URL is persistent. TinyURL and bit.ly seem to be doing fine right now, but I still remember my surprise when Tr.im shut down in 2009.
answered May 1 '12 at 18:26
sheepeeh
46626
46626
While this is a valid consideration for long-term documents, I'm not sure I'd consider a CV delivered to a company, particularly in response to a specific open position, "long term" by any means.
â Michael Kjörling
May 2 '12 at 8:49
1
@MichaelKjörling True, but in situations when resumes sit in job bank databases and are not updated, or recruiters get hold of electronic copies with old data, it is relevant (I've gotten plenty of resumes with outdated data, including dead URLs).
â jcmeloni
May 2 '12 at 10:35
1
@jcmeloni, In the age of recruiters spamming and cold-calling anyone they find on Dice.com, long after a resume has been removed from there, some might consider this a feature, not a bug.
â Stephan Branczyk
Jan 31 '14 at 12:29
add a comment |Â
While this is a valid consideration for long-term documents, I'm not sure I'd consider a CV delivered to a company, particularly in response to a specific open position, "long term" by any means.
â Michael Kjörling
May 2 '12 at 8:49
1
@MichaelKjörling True, but in situations when resumes sit in job bank databases and are not updated, or recruiters get hold of electronic copies with old data, it is relevant (I've gotten plenty of resumes with outdated data, including dead URLs).
â jcmeloni
May 2 '12 at 10:35
1
@jcmeloni, In the age of recruiters spamming and cold-calling anyone they find on Dice.com, long after a resume has been removed from there, some might consider this a feature, not a bug.
â Stephan Branczyk
Jan 31 '14 at 12:29
While this is a valid consideration for long-term documents, I'm not sure I'd consider a CV delivered to a company, particularly in response to a specific open position, "long term" by any means.
â Michael Kjörling
May 2 '12 at 8:49
While this is a valid consideration for long-term documents, I'm not sure I'd consider a CV delivered to a company, particularly in response to a specific open position, "long term" by any means.
â Michael Kjörling
May 2 '12 at 8:49
1
1
@MichaelKjörling True, but in situations when resumes sit in job bank databases and are not updated, or recruiters get hold of electronic copies with old data, it is relevant (I've gotten plenty of resumes with outdated data, including dead URLs).
â jcmeloni
May 2 '12 at 10:35
@MichaelKjörling True, but in situations when resumes sit in job bank databases and are not updated, or recruiters get hold of electronic copies with old data, it is relevant (I've gotten plenty of resumes with outdated data, including dead URLs).
â jcmeloni
May 2 '12 at 10:35
1
1
@jcmeloni, In the age of recruiters spamming and cold-calling anyone they find on Dice.com, long after a resume has been removed from there, some might consider this a feature, not a bug.
â Stephan Branczyk
Jan 31 '14 at 12:29
@jcmeloni, In the age of recruiters spamming and cold-calling anyone they find on Dice.com, long after a resume has been removed from there, some might consider this a feature, not a bug.
â Stephan Branczyk
Jan 31 '14 at 12:29
add a comment |Â
up vote
1
down vote
The shortened URLs don't look professional and most people like me don't trust shortened URLs, although tinyurl
provides a preview, but I don't think anyone would do extra work for it.
Another drawback of using shortned URL is they are case sensitive in some of the site such as bit.ly and tinyurl, and people normally use lowercase while typing the url, ignoring the actual case, so it's another reason to use long URLs.
Another point of view may be (not sure if its true everywhere or not) but once an interviewer told me that they treat shortened URLs like internet memes and shorthands (like using 'U' instead of 'you').
If your project URls are too long, you can have a blog explaining your projects and can put the blog link in your CV. Another way would be to buy a good domain name and put a redirect in it. It might impress your interviewer too.
add a comment |Â
up vote
1
down vote
The shortened URLs don't look professional and most people like me don't trust shortened URLs, although tinyurl
provides a preview, but I don't think anyone would do extra work for it.
Another drawback of using shortned URL is they are case sensitive in some of the site such as bit.ly and tinyurl, and people normally use lowercase while typing the url, ignoring the actual case, so it's another reason to use long URLs.
Another point of view may be (not sure if its true everywhere or not) but once an interviewer told me that they treat shortened URLs like internet memes and shorthands (like using 'U' instead of 'you').
If your project URls are too long, you can have a blog explaining your projects and can put the blog link in your CV. Another way would be to buy a good domain name and put a redirect in it. It might impress your interviewer too.
add a comment |Â
up vote
1
down vote
up vote
1
down vote
The shortened URLs don't look professional and most people like me don't trust shortened URLs, although tinyurl
provides a preview, but I don't think anyone would do extra work for it.
Another drawback of using shortned URL is they are case sensitive in some of the site such as bit.ly and tinyurl, and people normally use lowercase while typing the url, ignoring the actual case, so it's another reason to use long URLs.
Another point of view may be (not sure if its true everywhere or not) but once an interviewer told me that they treat shortened URLs like internet memes and shorthands (like using 'U' instead of 'you').
If your project URls are too long, you can have a blog explaining your projects and can put the blog link in your CV. Another way would be to buy a good domain name and put a redirect in it. It might impress your interviewer too.
The shortened URLs don't look professional and most people like me don't trust shortened URLs, although tinyurl
provides a preview, but I don't think anyone would do extra work for it.
Another drawback of using shortned URL is they are case sensitive in some of the site such as bit.ly and tinyurl, and people normally use lowercase while typing the url, ignoring the actual case, so it's another reason to use long URLs.
Another point of view may be (not sure if its true everywhere or not) but once an interviewer told me that they treat shortened URLs like internet memes and shorthands (like using 'U' instead of 'you').
If your project URls are too long, you can have a blog explaining your projects and can put the blog link in your CV. Another way would be to buy a good domain name and put a redirect in it. It might impress your interviewer too.
answered Apr 29 '12 at 17:34
noob
469421
469421
add a comment |Â
add a comment |Â
up vote
0
down vote
It might make a good impression if one is able to describe ones work in words (the fewer the better, as HR people don't have time anyway).
On the other hand, it might be of good service to the reader to include a single link to a webpage, e.g. johndoe.com/projects, where one can check out all the details.
If the CV is a .pdf, I would always use the URL as the link text, e.g. johndoe.com/projects and not "john's projects". This ensures that the link is valuable when the document is printed out.
add a comment |Â
up vote
0
down vote
It might make a good impression if one is able to describe ones work in words (the fewer the better, as HR people don't have time anyway).
On the other hand, it might be of good service to the reader to include a single link to a webpage, e.g. johndoe.com/projects, where one can check out all the details.
If the CV is a .pdf, I would always use the URL as the link text, e.g. johndoe.com/projects and not "john's projects". This ensures that the link is valuable when the document is printed out.
add a comment |Â
up vote
0
down vote
up vote
0
down vote
It might make a good impression if one is able to describe ones work in words (the fewer the better, as HR people don't have time anyway).
On the other hand, it might be of good service to the reader to include a single link to a webpage, e.g. johndoe.com/projects, where one can check out all the details.
If the CV is a .pdf, I would always use the URL as the link text, e.g. johndoe.com/projects and not "john's projects". This ensures that the link is valuable when the document is printed out.
It might make a good impression if one is able to describe ones work in words (the fewer the better, as HR people don't have time anyway).
On the other hand, it might be of good service to the reader to include a single link to a webpage, e.g. johndoe.com/projects, where one can check out all the details.
If the CV is a .pdf, I would always use the URL as the link text, e.g. johndoe.com/projects and not "john's projects". This ensures that the link is valuable when the document is printed out.
edited Jun 15 '12 at 4:10
answered Jun 14 '12 at 20:09
stefanl
111
111
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%2f1083%2fis-it-good-idea-to-shorten-urls-in-a-cv%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
1
That particular shortened URL might turn off many potential employers.
â Blrfl
Apr 29 '12 at 13:07
@Blfrl OK, used actual tinyurl instead as an example :)
â MatÃÂj Zábský
Apr 29 '12 at 13:17
1
Why would you want to? Why do you have URL's on your CV to begin with?
â IDrinkandIKnowThings
Apr 29 '12 at 13:59
Printed or electronic?
â Rarity
Apr 29 '12 at 16:08
4
If you have your own domain name, you can provide your own personalised URL shortener there. If the page you want is
example.net/blog/2012/04/05/this-post-has-a-long-title/
you could give the urlexample.net/tiny
, and have a redirect.â TRiG
May 14 '12 at 19:22