Ramsomware gets even more nasty
The Trouble with Hiring that 1st IT Employee – Part Two
Show all

The Trouble with Hiring that 1st IT Employee – Part One

You’re business is thriving, you’re hiring, now you’ve realized you have a lot of technology around the office and you should probably start getting a grip on it.  The thought of hiring an IT person pops into your head.  What’s to lose?  You’ll have someone with expertise, knows what they’re doing, handle all your IT and everyone will be happy right?  Not quite.

Hiring that 1st IT

When a company is hiring it’s first, or even replacing it’s only IT person, there’s a few problems that usually pop up.  Let’s get honest about hiring for IT (and many other positions!)

  • You want to pay X amount.  The first time out of the gate, that usually winds up between $35k-60k per year.  That’s just salary of course. At the low end of that, you’re going to get someone who’s entry level, and not much experience passed fixing desktop issues.  That leaves network, backups, database, applications, security in the learning area.
  • They’ll learn all your systems.  Great!  For them that is.  They’ll now leave to get higher pay.  Loyalty runs thin nowadays.
  • Most awesome IT professionals aren’t really looking for a job.  They have that great job.  So you’ll have to settle.
  • No sweat!  I’ll hire someone who needs a job.  If you mean desperate, they’ll leave as soon as they’re not desperate.

Interviewing for IT and Technical Positions

So enough with the basic decision of wanting to hire internally.  On to the fun stuff.  Resumes and Interviewing.  The main problems here are going to be how much you understand what you need from this IT person, what they understand, are they actually qualified, and the most important one, can you tell?

  • Resumes!  You search for or get a bunch of resumes using some of those keywords.  You do a little research and these are the qualifications you think you need.  All techies love those on resumes.  MCSE, MCSA, CCNA, and on and on.
  • Interviewing!  You weed it down and start interviewing.   What questions are you asking that lets you know these applicants actually know what they’re saying?
  • Recruiter?  Or you went the other route and hired a recruiter. The right recruiter can work out, but fact is, most recruiters are not technical in nature.  There’s no way for an applicant to prove their knowledge here.

There are many correct ways to go about hiring and interviewing for IT.  Our main point here is, it’s difficult.  Hiring and interviewing ANYONE, can be difficult.  Hiring and interviewing for IT is just that much more complicated, especially if they’re going to be your one and only IT employee.

We’ve broken down a few of the initial issues of hiring an IT employee in-house.  Next we’ll look why you shouldn’t hire that employee just yet.

UPDATE:  Check out Part II Here:  The Trouble with Hiring that 1st IT Employee: Part II