1st know your audience. Is it going through a keyword scanner? Is a friend bringing it in? Even if it has to go through the scanner?
I'll have a keyword section at the end nowadays. I've heard of someone being passed over by the scanner for lack of "unix" even though they had "linux". They had a friend asking HR where it was. As someone who has done interviews, I don't care about the font, what kind of paper, etc. I might get a fax of it from the recruiter. I'll never see the original paper its on. When I say I below, I mean "The person reviewing your resume or interviewing you". It's not personal. I *do* care about how it is written. If it doesn't sum things up concisely, I'm less interested. You should be able to express your accomplishments appropriately. If you are not clear on your resume (where you've had time to work) I know you're not going to be clear when you have less time. Maybe there's something on your resume that might make me overlook that, but why take the chance? I might have gotten your resume from HR or my manager 10 minutes before I go in to see you. Or worse, be reading it as I walk in. How many interviewers hire the wrong one as a result? Do you want to work for someplace like this? This was very common in the dotcom era I found. I once turned down a 4th interview saying I had gotten another job. They begged me to come in because they had just fired the person I would replace. I politely did an interview, but they didn't notify the interviewers that I needed to be convinced to stay. On Tue, Apr 9, 2013 at 12:15 PM, Drew Van Zandt <drew.vanza...@gmail.com>wrote: > On the reviewing/receiving end, I generally find that unless it's a recent > grad, one page is insufficient for a technical resume, two is about right, > and a third page is generally only useful if the first two were pretty good. > > On the other end, I figure that's exactly what I'll write. Two pages of > meat, one page of e.g. nonprofessional experience that might be germane (I > have technical hobbies). > > Trying to write a one-page resume is unbearable. > > Again on the receiving end, if a resume from a recruiter looks like hell > but has a few interesting items, I'll sometimes email the prospect and ask > for a copy of their resume that has not been ruined by recruiters. > > To any engineering recruiters on the list: Don't screw up your guys' > resumes unless you are SURE you know what you're doing. It gets in the way > more often than not, in my experience. I don't want to hear YOUR voice or > get things in the format you think is important, I want to know what the > ENGINEER thinks is important, in their voice, because that's what I'll be > working with. > > Second/third putting education last unless you just graduated. Mine is > last except for a one-liner indicating I've had a Secret clearance before, > in case it's germane, and a standard references-on-request tag. > > * > Drew Van Zandt > Cam # US2010035593 (M:Liam Hopkins R: Bastian Rotgeld) > Domain Coordinator, MA-003-D. Masquerade aVST > * > > > On Tue, Apr 9, 2013 at 12:06 PM, David Hardy <belovedbold...@gmail.com>wrote: > >> I'm nearly sixty and have had a bunch of jobs over the decades, not all >> of them IT and not all of them Linux. So I tailor the resume to the >> specific position and keep it to two pages, max. I then expand on whatever >> in a cover letter and interview, if I get one. I've seen other peoples' >> resumes and it is as you describe; no consistency and everything from >> cryptic geek-speak acronyms to web-based sound-and-video productions to >> eight pages of small print listing the person's detailed life history. I >> have also help to edit/fix resumes for people and had them down to nice, >> concise, informative two-page deals and then they insisted I hadn't >> included enough info and gone back to their four- and six-page horrors and >> never got called for an interview thereafter, because....yes....the >> screening HR drones tossed them instantly. >> >> It is also worth noting that the last stat I saw on this indicated that >> there is a roughly four-percent retention and examination of resumes in >> general. The rest, 96%, are tossed. >> >> In my half-century of experience, jobs are gotten by getting via hook or >> crook to the hiring manager and showing them how you can help them/make >> their job easier. Period. >> >> Regards from northwestern Vermont, under the F-16s >> >> >> >> >> On Tue, Apr 9, 2013 at 11:49 AM, Kenny Lussier <kluss...@gmail.com>wrote: >> >>> Hi All, >>> >>> Not specifically Linux-related, but I was wondering what other people >>> are seeing/doing with resumes these days. I have seen everything from a >>> 2-page resume for someone with 20 years of experience to a 15-page resume >>> for someone with 2 jobs over 3 years (it looked like the output of cat >>> ~/.bash_history). How far back should a resume go? How long should it be >>> before you stop reading it? I'm seeing absolutely no consistency in >>> resumes, and the ones that come from recruiters seem to be the worst >>> formats. >>> >>> C-Ya, >>> Kenny >>> >>> >>> _______________________________________________ >>> gnhlug-discuss mailing list >>> gnhlug-discuss@mail.gnhlug.org >>> http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/ >>> >>> >> >> _______________________________________________ >> gnhlug-discuss mailing list >> gnhlug-discuss@mail.gnhlug.org >> http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/ >> >> > > _______________________________________________ > gnhlug-discuss mailing list > gnhlug-discuss@mail.gnhlug.org > http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/ > >
_______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
