In my world it's pretty simple. I hire well paid professionals to get stuff done in a clear, concise manner as quickly and with as little intervention from me as possible. If the layout and text of your resume doesn't convey to me that you can do that then you will never get an interview. Getting an interview is the point of a resume, not to convey your life's work in multiple volumes. That's what coffee breaks are for after you get the job
In Eddie's case here the first page is his resume. The other pages are the 'telephone' interview. If they like what they see enough to have him come look the job over, that is the 'in person' interview.
How do I as the job seeker KNOW exactly what the hiring manager wants/needs?
I dont know. I will know they want X, Y and Z because it is listed as a required skill. But there might be other skills that they would like but do not realize or did not list.
I am not talking about having a hard to read book of a resume but one that shows relevant work experience. If a Manager is too lazy to read a couple pieces of paper that should only take them moments to first scan I don't want to work for them. Why waste MY time interviewing with them?
I have been on the job seeker and the job hirer side. NEVER, EVER when I was interviewing people did I have enough information on a resume in the corporate world. I always wanted MORE.
I have done back ground investigations in a non business environment on people. I know how much money the job seeker has made for years, their credit history/ratings, lists of references, friends, employers, and family. All get contacted and contacts are made from those contacts. What the job seeker states is checked and verified. In that job I have enough information about the job seeker.
By the time I graduate with a four year degree I had worked for the Federal government doing grunt computer work but also maintaining a district wide network. Created the process, bought the hardware, wrote the software, and implemented a anonymous employee survey across the district. The district was all of FLA south of the lake. Before "computer forensics" meant anything I was looking at computers siezed via a search warrant while CID was still rounding up people in the building.
I had also worked at a major computer company. The work for that company started in HR were I ordered and installed all of the PCs and other computer systems that they needed but never had. Which led to doing research about various issues. Which in turn got me a job working with a department of lobbyists to procure hardware and software as well as creating a database. Eventually I worked in hardware development and software development.
Oh, and I did some consulting on the side.
That quick summary would take a page and it has no details and I skipped a few things. No buzzwords.
Fill in what is needed to give more details and I think it was a three page resume.
The Coop office was using my resume as an example of what a resume should look like as well the value of a Coop work experience. I certainly had a wide range of experience before I got my sheep skin.
And I NEEDED every bit of it as well.
Thinking about what Eddie is doing actually helped ME.
I am creating my own website but I did not like it for some reason. I had done what Eddie had done to a certain extent but I was starting to split things into different pages. Looking at Eddie's "page" made it obvious what issues I had with my own page but yet could not quite figure out...
Another problem with websites is that some are just too complicated. They make you work too hard to get the info you for which you are searching. Or they are too fancy. They look good but no info. Just pretty pictures. They use too much Flash in both meanings of the word. The Disney website is a perfect example. Very well done. Lots of Flash. Music. Pretty Pictures. The website is a visual and sound work of art.
But finding information is a different story.
Later,
Dan
