IT Employment

Lessons in leadership: 30 concrete hiring ideas you can apply straight away

Ilya Bogorad offers 30 concrete tips that will bring your hiring practices up-to-date with hiring in a knowledge economy. Apply these ideas to find and recruit the best possible people for your team.

Despite many organizations' claims of their people being their greatest asset and despite the ubiquitous references to the "battle for talent" heard in executive suites, a typical Human Resources department remains a largely transactional entity, conspicuously absent from the top-level strategic decision making.

It's a great pity, because it is the people within a company who make it either prosper or languish. Yet people management skills in organizations are akin to raising children, investments, and driving: most think that they know how to do it best, but the results are often underwhelming. This is one area where your HR department could start making a difference right away, by coaching and mentoring hiring managers at all levels. But even this simple tactical suggestion may be too tall an order.

A couple of weeks ago, I wrote an article on building a winning team and promised to follow up with a bunch of practical hiring ideas. Well, here they are -- arguably each deserving its own article. This is not a nebulous discussion on how things should be but, rather, a set of concrete actionable items that my clients have found most valuable.

Marketing

  1. The strongest position to find and hire the best people comes not from your pounding the proverbial pavement looking for the right people but from your organization being perceived as "the place to be."
  2. A strong brand is as important for hiring as it is for sales. People line up for jobs at Google and Microsoft, but why would anybody want to work for your company? If you are a senior leader, make this side of the overall brand development your priority.
  3. If you lead a division, department or any other entity, no matter how small, develop your group's own brand within your organization. You will know that you've succeeded when people start asking whether you are hiring and you hear rumblings from less capable managers about your "stealing the best people."
  4. To make brand development most efficient, enable your staff to be ambassadors of your group's brand. Let them tell others why it's cool to work for you.
  5. How to market your group's brand: showcase; communicate outward; make sure you are a permanent feature of the corporate newsletter; do cool things and tell people about them; establish close relationships with as many decision makers as possible; hold open-doors sessions; run seminars on your specialty; etc. The investment of time in this area will pay off.
  6. Looking for and finding

  7. There are organizations and events in every city and online where the people you want to have on your team tend to congregate. Network, learn, connect. Ask for recommendations. Showcase your brand. I am amazed how many managers don't know what's going on and what's hot in their profession, industry, or locale. Get out there.
  8. Don't be afraid to offer a job to someone with an ostensibly high profile. I find that rejection is often automatically assumed ("Why would she be interested?"), but you don't know until you ask. After all, what is the worst thing that can happen?
  9. Avoid recruitment agencies. With rare exceptions of boutique and executive operations, screening of candidates' resumes is typically done by low-level, poorly compensated staff with little or no knowledge of technologies, vague understanding of business concepts, and certainly no awareness of your priorities. Why would you trust these people to find out who is fit to work for you?
  10. Likewise, do not allow your HR department do any prescreening.
  11. If you must use an agency (mandated, in a mass hiring mode for entry level positions, etc.), establish a relationship with the account manager and ensure that they understand your needs and priorities exactly.
  12. If your organization has a co-op program, make sure your department is a part of it. If not, start your own. Establish a relationship with the head of the recruitment office at a university or college, speak to graduates (part of promoting your brand), and get the best summer students. Then, hire the stars (otherwise, what's the point of going through all this trouble?).
  13. Don't confuse (yet this is far too common) short-term staff augmentation with long term building of a winning team. When I need my trees pruned, I simply hire someone who is good at it. If I wanted to hire a permanent gardener, my criteria would not be limited to technical skills (I told you in the previous article what I look for).
  14. Hire for the goals of tomorrow, not the ones of today.
  15. Advertising (you won't need it when you have a strong brand)

  16. Write the position advertisement yourself or delegate it to one of your people. If you need to get a nod from HR before it goes out, by all means get it, but don't trust them with writing.
  17. Think about your requirements carefully. Why are you looking to hire a person? What is important and what is not? Then, write it down, getting to the point quickly.
  18. Include a one-paragraph introduction on the hiring organization, no more.
  19. Skip the HR talk ("mental effort required," etc.) and don't bother listing requirements that no one in their right mind would admit not conforming to (excellent customer service skills, courteous, excellent team player, superb problem solving skills, etc.)
  20. For IT positions, only list required technologies that matter. I was helping a client to stop losing great prospects to the competition when I came across requirements of "proficiency with MS Word" for a VP position and "experience with TCP/IP" for a QA Analyst. The first one is laughable, and I have no idea what they meant by the second.
  21. Do not use internal job descriptions when advertising a position. They often disclose too much information that your competition really shouldn't have access to.
  22. Avoid internal acronyms. A client once complained to me that they hadn't been able to fill a senior IT developer position due to lack of interest. Upon examining the online advertisement, I found it to be for an "XCCX Developer," XCCX being an acronym for one of their business application complexes. Removing the scary acronym from the heading led to a flood of good applications.
  23. Selecting

  24. Here is how much trust I put in IT resumes: next to none. It's a good conversation starter at best.
  25. Experience is overrated. Guy Kawasaki was selling jewelry before he was hired by Apple. Carl-Henric Svanberg, the CEO of Ericsson (telecom), is going to BP (oil and gas) in a couple of months as a Chairman. Yet many hiring managers stubbornly look for some arbitrary number of years in the industry, with a particular technology, in a particular environment. There are many reasons why this is a poor, damaging practice, but I'll give you just one. A talented, motivated and hard working person can learn more in a year than his average colleague in three years. Why wouldn't you want the first candidate? If you demand three years of experience, he won't make it to your short list. See, if you are asking for this, you are looking to hire conformity, not talent.
  26. Diplomas and certifications are overrated. Outside of regulated professions, such as engineers, nurses, or doctors, we pay too much attention to formal education and certifications than is deserved. Knowledge can be acquired through other means and we all know of the famous dropouts who don't feel constrained to add CHIRP or CHOP or CHUM to their name.
  27. To expand on the previous point - look for the skills that you need, not the package they usually ship in. A head of customer service of a well known organization once told me that it was hard for him to recruit English majors given his budget. When I asked why on earth he needed English majors, he answered that he needed people who could reply to complaints in writing. My suggesting that he simply needed people who could write reasonably well was an epiphany. The problem was quickly resolved because this is one skill that is easy to test for.
  28. Tests, by the way, are perfectly appropriate for many positions, such as developers. A common issue with tests is that they are often misguided. Using developers as an example, poor tests include testing for knowledge of syntax or offer a candidate a convoluted problem which one of the resident staff resolved a day before after many months of trying. This is a waste of time. You want to see the understanding of the realm, the thinking process, the intelligence. Mini cases usually work well.
  29. Avoid irrelevant metrics. The size of a project budget is a poor proxy for project complexity and is no indication of the project manager's abilities. If someone managed a department of a hundred employees, it does not mean that she wouldn't be able to manage a group of three hundred, nor does it mean that she was good at it. Years of experience in this or that is one of the poorest metrics of all, as I already pointed out.
  30. Hire people with diverse skills and experiences. It provides for a capable, innovative team which draws on the complimentary strengths of its members. A group of people who do, think, and look like you is not what you should strive for.
  31. Offer

  32. No matter how tempting or how much you are pressured into it, never ever offer employment conditions that are not equitable. Not only is it because the immediate savings can be very quickly undone by a sudden departure of a key employee for greener pastures, it is also unethical.
  33. As in any negotiation, understanding the candidate's priorities will help you structure the offer to the satisfaction of the both sides.
  34. Establish remuneration based on value of one's work, not on seniority, age, gender, or hours spent in the office. We have been living and working in a knowledge economy for the past thirty years, a notion that hiring practices in many organizations haven't yet caught up to.

About

Ilya Bogorad is the Principal of Bizvortex Consulting Group Inc, a management consulting company located in Toronto, Canada. Ilya specializes in building better IT organizations.

9 comments
Mike Knapp
Mike Knapp

Great article - here are a few things to add. Marketing 31. Define (and develop) your department's culture. Consider things like the energy of the group, work style, innovation level, style of management. Understand where you want the culture to be. Knowing / marketing the culture will let applicants better understand if they'll fit. Looking and Finding 32. Hire people who will help move your team's culture to where you want it to be. Selecting 33. Consider hire for base required skills and aptitude instead of the person with the most knowledge. Often growing and developing the greater skill set you need yields better long-term results. This ties in to #22. 34. Hire for team fit. Attitude is key. It's important that the person fits with your team (and where you want it to go). We spend countless hours in the office - knowing your team gels and likes each other will make a much better team. 35. Listen to your instincts. They're usually right. 36. Adding to 25: Use tests appropriately. Testing for data that someone can pull from a Google search or text book is useless - because most people would just pull it from a search in the real world. Test using scenarios that show the person's common sense and understanding of broader concepts. http://www.tech-services.ca/blog/?p=79

JasonKB
JasonKB

All great points, unfortunately IT can't build an organization's brand on its own. You might be running a great IT shop but if the rest of the organization is perceived poorly you may have a hard time attracting good talent. Can't agree too strongly with point 9. I'd rather read through 200 resumes than have them screened for me and miss a gem of a candidate.

Tony Hopkinson
Tony Hopkinson

Even the experience which some might consider strange seeing as mine is counted in decades. I'm not holding my breath for a lot of this to happen, but hope does spring eternal.

cbader
cbader

I hope a lot of hiring managers read this article. Im tired of seeing ads that require a candidate to have 10 years experience, with an MBA, know Win98 and NT up through Server 2008 and Vista, Exchange 5.5-2007, and the job ends up being for a helpdesk position.

Snowflash
Snowflash

Great Lessons learned! I have been a manager off and on for 30 years, now I am a project leader, as well as a DBA student. I wish I had this advice 30 years ago, but at least I can now pass these lessons on to my future business students. Thank you, PAul

jeff.hayden
jeff.hayden

while I was encouraged that our management team does many of these already, there were still a few good take-aways from this article...thanks.

Kam Guerra
Kam Guerra

Remove staffing firms and HR from the hiring process.

Kam Guerra
Kam Guerra

Everyone wants the credit (and usually the $30K bonus) that goes along with hiring certain skillsets. The person that's in-the-know writes the job description and hands it off to HR. HR butchers it and everyone from the HR manager to the HR flunkee that posts it to Monster, CareerBuilder, whatever ... adds 1 year to the experience needed. This is why you have advertisements requesting people with 10 years SQL Server 2008 experience, or 20 years Java experience, or looking for junior engineers with 10 years experience with whatever. They do the same thing with salary too. Everyone adds a $$$$ to the salary hoping to attract someone. I do feel sorry for people interviewing for positions only to find out most pay half of what the advertised salary is only to be told it was a typo just to cover HR's a$$.

MPITIL
MPITIL

This article points out something I just did today. When asked if an interviewee was ITIL certified, I said no - and got dissaproving looks. However, I explained that this person explained the concepts of ITIL in the interview. We'll be making an offer asap!