Live data from Hacker News

The Way We Hire Is All Wrong

medium.com

101–110 of 143 posts

Re: The Way We Hire Is All Wrong

#101

What a bizarre and compelling story. Glad to have read it. Meanwhile I think the hiring problem/solution is staring us right in the face. What would the world be like if contract/freelance/part time/short term work were the default? Isn't it perhaps weird that there is an assumption companies and employees should bind their fates together, and, if it doesn't work out, one or both parties is pretty screwed because of…

People have kind of touched on this a bit, but I just want to say this as explicitly as possible, because I think this is a thing that's been kind of forgotten over time: Forcing employers to commit to their employees on some level was one of the most significant achievements of the labour movement.

Most people don't really want to have the 'flexibility' of working, because that also comes with having to find work on a regular basis. In some post-scarcity or at least post-austerity society this might be something people are willing to do, but most people aren't working because that work is something they have a passion for, they're doing it so they can do other things like have a home and a family.

Employers of this kind of labour would love nothing more than to schedule you whenever they felt like, have more part time employees at lower wages, and let you go if you miss even one shift.

Re: The Way We Hire Is All Wrong

#102

Earlier quoted context omitted.

I have no idea why this comment got so downvoted. This is exactly the software I've spent the last year building and it works incredibly well for our customers.

I think it's the "software" part that is getting down voted not the 5 attributes... I'm legitimately curious, how do you measure those things quantitatively?

You measure them relative to those who achieve high performance.

Re: The Way We Hire Is All Wrong

#103
This is awesome; I am so thrilled you are talking about this.

I am preparing a response to Deborah’s article; working title:

A Hackathon Cannot Fix a Broken Hiring Process. But the Right Experiences Can.

You see, in 2004 my life changed when I started caring about the people I did not hire. You discussed that here: https://news.ycombinator.com/item?id=8859199

But the thing you probably don’t get, and I didn't get until much later, is that I did not create a hiring process.

And it sure wasn't a contest with a job at the end (as many of you think).

It was an experience.

For the people who engaged with the experience it was life-changing. For those who didn't it wasn't.

Certainly for the people I hired it was life changing.

Changing jobs will change your life – what would be the point otherwise?

And certainly going from unemployment to employment changes your life; how could it not?

And working for me will definitely change your life because I grok this better than almost anyone you’ll ever meet.

But I want to change everyone’s life whether they work for me or not because I never wanted to be a programmer, or an analyst, or a hedge fund manager or all those other things I have had the accidental good fortune of becoming.

All I've ever wanted to be since the sixth grade is a teacher. See this: http://internationalfamilymag.com/IFarchives/archives/sep07/...

Most of the attendees experienced a hackathon because they couldn't figure out how to experience anything else. After all, this was held in the Bay Area in 2014.

The exact same thing could have been held in London in 1842 and yet nobody could have possibly experienced a hackathon back then.

When you read her article, notice that Deborah poses a question but doesn't answer it. She talks about her experience of the other attendees but doesn't offer to introduce any of them to readers who might be hiring. She ends the article with a really good suggestion that someone should create Smartup Weekend to slap some sense into employers. She asks, “Who wants in?” But she doesn't even buy the domain name. Doesn't she know that you shouldn't mention a domain name you don’t own in a coffee shop anywhere near San Francisco because the guy next to you will buy it and then try to sell it to you for $10,000. And NEVER EVER do that in print. (Of course, as soon as I read her piece I snapped up SmartupWeekend.com and I offer to transfer it to anyone who can convince me they will actually build something rather than just talk about it. I’ll give it to you for free on condition that if you don’t do much with it then I get it back.)

In short, so far Deborah has reported on her experience, but hasn't fully ENGAGED WITH IT.

Deborah’s experience of Staffup Weekend is only beginning now. I am confident that someday she will see that weekend as a pivotal point in her life.

I’m less sure about the rest of the attendees because I have seen no evidence they have engaged with the experience as anything but a contest they have lost. After all, Deborah organized a 1-month reunion and nobody showed up.

There is still hope if these folks reflect on what happened, refer to their notes (surely they took notes), then refactor the whole thing and reflect on what they can still learn.

But even if they don’t do that, I’m sure every one of them could be excellent employees under the right circumstances because, as Woody Allen says, 80% of success is showing up and they did way more than that. You can see everyone here: http://staffupweekend.org/2014/11/22/report-on-staffup-san-f...

If you’d like to meet any of them then let me know. I’ll gladly make the introduction.

Re: The Way We Hire Is All Wrong

#104

>Staffup Weekend put the lie to Stein’s pronouncement. As Nicholson later wrote me, “The fact that people stayed for 48 hours to work on something put them head and shoulders above the thousands of applications we receive, because the participants are people who show up and see things through.” And this event is an attempt to make showing up for a 48 hour 'work trial' a norm. This favors the younger, single populatio…

My first real job interview in 1999 worked exactly like this. A pool of candidates came in and were given the same 2 day coding assignment. We were paid for our time and worked on site. It was a great experience, but I tend to like working on interesting problems (which I guess is a valuable trait in itself). It especially made sense at this company because they were using an obscure coding platform and needed to tra…

I had something similar, 2 days, took me 12 hours of thinking/programming/etc.. time. Didn't get the job, didn't get paid for it!

Re: The Way We Hire Is All Wrong

#105

