4 ms·
At this point I'm mostly involved in hiring senior people (Senior Developers, Principals, Architects, etc). I definitely should modulate my claims by saying th
by gilbetron 9y ago
At this point I'm mostly involved in hiring senior people (Senior Developers, Principals, Architects, etc). I definitely should modulate my claims by saying that a Junior level position is totally fine having a 1 pager, although I still like to see a couple page from them explaining what projects they've worked on.
The problem with short resumes is that it is easy to hide shallowness. While that is easy to fix in face-to-face interviews, that takes up a lot of time and $$$. If you have to give details about jobs and projects, it becomes more difficult to hide shallowness.
I once interviewed at "7 year C Developer". We brought the person in and after a bit of a chat, asked some basic interview question - build a linked list, or something. We said that you could assume you have a pointer only to the beginning of the list. The person stated, "well, I don't know much about pointers."
Interview over!
- DoreenMichele 9y agoThank you.
- pkaye 9y agoI don't how your last question relates to a resume length though. I had a candidate with referral, 28 years experience and a impressive resume. All my colleagues were intimidated to ask him coding questions and he tried to weasel away from that but I insisted he do a quick C linked-list insert question and he said he didn't know much about pointers either. And things started falling apart from there. Some of these people are very good at deflecting questions and guiding the conversation so you know nothing about them in the end except what is in their stellar resumes.
- gilbetron 9y agoIt doesn't prevent lying (or "exaggerating"), but it takes more work to fill in details for a long resume, that's all.