The Resume Black Hole

black hole

Anyone that’s ever applied for a job has experienced the resume black hole. You apply for a job and don’t hear anything back (you might get an automated “thank you”). After a few days you send a follow up message (if you can find an email address) and wait some more. Nothing. No word whatsoever comes back.

It’s demoralizing and frustrating. And it’s insanely common. Too few companies take the time to respond to applicants in any way whatsoever.

The task of sending “thanks but no thanks” emails is time consuming and unpleasant. I always feel like the bad guy doing it, and struggle with what to say. I want to be honest and fair without making people feel shitty.

Some companies get so many resumes (hundreds / application) that it’s almost impossible to respond to all of them. I don’t see that changing in the future (even if it should.) They could setup automated email systems that are triggered as they’re changing applicants’ statuses in their back-end systems, so at least applicants get something relevant, and not totally generic, but most don’t put in the time or effort to do so.

For companies that get fewer applications, you should make the effort to respond to everyone. I tend to write very simple and short emails in these circumstances. Occasionally applicants will reply and disagree with my assessment, sometimes quite nastily. Don’t get into an email flame war with applicants – you can’t really win that battle. Either ignore the email, or reply with another very clear, “thanks, but no thanks” message. Some applicants will reply and genuinely ask for help, curious about what they should do to improve their career opportunities going forward. I have no problem responding to these kinds of emails with suggestions. Just because someone isn’t qualified today, doesn’t mean they won’t be qualified in the future. And it doesn’t mean they’re not qualified for other positions and can’t be successful elsewhere.

I don’t think brands / companies really get hurt by the resume black hole. Too many companies have them; if brands really did get seriously damaged by the resume black hole you’d see the impact. It’s just not there. The resume black hole – unfortunately – is the status quo. If a company goes beyond that in its poor recruitment and hiring practices, it can absolutely have a negative impact on their brand. The flip side is also true — eliminate the resume black hole and you’ll be rewarded for it in the public eye.

Black hole image courtesy of Shutterstock.


How Many Hours Should a Startup Employee Work?

Melted Clock

Every so often I get drawn into the debate about startup employees and how much they should work. Should you hire workaholics? Is it expected that startup employees work 100+ hours per week? Should they be online all the time, constantly available and ready to go?

It depends. And it’s up to you. If you expect employees to work 20 hours / day that’s your choice. If you find people willing to accept those jobs that’s great. I don’t have any issues with that, because when you recruit someone it’s a relationship between two people. If two people mutually agree on something that’s good enough for me. There’s rarely any arm twisting during an employee offer. If they don’t agree, the employee quits or they’re fired. Such is life.

But it got me thinking…

One of the big problems I’m seeing with a startup’s expectations for “hours worked” is that they use it as a metric of employee quality and success. Likely because it’s one of the easiest metrics to track. If someone works 80+ hours in a week they must be kicking ass! Whoever works the most is the best! But clearly that’s not always going to be the case. “Hours worked” is a poor measurement of almost everything, except for “hours worked.” I’m not even sure it’s a great measurement of passion (which is an essential quality you need to look for in startup employees.) It could just be that the guy is slow, so he works more hours.

We need to think about other measurable indicators of an employee’s quality and value. Just like “years of experience” on a resume is a shoddy measure of expertise and quality, the same holds true for “hours worked”.

I’m not arguing against a startup’s need to move insanely fast. Startup jobs aren’t (and never will be) “9 to 5 gigs.” And I agree that oftentimes startups do feel out of control and insane, and that’s part of the appeal. Startups are roller coasters. Don’t think of them any other way. But at the same time if you look at how you evaluate the quality and value of an employee and you’re saying, “Well, he’s not putting in 20 hours per day…”, just stop and ask yourself whether that’s a true measure of value or not.

image courtesy of shutterstock


9 Ways to Successfully Edit Job Postings

Job postings suck. We all know it. It’s been said many, many times. And it doesn’t seem like complaining about it is helping. I’m experimenting on NextMontreal with a job board hack, but I’ve also been thinking about practical advice I can provide on how to improve job postings. Instead of getting people to completely change how they write job postings from scratch, I thought it would be more effective to focus on how people edit them. So after you’ve written a job posting, walk through these steps, and let’s see if it comes out better!

  1. Read out loud what you’ve written. Make note of anywhere that it sounds funny, awkward or sentences run-on forever. Attempt to fix those things.
  2. Count the bullet points. If there are more than 5 in any list, take some out. Force yourself to prioritize. Find a way of replacing bullet points with paragraphs (but don’t go crazy with long paragraphs either!)
  3. Take out anything that’s absurdly obvious. The worst offenders are usually in the “Skills” area. For example: Must be an excellent communicator (both verbal and written.) Duh! Other common offenders: Great attitude, like to work in teams, ability to work in a fast-paced environment, a quick learner, works well without supervision, ability to work in a high-pressure environment, detail oriented, goal oriented, proficient computer skills.
  4. Pretend you’re looking for a job and read it. Does it speak to you at all? Does it interest you? Does it encourage you? Does it answer the questions you might have?
  5. On that note, write down a list of questions you think a potential candidate would have about the job opportunity. Now go back and read the job posting again. Are the answers in there? Do you know what matters to potential candidates?
  6. Count how many times the word “we” is there. Compare that to the word “you”. Hhhm…
  7. The company description should be short. And it should be centered around why someone would want to work there, not around all the awesome awards you’ve won, or how much money the company makes. What matters to job seekers? Focus on those things.
  8. Look at the number of years experience you’ve listed for various skills. Usually these are written as hard and fast rules: “Must have X years experience in Y.” Really? Are you sure? Why? Have you looked at other team members to see what number of years experience they have, and how successful they’ve been? What happens if someone has 4 years experience instead of 5? And does the number of years experience matter as much as the number of projects worked on? Think about ways to gauge experience differently. For example, you could say, “You know the difference between A and B.” A and B could be very specific things that typically would only be understood by a senior person. When someone applies, they should make note of the difference between A and B in their cover letter so they stand out. If they don’t, ask ‘em about it.
  9. Take out your company name and replace it with a competitor’s. Can you tell the difference? Does it matter? If not, imagine how a job seeker feels.

The road to high-quality, meaningful and useful job postings is a long, painful one. Perhaps too painful. But we’ll keep trying anyway…


About Ben Yoskovitz
I recently joined GoInstant as VP Product. GoInstant changes how we use the web, making it shareable like never before.

I'm also a Founding Partner at Year One Labs, an early stage accelerator in Montreal. Previously I founded Standout Jobs (and sold it). I'm a hands-on startup guy, helping companies grow successfully from the idea forward. You can reach me at byosko at gmail dot com.

Follow Ben on TwitterFollow this blog via email
Startup Tools
Find Stuff
Please Check Out:
NextMontreal.com I Spy Montreal
Disclaimer
The opinions and commentary on this site are mine and mine alone. They do not necessarily reflect the opinions or positions of my employer, GoInstant.