4 ms·
Everyone pay attention, this seems to be one of those lessons everyone learns the hard way. I'd made a similar mistakes with my first hire. Basically I hired t
by coenhyde 15y ago
Everyone pay attention, this seems to be one of those lessons everyone learns the hard way.
I'd made a similar mistakes with my first hire. Basically I hired the first guy who said he was awesome at php. Great I said. Do this, this and this. You can do some work from home, set your own hours at the office etc. He stopped coming into the office to work from home instead. I was so over capacity that i didn't check on his work for about 2 months (fool is me). When I finally did I discovered a horrible horrible mess. The app was completely useless and the 'awesome php dude' was completely incompetent. Lessons learned:
1. Do your own investigation into a potential hire to see if they are actually capable.
2. Watch new hires carefully
3. It costs more to fix hiring mistakes than to prevent them from happening.
Actually my second hire was pretty shit too. This time I made sure the dude was technically competent but he didn't fit the company culture I wanted. I don't like egos or office politics.
After those few bad mistakes my subsequent hires were great.
- sunsu 15y agoI'll second the "watch new hires carefully". You can save yourself a lot of problems if you just keep an eye on your new people for the first month. Obviously you don't need to be overbearing, but at the end of that first month you should do a detailed work evaluation (code review if a programmer). If the employee shows signs of producing crap in their first month, get rid of her/him then. Do not wait unless there is a really, really good reason to.
- mattdeboard 15y agoYep, I have been very surprised in recent weeks at how bold people will be in their lies about their professional capabilities and/or history.
- SanjayUttam 15y agoI'd also add: Never assume an individual is competent based on their title and/or the company they work for.