Do you include easter eggs in your résumé?
-
Mine is 13 pages. As ridiculous as that sounds, I get a very high interview rate and usually before I show up they know if they want me or not. I did it that way because I have been a hiring manager for many positions and you have so little to go on from a 1 page resume and cover letter. With mine, what they see is what they get. I use a skills grid to indicate my level of knowledge for various technologies using this key: Basic knowledge: I have researched this topic; or I haven’t used this technology, but I’d like an opportunity to; or I have used this for less than 6 months; or I could discuss it at a cocktail party. Applied knowledge: I have used this in one or more projects; or I have used this for less than 2 years. Advanced knowledge: I use this regularly in projects; or I have been using this for 2–5 years; or with some preparation, I would feel comfortable speaking about this topic to a general audience. Expert knowledge: This is a core technology in my projects; or I have been using this for 5+ years; or I have written or spoken to this topic; or with some preparation, I would feel comfortable speaking about this to an audience of my peers. For example, I have expert knowledge of C# and basic knowledge of Objective-C. People appreciate the no-BS approach.
Good Lord. A 13 page resume is the opposite of a "no-BS approach"
-
I don't, my full CV is like 4 pages. But I don't usually use it when it comes to send it somewhere. Why? My experience is in three big and very different areas: Automation, Robotics and High-Level programming If I send it as it is, most of the companies would get scared or think I am over-qualified. Conclusion: I adapt it and take all easter eggs away, if they are not relevant for the future reader.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
I've had to clear half the content off my CV because few companies took me seriously. I've been coding most of my life (started age 8) and started teaching at age 13. Explaining everything that happened before I started coding commercially takes longer than proving that I can do the job I'm applying for.
My plan is to live forever ... so far so good
-
Mine includes expert-level knowledge of IPoAC. Sadly no one has asked about it yet :(
I must admit that I never heard of IPoAC before and had to go look for it, but I think it's hilarious, yet makes you think. :thumbsup:
My plan is to live forever ... so far so good
-
I must admit that I never heard of IPoAC before and had to go look for it, but I think it's hilarious, yet makes you think. :thumbsup:
My plan is to live forever ... so far so good
I have an Easter Egg on my Linked-in profile. It's an encrypted message(string of apparent garbage). Nobody has told me they cracked it yet, but I have been approached by certain people of a Cheltenham disposition trying to offer me a job. As I would hate going through the DV process I turned them down. Besides, they are far too naughty.https://www.youtube.com/watch?v=GvGHIW3GQv8[^] As for interviews, when I was doing them I took a netbook running Linux with a selection of Mono C# demo projects including face-detection and capture and simple encryption. It seemed to help with serious players. :-D
-
PIEBALDconsult wrote:
A résumé just isn't worth the effort.
Aw, they're great to make a pre-selection. Correct address? If no, into the bucket it goes. Comic Sans? -> into the bucket More than four pages? -> into the bucket More than four colors? -> into the bucket And yes, if you have to work through a hundred of them, you'd be rewarding the minimalistic style most.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
That is exactly what I was describing above. Good "resume" ;P
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
Mine includes expert-level knowledge of IPoAC. Sadly no one has asked about it yet :(
That only gets a response if you apply for jobs in Europe or Africa.
I wanna be a eunuchs developer! Pass me a bread knife!
-
Mine includes expert-level knowledge of IPoAC. Sadly no one has asked about it yet :(
I don't have a resume or a CV and I don't think that I ever had one. Guess this comes from working for the same company for so long. Easter eggs is something that I have always done though. Everything that I have written has Easter eggs within. Always have done and always will do. Oh and by the way wtf is IPoAC? Oh yeah and if I get retrenched, sacked or something I might need your help with a resume/CV with Easter eggs.
"Rock journalism is people who can't write interviewing people who can't talk for people who can't read." Frank Zappa 1980
-
I've had to clear half the content off my CV because few companies took me seriously. I've been coding most of my life (started age 8) and started teaching at age 13. Explaining everything that happened before I started coding commercially takes longer than proving that I can do the job I'm applying for.
My plan is to live forever ... so far so good
And we have a winner. The point of the Resume is to show what IMPACT you have had using your core skills. Not iterate through every nuance. I started in High School, getting paid to write software. I don't include that. TRS-DOS? GW-BASIC/BASCIA who cares nowadays. Your cover letter should tie your interest to their position, and introduce you, giving them a reason to read your resume. Having read thousands of resumes, I have NEVER appreciated a resume more than 3 pages, and prefer a 1 page resume. If you cannot SUMMARIZE, move on. Of course, my goals at interviewing are to make you cry, or wish you were working with us :-) [with the same set of questions]
-
I don't have a resume or a CV and I don't think that I ever had one. Guess this comes from working for the same company for so long. Easter eggs is something that I have always done though. Everything that I have written has Easter eggs within. Always have done and always will do. Oh and by the way wtf is IPoAC? Oh yeah and if I get retrenched, sacked or something I might need your help with a resume/CV with Easter eggs.
"Rock journalism is people who can't write interviewing people who can't talk for people who can't read." Frank Zappa 1980
-
I must admit that I never heard of IPoAC before and had to go look for it, but I think it's hilarious, yet makes you think. :thumbsup:
My plan is to live forever ... so far so good
It is funny, and the beauty is that due to the design of OPI layers, the air (layer 1) and birds (layer 2) are technically as valid as any other protocol, albeit with a very high error rate. RFC 2549[^] updates the protocol with a QoS component. As a layer 2 protocol it does not require any changes for IPv6.
-
Mine includes expert-level knowledge of IPoAC. Sadly no one has asked about it yet :(
I've seriously considered putting something like the resumes I have posted at job boards: "Please include the word "asparagus"* in the subject line to show that you've actually read my resume. If you do that, I guarantee a reply." Then if I get an unsolicited email about a job and it doesn't contain the word "asparagus" in the subject I know it's probably not worth reading.
-
Mine is 13 pages. As ridiculous as that sounds, I get a very high interview rate and usually before I show up they know if they want me or not. I did it that way because I have been a hiring manager for many positions and you have so little to go on from a 1 page resume and cover letter. With mine, what they see is what they get. I use a skills grid to indicate my level of knowledge for various technologies using this key: Basic knowledge: I have researched this topic; or I haven’t used this technology, but I’d like an opportunity to; or I have used this for less than 6 months; or I could discuss it at a cocktail party. Applied knowledge: I have used this in one or more projects; or I have used this for less than 2 years. Advanced knowledge: I use this regularly in projects; or I have been using this for 2–5 years; or with some preparation, I would feel comfortable speaking about this topic to a general audience. Expert knowledge: This is a core technology in my projects; or I have been using this for 5+ years; or I have written or spoken to this topic; or with some preparation, I would feel comfortable speaking about this to an audience of my peers. For example, I have expert knowledge of C# and basic knowledge of Objective-C. People appreciate the no-BS approach.
I really like the wording in your skills grid "Key". (I even linked to it in my blog). But I do think a thirteen page resume is excessive. Personally, I pride myself on maintaining a dense ONE-page resume. It requires exacting discipline to strip out every un-necessary word in order to keep it short and concise. But I try to treat my resume exactly like an elevator speech: Make every syllable count. (Unlike my blog, which conforms more to the Pascalian adage, “I would have written a shorter post, but I didn’t have the time.”)
-
Mine includes expert-level knowledge of IPoAC. Sadly no one has asked about it yet :(
I'm rather partial to chocolate myself. I went semi-retired a few years ago and only do word of mouth now. Even before doing that, I skinnied my resume to a single page letter of some three paragraphs with about five bullets in it. The resume I did use when I got a response left out the first 10 years or so, but was always tailored to the respondent. Why do that when five minutes of letter tailoring works. Ultimately, word of mouth is best, though. Let someone else supply the donuts.
RSW
-
I've seriously considered putting something like the resumes I have posted at job boards: "Please include the word "asparagus"* in the subject line to show that you've actually read my resume. If you do that, I guarantee a reply." Then if I get an unsolicited email about a job and it doesn't contain the word "asparagus" in the subject I know it's probably not worth reading.
Love it!
-
I really like the wording in your skills grid "Key". (I even linked to it in my blog). But I do think a thirteen page resume is excessive. Personally, I pride myself on maintaining a dense ONE-page resume. It requires exacting discipline to strip out every un-necessary word in order to keep it short and concise. But I try to treat my resume exactly like an elevator speech: Make every syllable count. (Unlike my blog, which conforms more to the Pascalian adage, “I would have written a shorter post, but I didn’t have the time.”)
The 13 pages makes a lot more sense if you see it, and is more like an academic CV I guess. It is structured like: Executive summary - 1 page Work Experience and Education - 1 page Skills grid Publications, awards, speaking engagements, open-source involvement portfolio of major/interesting projects If all you read is the first page, you'll know if we are both looking for the same thing. If so, you'll read the second page and so on. Therefore, I don't care if they make it to the last page, but if they do, I am definitely getting an interview, and they already know that they want me. I understand that people feel uncomfortable selling themselves, but an employee is a purchase/investment like any other. If you hand me a stack of fancy car brochures, I will probably look at the first page of each and decide I don't want a minivan or an SUV, then the remaining ones I'll open up and look at the main features. If one seems particularly appealing, I'll read the specs, warranty, available colours and options, etc. If I make it to the last page, I've probably already made my decision, whether I realize it or not.
-
:laugh: Thanks for the explanation. I would have never guessed. Pigeon English would be a suitable language for addressing IPoAC issues then I guess.
"Rock journalism is people who can't write interviewing people who can't talk for people who can't read." Frank Zappa 1980