3 ms·
The reason for this is that if you haven't been coding (just managing) for 12+ years...you probably are not "hands-on" enough for a company of our stage. We ha
by justinY 13y ago
The reason for this is that if you haven't been coding (just managing) for 12+ years...you probably are not "hands-on" enough for a company of our stage.
We have gotten a lot of very smart but "big company" people who had applied for this position.
Sorry for the confusion however, most of our team is actually MUCH holder than the typical start-up: 500friends.com/team. We may be a lot of things but are definitely not ageist.
- el_fuser 13y agoBefore you edit much further: We want someone who has less than 12 years of MANAGEMENT EXPERIENCE. The reason is that if you haven't been coding for 12+ years...you probably are not "hands-on" enough This arbitrary cutoff makes absolutely no sense. I'd like to see your quantification of skill drop off per year of management. If what you are wanting is a hands-on technical manager, then you need to say so. And it shouldn't matter if the person has been hands on for 5 years or 20. But I feel I'm being a little too generous regarding your motives here.
- justinY 13y agothis has caused so many misinterpretations that I have edited it out of the post completely... But essentially, the ideal candidate was someone who was CODING 5-12 years ago...
- alternize 13y agoyou made the job ad look pretty bad now to people reading it with out knowning the first version... Note: Any notion that 500friends is ageist is a complete fabrication. This can be validated by looking at our team (link). really? this is how you chose to start your job ad now? that sounds so desperate, i'd never apply - not saying that i would have before, sorry :)
- el_fuser 13y agoAhhh. That makes a helluva lot more sense.
- deleted 13y ago[deleted]
- throwawaykf02 13y agoI think I know what you mean, but really, there must be a much better way to express this. For instance, instead of being quantitative, be qualitative. Don't say, "no more than 12 years", but say something like, "but still be able to code your way out of complex, practical software problems." Or maybe "code your way out of FizzBuzz"... Whatever. Just don't put a numerical value on it, because it is 1) insulting to many, 2) legally questionable, and 3) unlikely to actually find what you're looking for.