3 ms·
Never mind the specifics of the selection process, Silicon Valley's risk-adverse approach to hiring is baffling. Instead of making candidates go through an over
by Apocryphon 10y ago
Never mind the specifics of the selection process, Silicon Valley's risk-adverse approach to hiring is baffling. Instead of making candidates go through an overly rigorous process, why not embrace California's at-will status and hire and fire often? Employers and employees already view each other with suspicion in terms of loyalty, the former willing to downsize capriciously at any moment, and the latter willing to jump ship every year or two. So accept the mobility and instability of startups. Instead of spending immense resources on the interview process to find the perfect, you focus on getting the good and terminate swiftly if they turn out to be bad.
Not to mention, even when you have these types of interviews it still doesn't seem to filter out toxic people, such as the harassers of Susan Fowler at Uber.
Of course, it would be easier for workers to be okay with this arrangement if basic needs such as health insurance were decoupled from one's employer. That's another argument for single-payer in CA.
- ThrustVectoring 10y agoGood developers won't tolerate a contract-to-hire offer or will sniff out that they're a fire-fast environment. That, and it's pretty terrible for employee morale.
- Apocryphon 10y agoI'm not suggesting contract-to-hire, so much as a formalized and transparent concept of probationary periods. I'm pretty sure at-will employment means you don't need to bother with contract-to-hire unless you want to be cheap with paying your employees benefits. So these employees shouldn't be on contract anyway unless expressly temporary. It certainly would be terrible for morale if implemented thoughtlessly. But if it was done in a way with clear expectations of employee performance, then terminations would not be arbitrary. And the morale hit of being terminated at any time- a situation with legally exists in California atm anyway- would be mitigated by more companies being quicker to hire instead of forcing long arduous interview processes. So then the situation becomes "If mgmt. is just, then they will keep me on, if they are dumb, then I can get quickly hired across the street anyway."
- ThrustVectoring 10y agoSure, the end state of "everyone hires quickly and fires quickly" is better, but there's an intermediate state where only a few companies use the new paradigm. In that one, the "can get quickly hired across the street anyway" isn't true. And the people who get fired are going to spin narratives about how getting let go was management being stupid and untrustworthy, regardless of how true that is, so you'll wind up generating noise that scares off developers.
- munificent 10y ago> why not embrace California's at-will status and hire and fire often? This sounds like an utterly miserable experience for both new hires and coworkers of the new hire. Do you really want your company's onboarding process look like FNG syndrome? https://en.wikipedia.org/wiki/FNG_syndrome https://en.wikipedia.org/wiki/FNG_syndrome
- Apocryphon 10y agoSee my response here: https://news.ycombinator.com/item?id=14025297 https://news.ycombinator.com/item?id=14025297
- poikniok 10y agoBut why would anybody come work for you then? There are plenty of companies that don't fire, and they would be far more attractive.
- Apocryphon 10y agoThe interview process would presumably be shorter and less complain-worthy than the current industry standard.
- poikniok 10y agoWell I can confidently say that people I know don't have a problem with the current algorithmic interview process, in fact my friend group generally finds it fun, where as conversely I don't know anybody who would take a job with a non-insignificant chance of being fired.
- Apocryphon 10y agoThat's fair, and certainly there are plenty of engineers who are content with the current state of tech interviews, but there also seem to be many who aren't, given that this conversation is taking place on a comments thread full of criticisms of the tech interview process, and these threads seem to manifest at least once or twice a week on HN.
- enraged_camel 10y ago>>Never mind the specifics of the selection process, Silicon Valley's risk-adverse approach to hiring is baffling. I think it makes perfect sense. A bad developer hire is not just unproductive. They also tend to be a burden on their coworkers and reduce their productivity by asking trivial questions and writing buggy and/or hard to maintain code. With startups the risk is even greater. Think about it: the odds are already stacked against you. Why would you take even more risk by randomly hiring developers? Sure, you can fire them, but by then it may be too late.
- Apocryphon 10y agoI've read that rationale, and it makes sense, but it almost makes it sound like the organization is humoring a bad dev without oversight for months upon months until they suddenly realize their inability. Maybe they should spend more time actually running their company instead of interviewing candidates all day.
- aanm1988 10y agoSo fire them. Sorry, didn't work out. GTFO. The situation now is not better. People have cargo-culted a strategy that is based entirely on having enough applicants that you can afford to have a stupid false-negative rate. It's also easily gamed, so you have to keep trying to find new puzzles for people to solve.
- JoblessWonder 10y agoThere is a cost involved with onboarding/offboarding employees which is a common reason why this tactic isn't used. Between the time spend spooling someone up on your internal processes, completing required HR tasks, requisitioning equipment, etc it often makes it a pain to go with the hire/fire quickly method. I'm sure you could build your business around it, but at that point you might need to look at the moral of the company. Also, if you fire someone in California they will likely file for unemployment which means your UI reserve account requirements might go up.