>Staffup Weekend put the lie to Stein’s pronouncement. As Nicholson later wrote me, “The fact that people stayed for 48 hours to work on something put them head and shoulders above the thousands of applications we receive, because the participants are people who show up and see things through.” And this event is an attempt to make showing up for a 48 hour 'work trial' a norm. This favors the younger, single populatio…

"One reason is that employers can easily be flooded with hundreds, or sometimes thousands, of applications"

We're told our immigration policy has caused a drought in programmers, yet employers are flooded with applications from the nonexistent workforce.

Re: The Way We Hire Is All Wrong

#106
post #35

Earlier quoted context omitted.

Another option would be to hire fairly leniently, but prune ruthlessly and early. In most jurisdictions, there is a trial period of sorts, typically 60 to 90 days, during which it is easy to fire an employee, before various rules about dismissal kick in. As far as I know, most companies don't really make use of this, except in really serious cases. But assuming it is in fact easy to fire during this period, we could…

How long until you run out of applicants willing to take the risk of having to restart their job search after they've settled down?

Assuming we only care about applicants who believe themselves to be competent, that depends how much they trust you not to make false-positives.

"They let a lot of their hires go in the first month, but that won't happen to me."

Re: The Way We Hire Is All Wrong

#107
post #26

Earlier quoted context omitted.

> What would the world be like if contract/freelance/part time/short term work were the default? That's actually one of the reasons I find the idea of a guaranteed basic income so promising. The biggest thing making an "everybody freelances" world a dystopia rather than a eutopia (sic) is that it would eliminate any semblance of income stability. Static long-term contracts would still be an option because of the reli…

a dystopia rather than a eutopia (sic) This is an awesome typo. "Utopia" is a transliteration from Ancient Greek meaning "No place." The same rules of transliteration would make "eutopia" mean "good place." "Utopia" came into English through a satire, the meaning being that nowhere's really paradise, but today we mostly use it without that edge, i.e., as if it really were spelled "eutopia."

I don't think that's a typo. I think pluma added (sic) to point out that he spelt it differently on purpose, not that he's quoting someone verbatim.

But thank you for teaching me about eutopia!

Re: The Way We Hire Is All Wrong

#108

>Staffup Weekend put the lie to Stein’s pronouncement. As Nicholson later wrote me, “The fact that people stayed for 48 hours to work on something put them head and shoulders above the thousands of applications we receive, because the participants are people who show up and see things through.” And this event is an attempt to make showing up for a 48 hour 'work trial' a norm. This favors the younger, single populatio…

"One reason is that employers can easily be flooded with hundreds, or sometimes thousands, of applications" We're told our immigration policy has caused a drought in programmers, yet employers are flooded with applications from the nonexistent workforce.

It's not that companies can't find programmers, it's that they would rather find elite programmers than develop lesser ones.

Re: The Way We Hire Is All Wrong

#109
post #93

Nicholson here. I sponsored Staffup Weekend, brought Brooke Allen to SF, and helped Deborah Branscum write her story for Medium. I did it because I'm the in-house recruiter for FutureAdvisor ( https://www.futureadvisor.com ), and recruiting is a mess. FutureAdvisor hired me to do PR. But after we raised our Series B last year, our main problem was converting capital to talent, so that's what I did. I didn't choose re…

It sounds to me like FutureAdvisor might have a problem with low compensation. Previously you mentioned making 8 offers at this event, and only one accepted. And these are candidates who specifically had 2 days free to work on receiving a job, so they have lower compensation requirements then an average dev of equivalent skill, and still 7 of the 8 rejected your offer. This doesn't seem to me to be a problem of marke…

That would be fair to surmise, but incorrect. While most startups cannot pay Google salaries, we are competitive with our salary-equity mix. It took us a while to learn what the market price was for various types of roles, and we offer that.

We made 8 interview offers. 7 people either chose not to continue or were rejected by my teams further down the line.

Some of those who chose not to continue were not devs, but client-service specialists. This was not a purely technical hackathon. Many of those people decided they did not want to deal with the math involved in financial services.

You have to remember that SF is a very competitive job market. Devs are choosing jobs that fit their salary expectations, but also their lifestyle choices and their passions. We meet those needs for some people, but not all, since they are idiosyncratic.

Re: The Way We Hire Is All Wrong

#110

>Staffup Weekend put the lie to Stein’s pronouncement. As Nicholson later wrote me, “The fact that people stayed for 48 hours to work on something put them head and shoulders above the thousands of applications we receive, because the participants are people who show up and see things through.” And this event is an attempt to make showing up for a 48 hour 'work trial' a norm. This favors the younger, single populatio…

My first real job interview in 1999 worked exactly like this. A pool of candidates came in and were given the same 2 day coding assignment. We were paid for our time and worked on site. It was a great experience, but I tend to like working on interesting problems (which I guess is a valuable trait in itself). It especially made sense at this company because they were using an obscure coding platform and needed to tra…

I think the key part of that is: Getting paid.

I'd happily do that type of interview as two days of money coming in is still great in its own right when you're unemployed.

Plus it seems like an utterly fair way of evaluating candidates that I don't really feel like trick questions, riddles, and high pressure whiteboard challenges accomplish.

One question/concern I have is: How much paperwork is involved in paying someone for just two days? For example, do you now need to file tax stuff (both state and federal), and how do you physically pay them (e.g. set up bank transfers, cash, etc)?

In an ideal world you'd just have people in for two days and hand them a small wad of cash at the end. But with the laws on the books and complexity of employment in general, something tells me the overhead of such a thing would be problematic.

Post reply on HN