Resumes for New Grads?

CastrTroy asks: "I recently graduated from the software engineering program at the University of Ottawa. With 4 terms of experience, and good marks, I am still unable to even get interviews for jobs. What makes a good resume? I've gotten some good pointers from people I know, but it just doesn't seem to be working. Is there something that works really well for technically related jobs? What is a good way to include skills that I don't have on-the-job experience with? Some people say 3 pages is too much, while others say their resume is 25 pages. Are there any actual proven methods for writing good resumes, or is it all just hit and miss"

Comments

Language skills

[gokeln]

Fluency in Hindi.

You want to keep your resume

[foidulus]

as short as possible while still highlighting your skills. Remember, recruiters are busy people, and they usually spend a very small amount of time per resume(unless they are interested). Sometimes your resume may even get filtered out by computer.
Your best bet is to make a tight, targeted resume. Flooding monster or hotjobs with generic resumes probably won't get you very far. Find the jobs you think you are most suited for, and go for them! And of course, networkin never hurts either!
Happy hunting!

Keep it simple... but sell yourself with it.

[ChibiOne]

25 pages? A resume is supposed to give a glimpse of who you are (profesionally speaking), no to tell the story of your life since birth.

Keep it simple. And I don't mean cryptic. I mean, it must have a clean layout, nice itemized lists instead of clumsy paragraphs of post-modern crappy descriptions of your work. Of course, this doesn't mean you have to write a list like "tech support, programming in Java, computer mainteinance, bla1, bla2, bla3..." either.

Remember, you have to write something that can give the reader a grasp of who you are in 10 seconds. Otherwise, the whole thing will end up in the trash basket.

Cover letter!

[slappy]

It's not all about the resume, though the resume is very important. It's also about the cover letter. I just posted an ad today for a position, and while wading through resumes I've come to cherish the well-written cover letter. Some tips:

• Let me know you read the ad: reference the content of the ad.
• Tell me how you fit the bill: Choose one experience, one skill, or one attribute that meets the at least one of the requirements listed in the ad.
• Express (sincere) interest in the job: try to make it feel like you didn't just respond to this ad because you're desperate for any kind of interview.
• Don't send your cover letter as an attachment! It should be your email body. Really. I won't read an attached cover letter.

Make it easy on the hiring person, and you'll improve your chances on having your resume actually read -- and that is what will get you the interview.

Re:Cover letter!

[WarPresident]

Don't send your cover letter as an attachment! It should be your email body. Really. I won't read an attached cover letter.


I agree with everything except the above statement. Send it as an attachment and in the body of the email, referencing an enclosure of the cover letter.

Here's what happens at the place I work: After inHuman Resources gets done with initial screening, they print out a copy of the email and any attachments, stamp it and send it via interoffice mail to the hiring department. While the attachments are usually nicely formatted and generally in the style that a human being would care to read, the same cannot be said of the printout of the body of the email. One person in HR apparently sets the text to 16pt for easy reading and prints it out that way. I've seen clipped sentences and far too much of the "System" or Courier 10pt emails. They never look good...

If you care enough about the position, ensure that you will be presenting your best face. About the only "safe" assumption you can make with emailing resumes is that your attachments should be Word documents unless otherwise stated. Oh yeah, and hit all the keywords for those companies that use HR as the initial screening process.

SE

[mtigges]

The problem is that your resume says Software Engineering.

Some Advice

[benwb]

For an entry level position just out of school you really need to keep your resume to one page. It sounds like you don't have a great deal of work experience, so you should probably put your academic experience first. If you took any particularly challenging classes you may want to break them out much like you would with challenging projects from a job.

In todays market you can probably expect to send out about a hundred resumes per interview. Work any friends and family that you have- even if they're just acquaintances. Start sending your resume to large corporations- they're always hiring, even if they haven't posted anything, and you may catch someone in the right mood.

Skills sections will show up on hits when recruiters do searches, but they tend to be ignored when your resume is actually sitting in front of a real person. Try to work any skills you have into the context in which you used them. If you implemented some stuff for fun definitely put in a section of personal projects. When I'm looking at fresh from college resumes that's a definite plus, as I know the person actually enjoys development.

Get the recruiter working too

[philntc]

Recruiters make money by selling you. In Canada anyway, they typically only get paid if they place you and you meet expectations. They benefit by from your resume being up to par.

Interview your recruiters closely, and talk to their previous hires. Get an idea of what worked before, and what the recruiter is willing to do to make you sellable (ie better resume). If you're worth it, they will help you.

Like any profession, some recruiters can be really good at what they do, and others can be just useless. Run in the opposite direction of the latter.

