Does your résumé have to fit on a single page? Roger Ebert has the answer.

November 1, 2010 Job hunting 3 comments , ,

Every time I speak to a group of people, and people talk to me afterwards, the topic of résumés always comes up. And every time people ask about résumés, someone always asks “Does my résumé have to only be one page?”

Your résumé does not have to be limited to only one page. It just needs to have nothing irrelevant and uninteresting in it.

I refer to film critic Roger Ebert‘s rule about how long a movie should be:

“No good movie is too long and no bad movie is short enough.”

You should apply the same rule to your résumé.

As long as what’s in your résumé is relevant to the reader, and the reader finds it interesting and it helps show how you’ll be a valuable addition to the hiring manager’s team, you can put in whatever you want, and your resume can be as long as you need it to be.

This means that when you apply for a job as a network engineer, you don’t bother mentioning your job at a pet store back in college, unless it somehow relates to the job for which you’re applying. If the job for which you’re applying is at PetSmart corporate headquarters, then by all means, include it.

Is anyone reading your résumé going to care about your “hobbies and interests”? Probably not. I guarantee they won’t if your hobbies and interests are “music and reading.” On the other hand, if you’re looking to do web development for Guitar Center and you play an instrument, then definitely put that in your résumé, perhaps even in your professional summary.

This also means that you have to tailor every résumé you send out. You have to go through every line and think “Will someone reading this résumé care about this?” You have to figure out if some bullets in your work experience should be expanded.

From today forward, don’t ask “Is my résumé too long”. Instead, inspect every word to see if it is of interest to the reader.

The worst way to start a résumé

October 26, 2010 Job hunting 5 comments , ,

As I go through dozens of resumes, I’m amazed by how many people still waste the crucial top two inches of their resumes with drivel like this:

Objective: A fast-paced, challenging programming position or other technical position that will utilize and expand my technical skills and business experience in order to positively contribute to an organization.

You and everybody else, buddy. Why should I give it to you?

That top of the resume is prime visual real estate. It’s the first thing I see when I open your email or Word document. I want to see a summary of who you are, and how you can help me by joining my organization.

Here’s an imaginary summary from a programmer applying for a Linux-based web development position:

7 years professional software development, most recently specializing in Perl and PHP, including

  • Developing object-oriented Perl and PHP, including interfacing with Oracle and MySQL on Linux (3 years)
  • Creating intranet database applications with ColdFusion and Access (2 years)
  • Creating shareware audio analysis programs for Windows in C/C++ (5 years)

In just a few lines, she’s summarized the real meat of who she is and what she’s going to bring to the position. The key words for the job to hit are bolded, to make them easier to find for the reader. Note that in this case, she has not bolded “Windows”, “Access” and “ColdFusion” because that’s not something she chooses to pursue further. It’s part of her background, but not worth emphasizing.

The skeptical reader may ask “But what if she’s applying for something that’s not a Linux web position?” Then she’ll modify her resume for that job when she applies for it. Takes only a few minutes, but it’s more likely to draw the interest of the reader. You’ve got a computer, you’re flexible! Tailor the resume to the position.

The still-skeptical reader may say “But what if I’m applying for 100 different jobs?” Don’t apply for 100 jobs. There aren’t 100 jobs out there that match you and your skills. Why waste your time? Spend the time working on the ones’ that match.

Bonus mini-rant: “References available upon request” is also fluff. Nobody has ever said “Hmm, this guy LOOKS qualified, but doesn’t have references available. I better not bother with an interview.” Kill it.

