|
Mine includes expert-level knowledge of IPoAC.
Sadly no one has asked about it yet 
|
|
|
|
|
Sounds like you're hoping to send them on a wild-goose chase... 
Anything that is unrelated to elephants is irrelephant
Anonymous
-----
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-----
I'd just like a chance to prove that money can't make me happy.
Me, all the time
|
|
|
|
|
Mine used to say I was a founder member of the school's Kabadi club.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|
|
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.
|
|
|
|
|
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.
|
|
|
|
|
Yvan Rodrigues wrote: I use a skills grid to indicate my level of knowledge for various technologies
using this key:
I do it as well.
But what I mean is:
If due to laboral experience, you are having more pages, then it is ok. Example: 2 years as hardware developer, then 3 years as IT-Manager, 5 years more as automation programmer... and you are now sending your resume to a technical lead manager in a company making engines... well that's where you worked to, so you should not hidden anything.
But, in germany, not "desired / matching" information can be as bad as no information at all. I mean, if the offer is for a robot programmer, saying that you are good with python or SQL has nothing to do with the job and can play against you.
Anther thing is that you get asked about your skills in the interview. Then I would explain about the "extra" knowledge as well. Should they ask "why didn't you put it in your CV?" My answer would be "I just wanted to focus in the most important skills for this job"
At least that was my experience when I was looking for a new job 6 years ago. But, as everything in this life, it might have evolved and be not accurated anymore.
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.
|
|
|
|
|
Good Lord.
A 13 page resume is the opposite of a "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.”)
|
|
|
|
|
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.
|
|
|
|
|
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]
|
|
|
|
|
No one asks for what you're expert in?
Do you find someone who comes and stands next to you and asks you, "Hey sir! Would you like to tell me, what you're best in?" - No!
You have to tell others that you're best in this. If you're best in that, make sure every one gets free Easter Eggs, so they can remember what you're best in. Include it in your resume to describe and make sure the person you're writing too knows you're good at it!
Favourite line: Throw me to them wolves and close the gate up. I am afraid of what will happen to them wolves - Eminem
~! Firewall !~
|
|
|
|
|
A résumé just isn't worth the effort. Do the minimum and be done with it.
|
|
|
|
|
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 
If you can't read my code, try converting it here[^]
|
|
|
|
|
That is exactly what I was describing above. Good "resume" 
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 haven't needed a CV in ages, but I note on mine that I'm a beer enthusiast ![Beer | [beer]](https://codeproject.freetls.fastly.net/script/Forums/Images/beer.gif)
|
|
|
|
|
Try putting * on easter eggs.
|
|
|
|
|
What's an easter egg like in a resume?
Not the picture of the MS Excel team by chance?
|
|
|
|
|
What sort of easter egg do you have in mind? And what is IPoAC? Does it have to do with birds?[^]
My "easter eggs" are 167 articles on CP, #1 author by article count, and 2 e-books (one pending, where is it anyways!!!)
And I'm still asked moronic interview questions (like, "what's your greatest weakness and what are you doing about it" to which, then next time I'm asked that, the answer will be "going through this interview and to fix that I'm hanging up on you -- CLICK) and requested to take idiotic tests in C#, .NET and SQL Server knowledge. Some of those questions are absurd.
The whole interview process so sucks nowadays. The people doing the interview don't even bother researching who the person is on the resume.
Marc
|
|
|
|
|
Yes, I'm referring to IP over Avian Carrier. I hope that they just think I'm trying to drop jargon, and actually read RFC 2549 or at least find the Wikipedia article. The RFC is a cute read if you don't mind puns. If they ask I can mention that I'm trying to teach the protocol to my finches, but for far have a 100% drop(ping) rate.
I agree -- I always do my homework about the company I am interviewing for, and if they are serious about hiring me, I hope they at least google me, which will lead them to my CP articles.
And then there are the tests.
I don't have a CS degree, and I don't have all of the big O notation optimizations memorized, but I do have 25+ years of experience and will gladly answer anything pragmatic.
I do use tests when hiring, but they are easy and are meant to screen out the BSers before they get an interview.
|
|
|
|
|
 That's because you didn't specify you have experience in:
IPoAVwQS ~ where "wQS" is with Quality of Service
|
|
|
|
|
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. 
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. 
|
|
|
|
|
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.
|
|
|
|
|
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!
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
