Just read this pretty good piece, Recruiting Penn Engineers: Getting intro emails right.
Seems like the biz ppl have no idea how to recruit the engineering ppl, aka, us the hackers.
A couple of good points from the post.
Be humble and straight-forward: I believe you; this is an awesome idea. Engineers are by and large friendly, no-bullshit people. Please don’t throw words like synergy and competitive advantage around: they absolutely make sense in the business context and it’s great that you’re thinking about this stuff. As far as Engineers are concerned, though, this doesn’t make you look impressive or competent; it makes you look like a suit who is too focused on business-y things to understand the technical challenges involved in the work. Nothing is more annoying than working for somebody who you feel doesn’t understand your job.
Get your (technical) facts straight: Don’t ask for somebody with at least 7 years of Ruby on Rails experience. If you’re not sure why that’s funny, look it up. There’s no simpler way to get your email ignored than to show that you have no idea what work actually needs to be done. If you haven’t invested the bare minimum of time required to do your research, that says something about your approach to technical work. Don’t be a pointy-haired boss.
Remember this:
They are not the code monkey. You are the biz monkey.That’s just how it is.
And I think this is quite true. I do get some offers, and all the offers I’ve gotten so far are like this. I’ve been polite so far, except to the one guy who told me I should be happy with a $350 pay and no equity.
We are not the code monkeys, we are the guys who turn ideas great.
About Me 
Feed RSS | Subscribe Feed 
Twitter | Follow Me 
See my CV 
Facebook
Twitter
LinkedIn
RSS