Ask HN: posted startup jobs at github, 37sigs, and only 6 resumes?
We posted our startup jobs (pretty great jobs I'd say, exciting startup, well paid) in the best places we could think of:
* 37sigs: http://bit.ly/g24KTD
* Stackoverflow: http://bit.ly/gchGuU
* Github: http://bit.ly/dSzOvu
* and our blog of course http://blog.getgush.com/
Only 6 resumes in a week. Half of them worthless. Is this typical? I would have expected quite a few more applications, these job postings are fairly expensive. How have others faired with these job boards? Is there something wrong with/missing in our job posting?
(
26 comments
| 7 points
| on HN
)
"Working remotely is possible." How remote? Would I have to live in Canada? Is USA ok? Further afield? Would you want me to come into the office at least once a week? Once a month? Is "never" ok?
Do keep in mind a lot of the boards are US-centric, which might also change the response rates.
I mentioned this in an article I wrote last week: http://blog.coderstack.co.uk/lean-vs-vc-how-were-taking-on-s...
But essentially it comes down to one of the biggest complaints about the job boards you've mentioned is that they charge the same price whichever city your in. Even if they only have a tiny handful of developers who would consider working in your city.
Your best bet is to use a specialist local job board if one exists or otherwise reach out through the local startup community.
Does not saying what we do reduce the chances that you'd apply?
You say that you've got reasons for not telling the world, and I understand that. However, right now your ad seems to say "Hey, we're using a bunch of new technology to do something. Send us a resume!" Even changing the first paragraph to end "... to design scalable, distributed applications for robotic dental hygiene" gives me an idea about what I'd be working on (robots with floss) and hopefully doesn't give away too much of your stealth edge.
As for my application, I am expecting a baby in a little under two months and don't plan on switching jobs at the moment. I am always looking for interesting "5 to 9" work to complement my "9 to 5" and if you can accommodate that I'd love to talk to you. All that is to say that there are other factors at work besides your ad that keep me from applying at the moment.
Reduce? Try "eliminate." I would never bother applying to a company where I don't even know what they're building.
If you're that alpha/stealth, you'll probably fare better recruiting locally through referrals from friends / colleagues / former co-workers / local user groups / etc.
Yes.
I'll happily spill the beans during an interview,
That's nice, but what's the incentive for people to come interview with you, just to find out what you're doing? Like others have said, you don't have to give away deep, deep details, but you need to at least give an abstract description of what you're doing.
I just don't want to post it out there just yet (we're barely getting started).
I think you're worrying about this WAY too much. It's not like there's a gaggle of idea-starved hackers sitting around watching your job postings, just waiting for a chance to jump on your brilliant idea, execute it better than you, and steal your market from you. Somebody - I'm thinking Steve Blank, but don't quote me on this - said something like "If your idea is any good, you'll have to beat people over the head to get them to go along with it." I'd take that to heart if it were me. <shrug />
But if you really want to stay stealth, why not stick to recruiting locally through trusted connections? What you're trying to do here seems almost like a fundamental contradiction. "Advertise widely, but keep everything a secret." I'm having a hard time seeing how that's going to work.
We've updated the job postings with a little more info. We're basically in the photo space, but NOT another mobile photo sharing app.
http://jobs.github.com/positions/45d7614a-4f24-11e0-9e2f-43f...
http://careers.stackoverflow.com/jobs/10660
Also a note, HN automatically truncates overly-long URLs so you don't usually need to worry about pre-shortening.