(Originally posted at

Don’t send two résumés

October 12, 2010 Job hunting No comments ,

I’ve never received two differing resumes in response to a job ad, but Allison Green has seen a growing trend. Don’t do it. Create one resume that puts you in the best light, and include a cover letter that addresses the needs of the employer and shows that you’re interested in that specific job.

The job interview is not about collecting factual information.

October 10, 2010 Interviews, Job hunting 2 comments

There’s a common misconception in the techie community that you should make sure you don’t fall prey to. Here’s what it sounds like.

So I went on the interview, and the interviewer was totally unprepared. First thing he asks me, he says “So, Dave, tell me about yourself.” He’s got my resume right there on the desk in front of him. It’s like he didn’t even read it! What could I say? I said “Well, what do you want to know?”

Poor Dave is laboring under the impression that his interviewer was trying to find out facts about him. Dave’s attitude is basically “RTFM, dude.” Dave’s written down everything on the resume, so why should he have to bother explaining it to the hiring manager?

For the sake of his job search, Dave would do well to learn that Job interviews are not about obtaining factual information about you. They are about assessing the candidate as a person, as potential team member.

If the hiring process was as simple as gathering printed requirements from resumes, there would be no need for interviews. Hiring managers could sit back and shuffle through stacks of paper until the right combination of skills showed up. It’s not that simple. When the hiring manager hires someone, he’s hiring a human being, not a bunch of programming languages and network skill sets off a checklist. Hiring is fundamentally a human process, no matter how computer-oriented we may be.

The question “Tell me about yourself” serves at least three purposes.

  • It gives the candidate a chance to give her elevator speech, to tell about herself and what value she’ll bring to the organization, and set the interview off in a given direction.
  • It lets the manager see how well prepared the candidate is for the interview.
  • It lets the candidate show how well-spoken she is.
  • It lets the manager get an idea of the candidate’s attitude and personality. In Dave’s case, his attitude is terrible and that will come out. Dave won’t get the job.
  • It lets the manager compare what you tell him with what’s on the resume, to see if there are any discrepancies.

The worst response to “Tell me about yourself” is to ask “Well, what do you want to know?” What the hiring manager wants to know is what you’ll do to help him make money for the company, or do things faster, because business speaks in terms of money and time. To be able to answer that, you’ll have to be prepared, and probably do some research about the company and the position itself. It should not be a canned answer you use at every company.

None of this is to say that there aren’t incompetent, unprepared interviewers who fall back on “Tell me about yourself”. Chances are, however, that when you’re asked this in an interview, you’re being given a chance to make a good impression and to start the interview right. Don’t blow it by misunderstanding its purpose.

How to explain past problems in a job interview

October 5, 2010 Interviews, Job hunting 1 comment ,

In her recent US News article, the always spot-on Allison Green of Ask A Manager answers the question “How do I explain in an interview that I was fired?” An example from the article is:

“Actually, I was let go. The workload was very high, and I didn’t speak up about that soon enough. I just tried to keep my head down and get it all done. This wasn’t a realistic strategy, and I ended up making some mistakes because of the volume. It taught me a really valuable lesson about the need to communicate better when the workload is a problem and to figure out ways to make sure we’re on the same page about priorities if we’re in a triage mode. Since then, I’ve put a real premium on keeping lines of communication open so that that never happens again.”

Note how this example is much like answering the classic interview question “Tell me about a project that didn’t go so well, and what you learned from it.” You describe a problem clearly, without rancor, and how you dealt with it. After that, you describe what you’ve learned to improve things going forward.

Another key point that she brings up is that you must not be angry about having been fired. In the article, Allison says:

Practice your answer over and over out loud until you can say it calmly. What the interviewer is going to be paying a lot of attention to–almost more than the substance of your answer–is how you talk about it: Do you seem bitter and angry about it? Have you learned from the experience? How has it changed the way you conduct business? You want to really pay attention to how you deliver it.

This is fantastic advice for your entire interview, too. Are you one of those people who is easily angered? Do you find yourself irritated when talking about people you work with that you may not pull their weight, or perform as well as you? If so, chances are that irritation is coming out when you interview as well, and it doesn’t help you at all.

Every interview you go on is going to have at least one form of the “tell me about a problem from the past, how you dealt with it, and what you learned” question. Come up with an answer for it beforehand, and know what you’re going to say. Practice it. Make sure you are entirely without rancor or fingerpointing in your delivery. Role-play with a friend and see what they say. You might think you’re sounding calm, but a fresh set of ears may tell you otherwise.

Check out Allison’s article, and visit her main blog Ask a Manager. Allison is a must-add for your feed reader.

Milwaukee JobCamp, a free all-day job hunting event, is this Thursday

October 5, 2010 Job hunting 2 comments

Thursday, October 7th, 2010 is the fourth Milwaukee JobCamp. This free day-long event takes over a huge amount of space at the Potawotami Casino conference. There will be sessions on a huge variety of topics related to the job hunt, as well as a resume help desk room and, of course, lots and lots of networking with others.

I hope to see you there. I’ll be talking about how the hiring manager sees the hiring process, and how to use that to your advantage in the interview.

Fifteen ways to kill your job interview

August 15, 2010 Job hunting No comments

There are hundreds of ways to ruin an interview, but here are 15 that are dear to me, or that candidates have pulled on me in the past.

  • Show up late
    • It’s inexcusable. Drive there the day before to make sure you know you can get there in time.
  • Be unprepared
    • Your first assignment at this company is to show up prepared. Don’t fail it.
  • Smoke, or smell like smoke

  • Have bad breath or body odor

    • Nobody wants to smell your smells. Eradicate them.
  • Shake hands like a fish
    • Don’t shake hands with a death grip, but don’t wuss out, either.
  • Come underdressed
    • If you find yourself asking “Do I have to do X?” for the interview, play it safe and do it. That means wear a suit.
  • Speak ill of anyone, especially past employers
    • If you complain at the interview, you’ll complain all day at work, too. No boss wants to deal with that.
  • Complain; discuss your problems
    • Your boss has his own job-related problems to deal with. He doesn’t want to hear about yours.
  • Bring up your needs, such as money or benefits
    • Your interview is all about what you can do for the company, not what they can do for you.
  • Lie
    • You’ll be found out, and you’ll be worried about it until you are.
  • Appear uninterested
    • No boss wants to hire someone who doesn’t care about the job she’s going to be doing.
  • Fail to ask your own questions
    • The best way to show that you care, and that you have a mind for business, is to ask your own questions about what you’ve discussed during the interview.
  • Appear desparate
    • Enthusiasm is one thing. Desperation is another.
  • Leave your phone on
    • There’s no way you could be expecting a call that’s more important than this interview.
  • Cut the interview short
    • Allocate adequate time for an interview. A longer interview is always better, so plan for the good. Don’t try to squeeze in an interview on a long lunch hour. Make sure your kids are adequately covered and you don’t have to say “Sorry, I have to leave, my sitter can only keep my kids ’til 4:00.”

“I just slammed out 300 resume applications for which I am more than qualified for this week, I doubt I will hear from even one”

June 27, 2010 Job hunting No comments

A recent poster to reddit asked I just slammed out 300 resume applications for which I am more than qualified for this week, I doubt I will hear from even one…..any advice for [engineering] job hunting?

If I’m hiring people, the slammed out resumes mean nothing to me. You want to know the number one way to attract my attention? Write a cover letter that says that you’ve actually done some research into the job for which you’re applying.

It’s a buyer’s market out there. You’re putting your resume out there with, say, 500 other applicants. Wading through that much shotgunned resume crap is daunting at best. Give me something to grab hold of. Give me a reason to say “Hey, this looks interesting.”

Don’t waste your time applying for 300 positions. There are not 300 positions out there for which you are qualified, and that you would be happy doing. Instead of shotgunning them, work on two or three or five and really get into understanding the job. Research the company. Research what they need. Find out everything about the company that you can, and spend the time figuring out what you bring to the table that will help the company the most.

Finally, those 300 applications came from where, Monster or some job site? Less then 10% of jobs get filled through job boards. Personal networking accounts for about two thirds of job placement. Instead of wasting time with shotgunning resumes that are obviously shotgunned, work to talk to everyone you can and find pointers to other people who can help you find a job. The jobs are out there, but you have to know where they are.

How to do a web resume right

June 13, 2010 Job hunting No comments ,

I’m humbled checking out the web resume for my friend Julian Cash. It hits all the right buttons.

  • Catchy domain name,
  • Strong bulleted overview of his skills on the front page.
  • Links to key points in the margin on the right, and at the bottom of each page
  • Subpages about important areas of interest (project management, programming, etc)
  • Contact information at the bottom of every page
  • Testimonials page, although I’d put some information about each person to give weight to their words.

If you can get your web resume to be even one tenth as interesting as Julian’s, you’re way ahead of your competition.

When was the last time you were thanked?

May 30, 2010 Career, People No comments

Seth Godin’s blog entry today sums up so much of my frustration with much of what I see on the Net:

Yes, I know you’re a master of the web, that you’ve visited every website written in English, that you’ve been going to SXSW for ten years, that you were one of the first bloggers, you used Foursquare before it was cool and you can code in HTML in your sleep. Yes, I know that you sit in the back of the room tweeting clever ripostes when speakers are up front failing on a panel and that you had a LOLcat published before they stopped being funny.

But what have you shipped?

What have you done with your connection skills that has been worthy of criticism, that moved the dial and that changed the world?

Go, do that.

Right on, Seth. To that list of “so you can…” I’d add

  • You’re a master debater on Slashdot and Reddit
  • You’re quick with a link to
  • You correct people in the ways in which they ask questions in IRC

The tough part is that most of the things that you do “with your connection skills that has been worthy of criticism, that moved the dial and that changed the world” require you to get off your ass and get out from behind a keyboard.

Ever given a talk at a user group meeting? Ever organized a conference? Or lined up a speaker for a user group meeting? Written an article or blog post where people say “That’s changed the way I look at things?” Or created software where people say “I don’t know how I lived without this?”

When Seth talks about “moved the dial and changed the world,” I’ll even set the bar a bit lower. When was the last time someone thanked you for downvoting someone on reddit, or being an oh-so-clever snark poster on Slashdot? Ever received appreciations for pointing out what you perceived as someone’s shortcomings in a flame war?

Which is more likely?

  • “Thanks for telling that guy your negative opinion of him.”
  • “Thanks for that presentation on Ruby modules.”
  • “Thanks for reaching level 75 on Farmville.”
  • “Thanks for putting together this group. I learned a lot.”

Get out there from behind your keyboard and do something that builds rather than tears down.