Skip to main content

Hiring Courtesy

I really hate when I've reached out to someone and they don't respond. It's even worse if you've made an effort on their behalf--you've invested time and thought and they can't summon the courtesy to simply say no, this isn't going to work. 

And I'm a hypocrite--I do that from time to time: failing to acknowledge someone who has reached out, invested a bit of time, and asked for something. But I'm going to add that to my list of principles I'm committing to as part of the new and evolving daily routine. 

What sparked this post was a comment by Carl on today's post by Fred about the hiring process, along with a friend's story about how his incredibly qualified girlfriend was in the top 3 choices for a rare position at a college in New York, and after the process she still hasn't heard back from them after not simply going through the process, but also being told she's the likely selection (a mistake in any case). 

It's rude, and you should adopt a policy that all interviewees will be given a call or at least sent a letter. If you haven't decided and the process has been delayed for one reason or another, don't leave them hanging. Reset their expectations. 

As I said, I'm a hypocrite--I've been discourteous by allowing interviewees to come through the process without telling them that they didn't get the job. If you were ever one of those people, I apologize. I'll do better in the future. 

Emails hit my inbox that I'll choose not to respond to because it's not immediately urgent or my interest is low, and I don't get back to them. Recently I've been reviewing my inbox to make sure I've responded, but it's almost guaranteed things have slipped through. 

Hiring's not just about you, and it's not just about filling the slot. It's about the people you don't select, but who have made an effort on your behalf (and theirs) to help you come to a decision. They prepare, the interview, and they wait. 

They deserve communication, regardless of the likely outcome. Your interaction with them is a message, and they can and will spread that message. So look at it from a marketing perspective: what kind of company do you want to be? Would you want to go through your own hiring process? How would you want to be treated? 

Have a great hiring process--be systematic, methodical, and courteous. You don't have to be everyone's best friend, but kindness and courtesy are free and well worth it. 

And that's a good reminder for myself. Thanks Carl. 

Comments

Popular posts from this blog

Beta Signup

I've been working for quite a while on a new search concept, though the further in I get, the closer the rest of the world gets to what we're doing. So today I'm inviting you to sign up for the rather modest beta, which will be ready soon if we can nail down a few difficult  details. Jawaya is a way of navigating the web and getting better results. And that's as much as I can say right now, because we're not a funded startup, and things are moving really fast in this space--it's going to be very competitive. I predict there will be about 10 funded startups in the next 6 months doing something similar. One of them will be mine, and we aim to make it the best. We're raising a round of capital to fund the team, and are shooting for early sustainability. This is my fifth company; my fourth in the tech space, and my third software company. I think it will be the biggest and can possibly have a positive impact on the world by reducing the amount of time it takes

Where Innovation Happens

As I get closer to a go/no-go decision on a project, I've been thinking about the difference about my vision for the project and the supportive innovations to enable the core innovations The vision combines (in unequal parts) product, core innovation as I imagine it, the application of that core innovation, design, marketing,  developer ecosystem, and business development. The core innovation enables everything else, but it's the application of the innovation that makes it meaningful, useful, and in this case, fun. This week we're testing initial approaches to the implementation for our specific application, and that's where we'll develop the enabling innovations, which is basically where the rubber meets the road. The difference is that the enabling innovation happens at the source of real problems only encountered in the making of something, and in a project like this just getting the essence of it right isn't enough; it also has to be safe, the compone

The Real Jobs Problem

It's the economy, stupid.  Well, yes, it always has been, if you're in the distortion field of politics.  But whose economy? The pundits, the White House, the Republican candidates all miss the mark. They keep talking about debt, taxes, and monetary policy. None of those things tell the real story behind today's economy.  The Old Economy Keynes was right--in the old economy. Economy gets weak, pump some money into the economy through public works projects, which  1) puts people to work, which  2) boosts the economy and  3) generates new tax revenue, while  4) leaving us with another generation of reliable infrastructure to support  5) more growth (for growth's sake, which is another post).  The Beach Ball Imagine a beach ball, partially deflated to represent a recession. Got it? Now imagine the govt pumping that beach ball back up through sensible public investment (which we haven't seen for decades). The New Economy Same beach ball, same pum