People who either have degrees in IT or have experience working for companies. I'm not super comfortable with this running your own business on the side thing. At the same time, it is an entry level job doing some pretty basic stuff.... but I also don't want to be stuck with someone who is clueless either that HR won't let us fire, and it just kind of seems to me that if you've just been doing IT work on your own and never had any professional experience, you really can't be all that knowledgeable. The exception being if he had an IT related degree.
So, anyway, should we give this guy a shot? Anyone else have any experience with hiring someone with this guys background? Did it turn out good or bad? Would you hold out for someone who has an IT degree or professional corporate experience? I'm going to let HR know what I think Monday. Obviously, I am going to make my own decision on this, but I'd like to see if anyone has any similar experience with someone like this.
For $10 an hour? Seriously? He could make more money at McDonalds in all honesty. When I worked at Staples back in college (10 years ago now?), our "lead tech" was making $13 an hour. The fact that he has has A+, Network+, Security+ and MCDST/MCP/MTA certifications is pretty impressive; I've been in IT for 10 years, have zero certifications, and haven't even finished community college yet - I'm on year 15 of my 2-year degree (no joke) :awe:
I mean, without overtime, he's only going to be making about $20k a year (
before taxes). I don't know how competitive jobs are in your area, but that's like poverty line just about anywhere. So from that perspective, how much do you really want for the money? On the flip side, he's showing an interest in the job by doing an interview, and also has the certifications, so it sounds like a pretty good bet if he seems like he would fit in.
The biggest issue I've seen is getting DIY'ers to fit into corporate culture. I made that transition myself...I fixed up people's computers in college as a side job & eventually got into it professionally. I was all about build-your-own servers, Linux, and all that stuff. Working 70 hours a week and having to worry about little things like "uptime" made me change my tune pretty quickly. The biggest thing is having written procedures of "this is how we do things", everything from how you interface with the users to how you handle disaster recovery
My in-house corporate IT procedure book is a zillion pages long & has taken like five years to flesh out, but 95% of the stuff I do is now procedural, so I can be more efficient & not have to sit there & figure things out every time or forget the details of doing X or Y setup. So if you guys don't have official policy for him to follow, now would be a good time to start writing that stuff out. That's probably the biggest foreseeable issue that I can see.
If you don't let him have hands-on stuff to the really important stuff (i.e. full network domain admin rights & whatnot), then you'll stand less of a chance of having to explain to your CEO & CFO why the new hire with no college degree screwed something up big-time. Embarrassment is a very real part of the corporate experience because it can lead to you getting fired because you made a bad hiring decision, so I understand where you're coming from. That's a little bit of the reason why I haven't hired an assistant for myself yet...so many ways for them to screw things up & for it to come back to haunt me.
But he sounds like a pretty safe bet, as long as you think he's trainable (and not super dug into his own approach theories), and if you have some kind of clear in-house methodologies for him to follow so he's not constantly getting berated for doing things wrong that aren't clearly expressed anywhere for him to follow.