You Won’t Believe How Much Money We Wasted On Bad Hires In 2013
hub.uberflip.com
hub.uberflip.com
Also, Warning signs- Randy mentions "9-5" and "as they say goodbye at what you may not deem not a legitimate end of the day."
I don't think I would want to work for Randy- Maybe this is just my impression and not the case here, but if you think being a startup is an excuse for regularly expecting employees to work more than 8 working hours a day then you are deluded, taking advantage of your employees and hurting them. I would not let my employees work more than 50 hrs/week even if they begged.
Side thought: Everyone in the valley mentions 9-5 as "standard working hours", but a standard work day is 8 hours. So assuming a 1 hr lunch that is 7-4/8-5/9-6... Where I grew up in the upper midwest, there everyone used the term 8-5...
Also, he never really says what was wrong with these employees. Vague doubts about "fit"? "Get under your skin"? "Don't mesh"? All sounds like a discrimination or wrongful-termination suit waiting to happen. Anybody who is in any way dealing with HR should know that firing someone requires extensive documentation of actual wrongdoing, not just this weak "feels wrong" crap. I'd be very surprised if that's less the case in Canada than in the US.
This author really needs to worry less about cover letters, and more about why his company is having these cultural-fit problems. Maybe putting "Like to work late?" and "Test your ping pong and foosball skills" on the Careers page doesn't attract the right kind of employees. I'd love to hear what some of those ex-employees found once they got there, especially regarding the little Pocket Napoleon of a COO.
Not likely on the coasts... at least not that many at one time.
>Vague doubts about "fit"? "Get under your skin"? "Don't mesh"?
Agreed, culture is important, but an absolute fit isn't essential either. For fscks sake, sometimes a good workplace cultural value is tolerance for your co-workers idiosyncrasies.
sometimes a good workplace cultural value is
tolerance for your co-workers idiosyncrasies
Very true. At the same time, having a boss with these types of idiosyncrasies is like seeing an exit sign.Instead look for people who like to tinker and fix and build things. People whose personal lives are stable and sane.
Like you said. Its basically a guy who sacrifices his whole life to make you rich and expects to get nothing in return.
75 * 6 devs = 450 dev-days, or 1.23 dev-years. 70K/1.23 = 56.9K. According to Google, that's $51K USD per year.
Yeah, I can't imagine why rockstars aren't beating a path to his door.
In the US? Maybe to help avoid frivolous lawsuits, but barring having signed a contract stating otherwise, you don't need any wrongdoing to terminate someone's employment.
http://www.expertlaw.com/library/employment/at_will.html http://www.bls.gov/opub/mlr/2001/01/art1full.pdf
Terminating an employee without cause is acceptable for at will employment, but it means you will be paying them unemployment.
Firing is terminating an employee with just cause and means you don't have to pay unemployment.
If this guys is letting people go because they don't fit into his super-culture, that is the former and not the latter.
Not that I am defending the article, I find the vague cultural fit and sweatshop vibe to be bad. I've watched amazing coders turn to crap after a couple of grind weeks.
Companies like google cause a salary imbalance here - they pay Bay Wages - in seattle.
Having hired and fired employees as an employer, and having been fired myself, I have two pieces of advice for readers here.
#1: this person is an asshat, and at worst is setting himself up to get sued, and at best, just fucked morale among his not yet fired rockstars who'll rightly wonder "Am I next?".
#2: suck it up. hiring is hard. it's inevitable that you are going to make mistakes. you can either hire people and see how they work out, or you can burn your technical team out doing endless interviews. pop quiz. what's even more annoying to your developers than unnecessary meetings? doing two hour long interviews with yet another not properly vetted by HR candidate, that's what.
I've found its easier to hire people on contract, see how they work out, see how they like the company, and go from there. One of two things happen. Either they really like the work and company and you like them (yay), or they mentally check out, and you both amicably part ways or figure something else out.
Hiring someone at below market pay, and then publicly slagging them like this, that's just low class.
What does Uberflip do anyway? (Never heard of them).
>You get this uncomfortable feeling when you see that hire [...] say goodbye at what you may not deem not a legitimate end of the day.
Come on Randy. I can smell bullshit management speak for "didn't work an unpaid extra four hours every day" a mile off here. Did you actually feel they weren't getting enough done or not putting in the work you paid them for? Why not say that if so?
>our 25 rockstar team members
I think the work rockstar has been hashed over here enough, but seriously. I'm sick of it being used a code word for overworked 20-somethings that don't know any better.
>And it’s definitely not to make it seem like we’re a tough or crummy place to work – pretty sure our Instagram feed would show otherwise.
Ooh, I can almost see the fun jumping off the page. Ski trips for the exec team, office pumpkin carving, #startuplife? There's hashtags so it must be a good work environment.
For Example:
Changing Jobs every 6 months - The economy has been shit for 5 years - and unless you have spent your whole career in the Bay Area - you're likely to have been job hopping from contract to contract.
Commute - again, this is highly tied to which market you're in. An hour away in Seattle is a doable commute - its either 30 miles (if going to Seattle) or up to 60 miles (if heading away).
Followup to Interview - I used to do this - but after getting no reply 90% of the time, I stopped. I now only do this if I'm really, really interested. Typically something that makes me really interested is a great resume builder, salary or benefits - I try not to apply for jobs that I don't find interesting from a technology level.
On a personal note: Lack of personalized cover letter - I've been in the position where applying for work was more like an assembly line - How personalized should it be? I have a form letter I modify light for each job I apply for - I'd be leery of any employer that expects me to write an essay of ball gargling - The cover letter IMO should exclaim my strengths to the job - not why I want to work for you - I want to work for you, because the work sounds interesting, and for one reason or another, I'm in a the market for a job.
The Good - Listen to your intuition - I think this is great advice - but only listen when its screaming - not just when you meet someone different then you. A warning, intuition is how you judge that 'fit to culture' - If your intuition says too many people are off - the problem isn't the candidates, its your culture.
Regarding this. I am afraid there are some people who just don't stay at any place for a meaningful period of time. And its not like they are getting fired all the time. These people just in their full consciousness and responsibility just keep hopping jobs in hopes of a mythical super career.
In my country(India) its standard to get a ~15% hike on a job change on your current pay. The net result is you have a market full of job hoppers with hardly meaningful experience. It takes some time to come to speed in your new job and you hardly do any work in your notice period. So you essentially do some small time work in the minute period of time you serve at any company.
What's worse is these people are expensive compared to actual genuine contributors, they hardly stay and contribute anything. Since they won't be around in your company in the next 6-8 months why bother hiring them at the first place. And given that, you can't trust them with any long term responsibilities. Or any work of strategic importance.
I'd personally love to come and work in India for a year, just for the cultural experience.
A interpretation is that the criteria they're using to hire, includes a large amount of personality-matching based on their description, could be drawing from a pool stocked more with winning personalities than with competent developers.
>one of our Bad Hires failed on three of the following items which are usually a make or break for me:
Sounds pretty serious. Let's find out what it is.
>They did not include a personalized cover letter with their resume when applying.
Oh my. No personalized cover letter? The bastard should be shot, or at least unemployed for the rest of his life. Or maybe instead the author should think for a moment why his number one priority (its the first thing he listed) when it comes to evaluating candidates has fuck all to do with anything that an actual adult might care about.
> They did not include a personalized cover letter with their resume when applying > They did not create a trial account of our product before the first interview >They did not send a follow up email after the first interview
But I'd have liked to seen a "didn't meet explicit 30 day objectives" rather than the touchy-feely reactions.
70k / 6 employees < 12k / employee.
That's a lot of money? That really doesn't seem like that much money, especially if the vetting paradigm allowed the other 13 employees to bring vastly more than that lost 12k / employee to the table.
Thanks god I don't work for you. I'd be a bad hire too. 5pm is the legitimate end of the day in US.
Minor quibble, but given that their two products are ostensibly not consumer-oriented --a content management tool for marketers and a tool for creating branded, flippable PDF viewers--, is it really too unreasonable that some candidates did not sign for their product? Or maybe it's just seen as a sign of lack of curiosity/interest about the company, dunno.
Particularly fire "fast" option, for the employees next job it raises uncomfortable questions of why. So the goal is to not hire bad people. If you did hire a person, own it up and provide them with close performance feedback. Fire people if you have to, but not before they had at least few chances to improve their behavior and were clearly communicated as to what is going to happen if they do not.
And if a few days strikes you as being too short, then try a week or two. Personally the only time I fired someone that was just not suited, was after two weeks. But in thinking back on it, I already knew this aftera few days, just needed some time, and some conversations with the employee to convince myself. Of course, part of that decision was that the conversations did not lead to improvements, but the important take away is to act fast on your hunches.
If you don't trust yourself to fire someone after 3 days then at least set up some tests that will provide you with the data to know whether or not the employee will work out.
It is better for everybody that way.
I'm no lawyer, but I wonder whether saying things like this creates legal liabilities related to employment discrimination by implying that the company makes hiring decisions on non-job related criteria.
If they're not building space-ships, robots, or general AI, I'm now officially at the stage of my career where I expect employers to get down on their knees and seduce me.
And I hope these aren't developers they were hiring and firing. The average salary of these bad hires was about $57,000 per year. (The total was $70,000, divided by 6 people who stayed an average of 75 days.)
Edit: http://www.youtube.com/watch?v=soxnNYT5res Found a video, yep, they look young.
Nevertheless, this Canadian employer should know better. In the first three months they can let people go instantly. If they aren't confident in the person after a few days, show them the door.
Next time spare me the article and just tell me the one weird trick.
If you inadvertently cross a few red lines as a new hire you can ring a few alarms in your hirer's mind. If those red lines are in the company culture that's fine, you might be a bad hire (or the company culture might suck, which should have the same consequences). But sometimes those red lines are totally hirer specific.
How does lunch help with hiring technical staff?