None

[UserChrisCanter4]

Here's what you need to worry about on your resume: Is everything spelled correctly, laid out in a pleasing manner, one or two, three pages tops. In your situation, a resume doesn't matter.

Unless you were involved in some crazy groundbreaking research, went to an extremely prestigious school that will make a mark based on the name (Ivy League, Cal Tech/MIT/etc.), or work on some readily recognizable OSS in your spare time, your resume is about as good as it's going to get provided you follow the rules above.

Now for the fun part: Remember that cliche about "it isn't what you know, it's who you know?" It didn't achieve cliche status without having a bit of truth. Two of my friends graduated last Spring. One had a pretty good GPA and a degree in Chemical Engineering. Hadn't programmed since High School. He's now a consultant with Accenture, doing minor programming work on site for pretty nice cash, considering he's a first year employee. The other day he mentioned how one of the guys he had graduated with had a better GPA, better extra-curriculars, and sends out a shitload of resumes with no result (He was bemoaning the economy). I answered to him that the reason he ended up with that job was that he showed up everytime Accenture came to campus, be it for some random business school speaking engagement, or at career fairs. He came to be known by the guys there. The second friend graduated at the same time with a BS in EE. He spent about 5 months working on getting hired with one of about three different places, and now he works on the ISS at NASA. A third friend did approximately the same thing, and now works for the State Department (I think, long story but I suspect he works for a more clandestine side of the executive branch, but having had relatives in those positions I know he can't tell me if he does).

These guys are not geniuses, they both went to state schools (albeit good ones, and the third went Ivy League, so I consider his example less representative), and they're not the sort who were posting Summa Cum Laude grades at graduation. In short, they're probably just like you.

So what you need to do is this: Take a look at the companies operating in the region in which you want to be hired. Pick two or three good ones, and make sure to read up on corporate (or govt.) culture, benefits, etc. Know them well. Now start finding out ways to make contacts with the people there. Do their developers participate in some SIG around town? Go get to know them. Speak to guys who might be responsible for recommending a new-hire, but make sure you aren't hounding people. A lot of jobs aren't filled in a position->applicant order, but rather the other way around. In other words, a lot of times a team might need another hand, or a particular task that you're well suited at might need an entry-level programming position. The company probably wouldn't actively go and create a job advertisment, post on Monster.com, etc., but if one of the devs says, "hey, there's that guy I remember from the Linux/Graphics/Networking SIG who could probably help us out", the job will be "created".

At the risk of sounding like some crappy self-help speaker, when you're trying to get a job, you're essentially acting a salesperson, and the product you're selling is yourself. Right now, you're basically a commodity product, nothing but a slightly-better-than-average list of achievements on paper. Your job is to provide that extra push, in whatever way you can, to put yourself above commodity status.

Oh yeah, and please ditch that "objective: To obtain a position in..." section. God I wish those things would go away on resumes. Everyone of them is the same canned line that does nothing but take up space better devoted to anything.

Re:None

[sql*kitten]

First real job, right out of university: Walked into the office of a nearby startup ISP, asked if they needed a good UNIX systems programmer, interviewed by the CTO that afternoon, started the next week. Now, the thing is, I'd also been down the traditional route, sending out letters and CVs - but by the time any of them called, I'd already signed. Didn't hurt that I was friends-of-friends with a few of the other staff, tho' I didn't know it beforehand.

Second job: A friend called me, said he needed someone for a UNIX job, would I be interested? It was a cool company (at the time) so I interviewed with his manager, quit my first job and started a few weeks later. I'd outgrown the first job by then and had sent out letters and CVs - but by the time any of them called, I'd already signed. I was there 3.5 years. Converted my specialty from UNIX to Oracle while I was there.

Third job: A friend interviewed for a UNIX job, which she later turned down. The interviewer asked her on the way out if she knew any Oracle DBAs, he was hiring one of those too. She gave him my name, I interviewed with him when he was in my city, started a few days later. I'd been laid off from my second job in the NASDAQ meltdown and had sent out letters and CVs - but by the time any of them called, I'd already signed. I'm still there.

The moral of these 3 stories? It really is all about personal contacts. And I've done the same, a bunch of my friends have been hired through me too, either directly or through referrals. Skill in building networks of people is far more important than what most geeks think of when they think of networking.

Short resumes are a sign of a focused mind

[GuyMannDude]

as short as possible while still highlighting your skills. Remember, recruiters are busy people, and they usually spend a very small amount of time per resume(unless they are interested).

That's very true and there are other reasons for keeping your resume short. Quite frankly, if you cannot tell me the important things about yourself in a single page, I shudder to think of the mounds of documentation you will produce when I ask you to summarize your recent progress on the project you are working on. A succinct resume is a demonstration of your ability to quickly identify the most important parts of something (in this case: you) and communicate those clearly and effectively. I believe that a good resume indicates a focused mind and an ability to cut through the crap and get to the heart of what's important. In addition, when I see resumes over two pages, I get the impression that the applicant is trying to "snow" me with tons of crap. That s/he's trying to bowl me over with quantity rather than quality.

Your best bet is to make a tight, targeted resume.

Again, I agree. I'm baffled at how many people just stick a generic "goal" at the top of their resume. Something like "Seeking employment in a challenging field, allowing me to further develop my experience and capabilities" is just a bunch of crap. Who the hell doesn't want a job like that?

The cover letter can make a big difference as well. There was a recent slashdot story about handwriting and someone pointed out that a handwritten cover letter will make you stand out from the stack. That's something you might try. But definitely explain why you are interested in that particular company in your cover letter -- don't use a generic letter!

GMD

Re:Short resumes are a sign of a focused mind

[Jerf]

Again, I agree. I'm baffled at how many people just stick a generic "goal" at the top of their resume. Something like "Seeking employment in a challenging field, allowing me to further develop my experience and capabilities" is just a bunch of crap. Who the hell doesn't want a job like that?

As a matter of curiosity, what do you expect up there? How do you justify whatever answer you give in light of the fact that it all boils down to "I want the job you are offering" anyhow?

I'm an honest person. And while I know it's a disadvantage, I prefer to avoid bullshitting on my resume. Despite significant pondering, I've never managed to figure out what to put there. I've recently settled on "To become a respected software architect" but that still doesn't feel right on a number of levels. For one thing, at my level of experience, the odds of me still being in your company when I get to that point are pretty slim in this economy... although that's as likely to be your doing as mine.

For another, what do you care about my goals? I know a lot of companies claim to care but the evidence I've seen suggests otherwise.

Like I said, the only honest thing I've thought of to put in there is "I want to engage in a mutually beneficial relationship where I do a job and you pay me for it, and I'll worry about my own damn goals thank you; if I'm applying for this job you can be assured that I think it is meeting my needs and who are you to decide any differently?"... which of course gets PCed down to the aforementioned "To become a respected software architect".

... Maybe I should just say "I want to be your boss"?

The cover letter I do better with (plenty of experiences to draw from to customize a resume without guilt), as long as I manage to steer clear of the "career goals" issue, but it suffers the same problem: Asking people to talk about "the future" is just begging them to bullshit you, and that includes their hypothetical and malleable-anyways goals. Why not just stick with the past: Where you've worked, what you've accomplished, at most where you are headed right now, and leave vague references to "future goals" alone? Then I don't have to make up absurd rationalizations for "Food and shelter cost money."

Re:Short resumes are a sign of a focused mind

[Anonymous Coward]

Again, I agree. I'm baffled at how many people just stick a generic "goal" at the top of their resume. Something like "Seeking employment in a challenging field, allowing me to further develop my experience and capabilities" is just a bunch of crap. Who the hell doesn't want a job like that?

As a matter of curiosity, what do you expect up there? How do you justify whatever answer you give in light of the fact that it all boils down to "I want the job you are offering" anyhow?

What makes you think you need ANYTHING up there? Why not just leave off the Objective? That goes back to the idea of making your point using as little fluff as possible. If you can't put something really novel there -- and I confess I don't know what that would be -- then just leave it off. It's clutter. Don't just state an objective because everyone else does. This is a resume, not a form. It's your chance to express yourself. There aren't any hard-and-fast rules.

The cover letter I do better with (plenty of experiences to draw from to customize a resume without guilt), as long as I manage to steer clear of the "career goals" issue, but it suffers the same problem: Asking people to talk about "the future" is just begging them to bullshit you, and that includes their hypothetical and malleable-anyways goals. Why not just stick with the past: Where you've worked, what you've accomplished, at most where you are headed right now, and leave vague references to "future goals" alone? Then I don't have to make up absurd rationalizations for "Food and shelter cost money."

Questions about long-term goals are pretty stupid and shouldn't be asked. However, they are somewhat related to a much more important question: why are you interested in working for that company. Presemably, it's because you think working for them would be exciting. So, when people ask you about your future goals, you can talk about what types of projects you'd like to be working on. Or, better still, talk about what you'd like to see the company accomplish and feel like you contributed in no small part to that achievement.

Target for What you Want

[jgardn]

Target your resume for the job you want. Write a different resume tailored for each job you apply for. Be humble, yet confident, and only mention relevant skills.

Think: What do they want? What do I have that they want? Write down everything you can think of, and then turn it into a 30-second commercial slot. Pound on those few points solidly, and leave the rest as dressing. Avoid things they might not want. Definitely avoid negative things.

For instance, if I were applying for a software engineering position at, say, Microsoft, in C++. I would highlight all of the experience I had writing C++ code, emphasize the project's I've worked on, and bullet point the various things I've done in relation to coding. The "dressing" will be where I've worked (relevant places only -- NOT McDonald's), what college I've graduated from, what degree and what my GPA was, and what my other skills or hobbies are.

Think of your resume more as an ad: You have to hire me because I will bring your company $$$! Sell yourself!

Keep it short and sweet

[Chelloveck]

For someone fresh out of college with no work experience, there's absolutely no reason to have a resume that's more than one page. No offense, but you probably haven't done anything worth taking that much of the reviewer's time.

List your coursework and your strengths. Describe some of the relevant projects you've done for class. You can list summer-job type work experience, but if all of it was just flipping burgers don't dwell on it. On the other hand, if you've interned or done anything related to your field, play it up!

If you've done anything applicable outside of schoolwork, be sure to list that! That's what's going to catch someone's eye. When I'm looking at resumes I give top priority to people who have technical hobbies. It shows that they really like this stuff, and aren't merely going to be punching a clock.

Also, make sure you send out resumes. Lots of resumes. To anyone and everyone. I graduated in 1988 with a BSEE degree from a respected university. Jobs were easier to find then, but I still ended up sending out over 400 resumes. That netted me only a handful of interviews, and a huge pile of FOAD letters. You know how I got my first real job? Through a friend-of-a-friend, who happened to have also graduated from my school ten years before. That's right, in the end good ol' social networking gets you the most action.

All I can say is keep at it. Definitely get involved in some sort of activity related to the work you want to do, if only to keep your knowledge fresh. Send out lots of resumes. And especially, chat up your friends and see who's hiring.

Short and Focused

[mgoff]

As a new college grad, your resume should not be any longer than a single page. Screeners are spending less than a minute on each resume-- they're not going to waste time paging through tons of detail. Here's a few tips I think will help you be successful:

• Cusomize your resume as much as possible for every position. What industry is the company in? Highlight non-engineering experiences you have that would help you (as a programmer) in that sector. Of course, you don't have time to rewrite your resume for every employer, but a little tweaking (with the right buzzwords) can help your resume get a few more seconds of attention.
• Focus, focus, focus. Pretend you're the employer; do you really care that a candidate was a lifeguard in high school? Probably not. Do you care that he or she provided weekly status reports in his last internship? Again, probably not. Remember, resume screeners are skimming your resume. They're not going to read every word. Make sure that most of the words on there are valuable. Leave off obvious stuff. It's great that you know how to use Windows XP and Microsoft Offce, but those skills are assumed.
• Bullet your accomplishments. For every job/school, list a short summary of your primary duties so that the screener knows what the role was. Then, give a list of bullets that show concrete accomplishments in that role. Things like "reduced cycle time by 15% by restructuring development process" or "wrote credit card transaction module for BuyFast middleware on time with zero errors, as verified by validation team."
• Links. Done online work? Why not include a link? Especially if you're on the UI or creative side, if your resume makes it past the first cut, a look at your work might get you an interview. On that same note, if you do provide a link to your web site, make sure everything is Safe for Work (tm). That picture of you puking off a balcony might be hilarious to you and your friends, but not so much for a potential employer. Same thing for blogs.
• Have a few friends proofread it.
• You've got one chance to make a first impression. Make sure it's a good one. Nothing will get you in the "NO" pile faster than misspellings and grammatical errors. Even one. No matter how much of a perfectionist you are, you will miss your own errors. Have a few people read over your final draft for you. Yes, it's embarrasing-- but less so than moving back in to your parents' basement when you run out of money.
• Consider adding relevant nonwork experience. Don't limit yourself to programming experience. Show an employer that you've got the skills they need to work for them, including teamwork, leadership, creativity, networking, and influence. Don't just throw them on there-- you need to spin how it will help you in your career as a programmer. This one is a little trickier to use (and still follow the other advice above), so use carefully.

I used to be a resume consultant for younger sutudents when I was in grad school and am willing to provide brief help if anyone wants to email me. I've put a decent amount of time into crafting my own resume-- it's online, but I fear the mockery of the Slashdot community. If anyone's interested in an example that follows the notes above, email me and I'll send the link.

Good luck!

short and simple

[pizza_milkshake]

recruiters want a resume they can scan for keywords and they want to know how long you've been using a particular tool/skill. if the position is in a specialized industry then the tool/skill may refer to a specific product or protocol.

imho the best length is 2 full pages, about 100 lines. if your experience of talent can't fill this up, you need to indulge a little. if it's longer, you need to cut out the fluff. they don't want your life story.

keywords are important. if a recruiter is looking for a c++ or java coder then they don't want to spend 2 minutes reading your resume, trying to figure out if you've ever used them before. they want to see those keywords easily in your resume and then if they do, how much experience you have. after the basic quantitative evaluation, they'll like take a look at the major projects you've listed off. the more impressive-sounding the claims, the more likely you'll get a call.

remember that if you're young with no real-world experience, no matter how important you make yourself sound, you will not look better than someone who has 5 years of experience, unless perhaps your reputation precedes you (about %0.0001 of people). no matter how cool your final project was or how much better you were than the rest of your class. you're entry level and when you find a job it will be entry level unless you have a rich family member who owns a business (perhaps 2% of people). for the other 97.9999%, keep blasting out those resumes

as for actually find a job, just keep trying... my girlfriend looked for a job for months before she got lucky and found a place where an ex-colleague was in a position to hire and she got the job. the old "it's not what you know it's who you know" story. try checking with people you or your family or friends know; your highest probability for employment (note: not best jobs) is likely with someone you already know... although i did that twice through friends of my dad and they were both shitty jobs. good luck!

Objective: To Take Up Space on My Resume

[Anonymous Coward]

Oh yeah, and please ditch that "objective: To obtain a position in..." section. God I wish those things would go away on resumes. Everyone of them is the same canned line that does nothing but take up space better devoted to anything.

I hear you, pal. I once had an applicant in my office hand me her resume. Her objective was something along the lines of wanting to apply the knowledge of communications technologies she learned in grad school to real world problems. Sounds great, right? Just a tiny problem: WE DON'T DO ANY COMM WORK! So I asked her if she was aware that we didn't have a Communications division and pointed out her objective. "Oh yeah," she replied. "That's just something I put down. I'm flexible."

So now I'm thinking:

1. Her objective is apparently not a very strong one since she's willing to give it up for a chance to make some scratch. What kind of individual doesn't even believe in their own objective? OR
2. She's lying to me. She really does want to do comm work and she's only interviewing her as a "backup" in case she doesn't get a job at a comms company. OR
3. She's so damn lazy that she couldn't even be bothered to change ONE SENTENCE on her resume to match our company!

Needless to say, we did not offer her a position.

Advice

[Inexile2002]

He used to get around 50-100 resumes a week even when he didn't have a job posting up or any availabilities. Basically, IF he looked at them at all, he wouldn't spend more than 3-5 seconds with any given resume. The layout has to be clean and really easy to follow. There's very little that can be interesting or eye catching about a resume, but that said the good stuff has be OBVIOUS.

Basically though, in this job market, resumes basically resemble spam. Sending companies resumes is not really an effective way to get a job. Start calling people at the company, and don't be afraid to be a little pushy. Don't be afraid of approaching the same company multiple times, especially if you can talk to different people. Network like crazy. Everyone in your life up to and including your aunt's neighbor's mailman should know you're looking for a job and what kind of job you want.

A good resume is really a springboard for the kinds of questions you want them to ask you in the job interview.

As for the basic format considerations, go for information density on a single page. Bold key terms that you want people to notice right away, but embed them in sentences so they're not just looking at lists. I don't like lists of just words, but used to have a section titled "Other Technical Skills" where I put the stuff I wasn't emphasizing.

If you're really convinced that you're doing everything else right and it's the resume that's holding you back, go hire a service. They're cheap and they do decent work. Or do what I did, look at like 20 other people's resumes and steal the format of the best one.

One other thing that a friend did that was a little weird, but worked. She got the name of a manager at a company in her field, called him and sold him the following line. "I understand that you're not hiring right now, but it's a lean market and I want an edge on my competition. Do you have a project that I could be involved with as an intern? I understand that you probably couldn't pay much if you can pay at all, but at least I can start building up experience and if you love me, and trust me, you're going to, you can offer me something when it comes up." It was ballsy but she pulled it off and later parlayed it into a job with one of their competitors.

Maybe it's not for everyone, but the moral of the story is that a one or two page piece of paper is a weak way to job hunt. Start thinking about what else you can do and don't sweat your resume.

His Resume, with critiques.

[cgenman]

Eric Kibbee
716-169 Lees Avenue, Ottawa Ontario, K1S 5M2 Phone: (613) 612-7561 Email: eric@kibbee.ca

PROFESSIONAL PROFILE
A new Software Engineering graduate looking for an introductory software development position. Participated in the co-operative education program, which provided four terms of directly related and progressive experience. A strong team player, as evidenced by excellent grades on the program's major final year team project.

EDUCATION
Bachelor of Applied Science, Software Engineering 1999 - 2004
University Of Ottawa
Participated in co-operative education programme
Graduated Magna Cum Laude

EXPERIENCE
Build Manager
Software Engineering Final Project
January - December 2003
Responsibilties
Final year project that was part of the program that followed all the steps of the software development life cycle
Developed on an on-line document management system
Designated role was Build Manager, but also participated in all aspects of the project
Used ASP and Visual Basic with MS Access as a database
Accomplishments
Completed the project on schedule and met all required performance criteria
Achieved a mark of "A" in the course based on customer satisfaction, documentation of the system and quality assurance presentations

Web Developer
Office of Critical Infrastructure Protection and Emergency Preparedness (OCIPEP)
May - August 2003
Responsibilties
Responsible for the upkeep and development of new features on the department Intranet site
Used Visual Basic .Net and MS SQL Server to develop applications for use by the department employees
Accomplishments
Provided a high level of service and consistent performance of the Intranet
Developed new tools such as an employee directory and an events calendar

Web Developer
Department of Fisheries and Oceans (DFO)
August - December 2002
Responsibilties
Development of a web based financial tracking application
Used ASP with an MS Access database to allow for data entry and retrieval.
A significant portion of the job was to meet with clients and users to obtain new requirements and resolve existing problems
Accomplishments
Project completed on schedule and provided targeted functionality

Web Developer
Environment Canada (EC)
January - April 2002
Responsibilties
Responsible for working on many of EC's Intranet and Extranet web pages
Used JavaScript to create interactive menus for the website
Accomplishments
Completed a major update to the on-line version of the health and safety manual
Developed and implemented a Java based employee training application

Software Developer
Human Resources Development Canada (HRDC)
May - August 2001
Responsibilties
Responsible for reverse engineering an N-tier e-commerce web application
Worked jointly with a second software engineering student on the project
Analyzed the application that used a variety of technologies including ASP, VB, MS IIS, SQL, XML and COM
Accomplishments
The reverse engineering of the application was successfully completed
Developed skills with the above technologies and improved technical writing skills

SKILLS

Web Development - Experienced in web development with HTML, ASP, VB/VB.NET, and PHP
Database Development - Experienced in database development with MS SQL Server, MS Access, and MySQL.

Application Development - Experienced in applications development for both Windows and Linux, in a variety of programming languages including C/C++, Java, Delphi, and Visual Basic
----------------

Whoever reads your resume is going to do so from the perspective of someone who needs X Y and Z, and needs it now. People are looking for a condensed skill section like "PHP, ASP, VB/VB.NET, HTML" (Don't lead with HTML). Your skills section is good, and would be a good leader, though it needs to be less wordy. Give me a list of what you can do. Remember, this list is targeting two peo

What my Dad always told me...

[bergeron76]

GET A JOB!!!

(and minor in Business, not Math!)

I was 15 at the time, but I worked for $60 a week washing dishes. It gave me the confidence and understanding of the business world to be a "go getter".

I did the college thing, and while I did it I was working at tech-related jobs/consulting gigs here and there. Learning how the business world worked (as droll and drab as it may sound), is actually quite valuable. Learn about sales and marketing and it will help you sell your skillset and accomplishments to employers. I've only really had to "seek" work once (maybe twice) in my professional career. Every other time a job/headhunter has either come to me, or a friend of a peer, etc has offered me a job.

It's worth noting that about 70% of all [US] jobs are obtained via personal networking, and references.

Don't be anti-social!

Pretty good way to get results...

[poofmeisterp]

Try submitting your resume to fields other than your target. It seems that people with skills unrelated to IT work seem to get the IT jobs, and the IT-minded people with valuable skills seem to end up working at Burger King. Along those lines, modify your resume to include a bunch of non-IT work and skills.

Also, don't let them know that you're intelligent. If you give them that impression, they will fear that you will realize how messed-up their processes and procedures are and point them out and try to change them. You have to pretend you're completely incompetent and will never have an opinion on anything, but rather just do as you're told.

I speak from personal experience.

Core dump.

[gregh76]

Don't core dump on your resume. A resume is a teaser. Its purpose is to capture interest. Keep it to one page as much as possible. A prospective employer doesn't want to sit there reading your life story when they have a stack of other resumes to go through. Save the details for the interview and, perhaps, a summary of qualifications, which you should have handy when you go to the interview. Targeted resumes are very important. One thing that makes me cringe is seeing people write out these long lists of operating systems, programming langauges, applications, office suites, and the like. Lists like those are meaningless. Instead, under your job experience list, give a short description of what you did and include the relevant OSs/langs/apps/suites. But again, keep it brief and maintain scope. Drop the generic mission statements. A good interviewer will guage how well-rounded you are, so leave those lists off the resume, too. Briefness, specifics, and relevance are what you should concentrate on. Forget the fancy fonts. Keep the layout neat and readable. It's a resume, not a royal proclamation. This has worked very well for me. And remember, be sure you can back up and immediately recollect anything you write on your resume. Think of it this way. Your resume is like the front page of a newspaper, the headlines, the stuff that makes you buy the paper. Interviews and everything else are the rest of the newspaper, the juicy details.

Re:What needs work is the curriculum at your colle

[Quarters]

You can believe what you want, but a Placement Office with a dog-eared 5yr old book on resume writing and a database of potential jobs isn't enough. A resume is a requirement. A good resume is a leg up. An excellent resume and the skills to conduct yourself in an exemplary manner during an interview are necessity for landing a good job.

There's nothing 'vocational' about it. Resume writing and interviewing are skills a person needs to get a job. College is the place where you learn those skills. It makes *sense* to have classes in such things. I went to a Big-10 college and earned a Bachelor of Science. It wasn't a vocational school and the department has an almost 100% placement rate within the first 3 months after graduation....without having to push students through the campus placement office. One of the first things we learned in the class is that resume spamming and using an over-taxed resource like a Placement Office are the absolute *WORST* ways to go about getting an interview.

I had a required class my senior year that covered resume writing (relevent to my major), portfolio layout and creation, and mock interviewing (with representatives from the industry for which I was going to be entering).

I'm in a position in my career now where I look at resumes and portfolios;many from recent college grads wanting to get their foot in the door. It is very easy to see which people have been taught the necessary skills to present themselves effectively. Unfotunately they the minority of the resumes I receive. I can honestly say, though, that the people who can present themselves well have a *huge* competitive advantage over the regular folks who think the Word Resume Wizard and a clumsy cover letter will get you a job.

You can belittle such required college classes all you want. I know, from experience, that the class I took was one of the more important classes I attended.

Humor

[SmallFurryCreature]

Well it worked for me. About 50% of the time I did get an interview. This was during the bubble and after.

I basically don't have an education/diploma and am a late comer to the IT. So a proper CV would be kinda thin.

So I add some stuff that every human resource monkey will tell you is a no-no and hope the CV is read by the tech-head/director/someone with clue/non-tie person instead. Stuff like a Q&A section. Birthday-???? School of life. Diploma not yet. (note that I mean humor, it is not comedy) Most of my jobs HR said no, boss and tech department said YES. I only get in trouble once the tech department is reorganized.

Granted I work as a web-developer wich is perhaps an area in wich a bit of creativity is more appreciated then in other fields. You wouldn't accept a simple CV from a designer would you? Your CV will be read among dozen of others, some more capable some less. What you need to do is grab their attention make them curious. Curious enough to want to find out if your the right person. If they are any good they can train you in skills you don't yet have (language, dev tool, eviroment) but they can't teach you to be creative. Nor can they teach you if they never hire you because your cv looked good but didn't spark an interest.

Also another rule seems to be to not list your negatives. WRONG. Honesty works. Works in two ways. First you don't have to bother remembring your lies. Second you can never be caught out telling the truth.

But the most important is this question. If you got to bend youreselve over backwards in the CV what kinda loops do you have to jump through in the job itself? Make the CV reflect who you are. Then the person they invite will be you. Not some superman you dreamed up and can never be in real life.

Last trick, rate the skills that they absolutly require honestly but at the level they ask. So if they ask PHP excellent and you have it list it as such. But don't brag. Be moderate with the rest. If they are smart they will ask you some questions relating to the skills they want and it is better to have them rate you upwards of what you have put down then have them rate you down. (I find that just listing all your skills is a stupid thing to do, it just doesn't tell them anything HR monkeys love it, tech people know it to be a bragging list, rate the skills as to how well you know them and don't be afraid to rank youreselve a noob)

So basically, be yourselve, show some sense of humor, be modest, don't tell lies and above all, DO NOT FEAR REJECTION. And finally (longer post then I intended) don't blanket bomb. Certain companies will just never hire you. Your personality will just not match what they want. I got long hair and look like something the cat brought in and then brought up. Suit companies don't want me, they do invite me because they like my skills but they want someone in a suit. It is funny to do these interviews because of the reaction on their faces.

Re:Some resume tips

[wackybrit]

You have to be kidding. Even if you have experience with all of those things (and I believe you do), you shouldn't list them all on a résumé! Seeing that list, as an employer, would make me think you're not a specialist.. and sadly generalists don't fare too well in the typical world of recruitment. This is further magnified by your work experience.. publishing, HR, and govt. project management. All good jobs, but there's got to be a better way to present it if you're aiming for a specialized job. I learned this the hard way.

The shortest possible resume:

[Chemisor]

Starving new IT graduate.
Knows how to use computers.
Will work for food.
Have passport, can relocate.

Be brief, be positive, be honest

[wowbagger]

You are fresh out of school - one page.

Hell, I have been an engineer for 17 years, and I would try to keep my resumee down to 3 pages!

First pass, your resumee will get about 10 seconds of review, if that. If I cannot extract the meaningful information in that length of time, bu-bye.

If you are using a head-hunting service, they WILL hammer the shit out of your resumee - it will look like absolute CRAP when they are done with it (scan it, OCR it, condense it, fax it, convert it back to a PDF). True, IF you are sending your resumee directly to the company you need to make sure it is cleanly printed, preferably on a good high bond weight paper. But don't be like Calvin of Calvin and Hobbes - a shiny binder and pretty paper will not disguise the absense of content.

You need to play up whatever experience you have - even if it was just washing dishes or pushing a lawnmower for a parks department (those items are autobiographical). Demonstrating a good work ethic at a crap job is STILL very valuable.

But DON'T exaggerate yourself - you may have taking Signal Processing 101, but you don't know CRAP about signal processing yet (substitute anything from your own education you want). I cannot count the number of times I've interviewed someone who said "C++ experience" on their resumee who could not tell me the difference between IS-A and HAS-A, or even what a class is!

Since you are staring out, you DO need to tell me where in general you want to go - a one or two sentence goals section is helpful. Be real, be specific - "I want to develop Web applications for public use" or "I want to be a technical writer" is good, "I want to excel in creating software" is bad.

Apply for approrpiate jobs. I had a candidate come in the other day - she had been an engineer for some time, but had basically been doing mostly apps level work. She had studied DSP in school, and wanted to get more into that. Unfortunately, she was applying for a senior DSP position. She wasted our time and airfare for the second interview, and that makes us LESS likely to hire her.
I am going to give you the three most important words any technical person can learn, right now. Study them well:

I don't know.

I'd FAR rather deal with somebody who is willing to say they don't know (but are willing to try to find out) than to deal with somebody who is unwilling to EVER admit ignorance. Hell, I am one of the "go-to guys" at work, I *do* know the answers most of the times, but I still often have to say "I don't know, that is not my field of expertise - I can look it up, or you might talk to [person] as they would know more about it"

One last piece of advice: Be trustworthy. Be the sort of person your supervisor can say "This needs to be done. Handle it." and feel that it will be handled. If you have problems, by all means ask for help - but make sure that what has been assigned to you gets done - if not by you then by somebody. One of the best job recommendations I had was from the foreman at the Parks department - while all of the other summer help fuckoffs needed constant supervision to insure they did their jobs and weren't out joyriding or smoking dope, he knew he could just say "The city building needs work today." and I would do it - quickly, properly, and professionally - the Mayor would not be calling about me screwing off.

How CVs get read

[Anonymous Brave Guy]

Remember, you have to write something that can give the reader a grasp of who you are in 10 seconds. Otherwise, the whole thing will end up in the trash basket.

That's very true.

Actually, as I understand it from people who do this for a living, you have around 20 seconds to make a first impression on a very quick scan. That's mostly first-page stuff: does this person have roughly the right mix of skills, and do they have roughly the right level of professional and academic experience?

If you don't get circular-filed at that point, you'll probably get a reasonable, slightly deeper reading: they'll look at the more specific details of past work experience and higher academic qualifications. If you mentioned a web site and your CV is being read by a real person not an HR computer, they might take a look at this stage, too. If they're still reading worthwhile stuff after a couple of minutes, you're probably shortlisted.

CVs might include more (relevant!) detail than that so that they can form the basis for a conversation at interview, but remember that it's a conversation starter. It should provide the interviewer(s) with a neat list of things to start talking about, and you should be able to expand on any of them as they wish when you meet them in person. You don't need to tell your whole life story!