3 ms·
I've seen a lot of people asking for a description of the problems the position will be addressing. Discussions with clients over the past couple of years have
by mgkimsal 16y ago
I've seen a lot of people asking for a description of the problems the position will be addressing. Discussions with clients over the past couple of years have led me to understand that in some cases, companies don't put out many specifics because what they want you to work on is a bit of a competitive advantage (in some cases this is even justified). Letting your competitors know you're hiring to build system XYZ to do ABC gives them a heads-up as to what's coming down the line.
Granted, this isn't the case in all or even most postings that are vague. But if other aspects look legit, but the posting is a bit vague, give them a little 'benefit of the doubt'.
- deleted 16y ago[deleted]
- dotBen 16y agoSo you are exactly right. I spend a lot of time trawling my competitor's job reqs (and even just those of interesting startups) to get a feel for what they are working on next. I still say that you have to alude to the nature of the problems you are looking to solve - it's better to have A1 suitable candidates and your competitors having some clue about what you are doing rather than be so vague that you miss all the good developers and your competition pwns you on execution. If you are hot then your competitors probably already know what you are working on from leaks, failed candidates breaking NDAs, etc. But most of the time no one really cares that you are about to spin up a map-reduce datastore and need folks with experience.