7 ms·
There's a way through this mess. First, focus on people that want to be hired. There's lots of people out there who tried to roll their own and realized it's a
by vinceguidry 12y ago
There's a way through this mess.
First, focus on people that want to be hired. There's lots of people out there who tried to roll their own and realized it's a lot harder than it looks. Plenty just want to focus on the fun tech stuff and leave client communications, marketing, and all the other small-business drudge work for others.
Second, be willing to build people up. Promote from within and let people grow into the role they want to have. Fuck a foosball table, I want room to grow. Convey this clearly in the interview. Leave off the X number of years in technology Y nonsense, and, if you're feeling particularly froggy, the demand for a four-year degree. Nothing about having one makes you any better at technology work, it's function is purely signaling. You can get a much better feel for who someone is just by listening to them talk about their pet projects or what inspires them or what they want to do.
Third, drop the pretentious bullshit. It's a seller's market for talent, you're courting them, do what you have to to minimize HR's influence on the process. Be responsive, don't ask stupid questions, do whiteboard exercises, all that tech interview bullshit that just skews the signal-to-noise ratio rather than increases it. You can get away with that shit if you're Facebook, but even there it's a dick move and it doesn't really help.
- cgh 12y agoAgreed. And don't be afraid to hire people in their 40s who might not fit in visually but nevertheless have vast experience building stuff that actually ships. And don't be afraid to hire remotely. You don't even have to go overseas - there is a vast untapped pool of underpaid talent in North America.
- jdhawk 12y agoPlaying devils advocate here: > And don't be afraid to hire people in their 40s Experienced, and expensive. Usually have families to support, and a greater desire for work/life balance. This does not mean they're less productive (per capita) but it doesn't fit the image of "start-up culture." Work long hours for peanuts, do what you boss says. > And don't be afraid to hire remotely. This takes damn good management/culture to work well. Someone who has faith in their employees. Someone that's not looking to blame everyone around them for failings. Someone who can see past the cognitive bias of the person down the hall, etc... There are lots of managers and lots of cultures. Not a lot of good managers in good cultures. EDIT: I do agree with you - just pointing out what I hear on repeat about the subject.
- kijin 12y agoPlaying even more devilish devil's advocate here: > "start-up culture." Work long hours for peanuts If your business model depends on people subsisting on ramen, and having no life outside of work, maybe what it really means is that your business does not deserve to stay afloat. Most startups fail anyway. You just fail earlier, because your cute Android game is not worth compromising the physical and mental health of everyone involved.
- amirmc 12y ago> ...be willing to build people up. Promote from within and let people grow into the role they want to have... I think this is one of the missing pieces in modern companies. Very few places really want to train you up and all the procedures and processes either expect that (1) your school/course should have taught you or (2) you should have already taught yourself.
- deleted 12y ago[deleted]
- amirmc 12y agoI don't understand what you mean. When I said 'train' I did mean as an employee doing actual work.
- jdhawk 12y agoThis goes back to people hiring for Tool Knowledge. Think of all the requirements you see on job postings. Must have X years of [insert hyper-specific tool]... Most hiring managers are looking to find someone they won't get in trouble for hiring if they end up sucking. This leads them to look for people who have used the same tools, not people who are intelligent problem solvers that can learn anything given a bit of runway.
- sliverstorm 12y agoWe certainly don't help the problem. I have a few friends who switch jobs every 9 months or so, which almost certainly makes companies wary of investing years of training.
- dllthomas 12y agoMaybe they wouldn't switch if they found similar advancement internally...
- wuliwong 12y agoFor myself, the desire to change jobs comes from the observation that the companies trying to poach me away are offering more money than my current salary even considering the foreseeable future of raises. I happen to like the people I'm working with, so I continue to stick around but at some point those numbers are going to get too far apart and I'll make a move. In my current company (very large), the prospect of raises and promotions are slow, small and far in-between. Maybe I'm in a weird place, but that's been my experience thus far.
- Nursie 12y ago>> Nothing about having one makes you any better at technology work, it's function is purely signaling. Better than someone with more experience, possibly no. Better than someone with similar experience but without the degree - hell yes. I'm still happy I did mine because it gave me a grounding in all sorts of concepts and it keeps on giving, even though I graduated 14 years ago now. A comp Sci degree is way more than signalling. --edit-- or perhaps I should say that a degree is no more signalling than experience is. I've worked with terrible, awful engineers who appeared to have both.
- new299 12y agoTalking to people, provides the best SNR. It's possibly best to down weight signaling from both degrees and experience.
- dllthomas 12y agoIs that true? I think I recall hearing that studies show interviewing actually usually leads to worse results. Here's one that seems related to academic admissions, not hiring per se, but similar vein: http://journal.sjdm.org/12/121130a/jdm121130a.html http://journal.sjdm.org/12/121130a/jdm121130a.html I think clearly the best SNR is from working with someone. That's not easy to fit into the hiring process, though...
- vinceguidry 12y agoI imagine that would be really hard to research in a coherent fashion. I personally know within minutes who I'll be able to work with and not. I look for three things. Have you shipped anything? Are you teachable? Can you put other's needs over your own yet still remain able to push back when necessary? Someone like that, I'd let him do anything.
- Nursie 12y agoI'm getting to quite like the idea of a trial period. I'm a contractor and I usually work to one. One day's notice for the first two weeks, if it's not working out (for either party) we say goodbye during that time. Crucially, the prospective employee/contractor still gets paid for that. Unlike with some of the "Hey, come work for us for free for two days so we can see if we like you!" arrangements I hear about...
- analog31 12y ago>>> First, focus on people that want to be hired. There's lots of people out there who tried to roll their own and realized it's a lot harder than it looks. Plenty just want to focus on the fun tech stuff and leave client communications, marketing, and all the other small-business drudge work for others. ... hired by a start-up, that is. Perhaps the dilemma is finding people who believe in start-up economics and culture, but don't want to found a start-up of their own. >>> Nothing about having one makes you any better at technology work, it's function is purely signaling. Likewise, nothing about having a start-up makes you any better at business -- its function is also purely signaling. My comments, while they seem pretty snarky, point to a sort of parallel issue between start-ups and job applicants: How does each "side" see past the signaling aspects of the other side in order to pick winners?
- cageface 12y agoFourth, be open to remote workers. Remote work has some downsides but there are a lot of skilled developers that don't want to live in the valley or SF. Many of us are even willing to work at a discount relative to SF rates.
- vinceguidry 12y agoEh, your business requirements are your business requirements. Work from home isn't something you can just implement in a day. You have to build your entire dev process around it. We're hiring for an entry-level Rails coder right now, our company culture just won't allow for remote. That may change in the future, but I'm not sure, even as the lead developer. Eventually we might start outsourcing some dev work, but I can't see us offering someone full-time salary and benefits to a remote worker. We're just not set up for it. I could demand work-from-home days if I really wanted to, but I don't. I like going in to the office.
- cageface 12y agoThat's a perfectly legitimate call to make, as long as you acknowledge the tradeoffs of excluding a lot of potentially qualified people.