3 ms·
Recruiters could at least ask coders what coders are interested in. I get a few emails per month from recruiters/CEO's and they are invariably doing the same mi
by alkonaut 9y ago
Recruiters could at least ask coders what coders are interested in. I get a few emails per month from recruiters/CEO's and they are invariably doing the same mistake: they enthusiastically describe their product but not what I'm interested in: tech stack, new/old code, office location, team size, role/responsibilities...
I don't care what the product is if the tech stack is wrong, and with the right tech stack and other circumstances I can work on any product.
- tejasmanohar 9y agoMaybe it's telling of what they want to recruit for. If the CEO is emailing you, I presume it's an early-stage startup. When I join a startup, I care more about the product and growth than tech stack, but the tech is a factor once I have multiple companies that are a product fit. I suppose everyone has different priorities... I wonder if there's a good survey on this from a lot of engineers (divided by title, region, etc.).
- alkonaut 9y agoNo, zero early startups as far as I know. Some young-ish companies though. I'm not interested in working in a rapidly growing business or one where there is a single make or break product being created at an early stage. Most of these are like "we make a product that compares car insurance so that [goes on to describe at lenght how awesome the product is]" I mean it's cool if it's a great product (I guess) but again, tech matters (more). Writing about tech, processes, team size etc doesn't necessarily exclude writing a long bit about the product either. My issue was that they are 100% product.