That's my main takeaway anyhow. Extraordinary people command extraordinary compensation - if you can't cough up the cash you're not going to get to play.
That's my main takeaway anyhow. Extraordinary people command extraordinary compensation - if you can't cough up the cash you're not going to get to play.
The best combination of passion and reward I've ever seen has been small hedge funds and quant shops. They're smart, love what they do, and have equity and fat bonuses. I've been lucky enough to be both work with and be rejected by these guys and it's one of the few cases where I truly believed the 'one percent' angle.
I'm not being caustic with the simple search, a few of those have excellent resources and discussions. You can also research the top recruiting firms in NYC / London who specialize only in Quant dev related roles. Top-3 financial firms require an Extremely high level of math, PHd. (for Senior roles), no job hopping, a target school (very rarely State schools), etc.
http://www.wilmott.com/messageview.cfm?catid=16&threadid...
(A kind of cruddy tone, but informative): http://news.efinancialcareers.co.uk/Guest_ITEM/newsItemId-26...
http://www.amazon.com/Heard-Street-Quantitative-Questions-In...
Edit: My own Boolean's recruiting for entry-level Quant Developers. Very specific criteria. CS Degree (no EE / Math programmers), Target schools, (but, "top" state schools allowed), NO Masters / PHD (an argument over too much specializing or saturation of education, meaning, the fund wanted to teach the hire).
They would relocate / sponsor from anywhere in the world. Only very specific schools from out of country (like India, the The Indian Institute of Technology was the only school to look at).
site:linkedin.com (inurl:pub | inurl:in) (BS | BA | “B.A.” | “B.S.” | Bachelor) (2006 | 2007 | 2008) SQL (java | vb | "c++") (logic | algorithm | multithread | concurren* | "multi-thread") (Princeton | Yale | Harvard | Columbia | Cornell | Stanford | "Carnegie Mellon" | Rutgers | Amherst | Brown | Penn | Pennsylvania | MIT | “m.i.t.” | Duke | Northwestern | Tufts | "New York University" | NYU | Dartmouth | “cooper union” | bucknell) (-PHD -“P.H.D.” -“p.h.d”)
(BS OR BA OR “B.A.” OR “B.S.” OR Bachelor) AND (“computer science” OR “CS” OR “C.S”) AND SQL AND (java OR vb OR "c++") AND (logic OR algorithm OR multithread* OR concurren* OR "multi-thread") AND NOT (PHD OR “P.H.D.” OR “p.h.d”)
site:linkedin.com (inurl:pub | inurl:in) (BS | BA | “B.A.” | “B.S.” | Bachelor) (2006 | 2007 | 2008) SQL (java | vb | "c++") (logic | algorithm | multithread* | concurren* | "multi-thread") "greater new york" -PHD -“P.H.D.” -“p.h.d” site:linkedin.com (inurl:pub | inurl:in) (BS | BA | “B.A.” | “B.S.” | Bachelor) (2006 | 2007 | 2008) SQL (java | vb | "c++") (logic | algorithm | multithread* | concurren* | "multi-thread*") (M-PHD -“P.H.D.” -“p.h.d”
Harder to measure than pay, but so is being a top 1% programmer. This can be a good reason to talk about pay -- an employer can claim excellent culture without any truth to it, but it's harder to self-deceive about money. And pay often correlates to important ephemerals like respect.
In regards to top 1% compensation, the true top 1% aren't hireable because they have their own startup companies. The top 1% compensation as has been discussed on HN before goes to domain experts. Lesson learned: become a domain expert.
However expectation was 10 hour and 12 hour days, and work environment seemed, for want of a better term, hierarchically abusive.
Furthermore, anyone who's seriously good is contracting, which should net you around 5-600GBP/day.
Paying high wages to knowledge workers causes them in general to be less productive. The top 1% might rather go for the money anyway. But the top 1% also care about working conditions (more screen space, faster computers, fewer interruptions, etc). Perhaps more than money, after they're being paid enough not to have to worry about money.
What they found was that paying larger performance-related bonuses caused bad performance. I don't think the finding applies to base pay.
That said, you're probably right that working conditions will be more important past a certain salary level.
As a Python programmer, I care more about hard drive speed and a nice monitor, but if I had to compile C++ I would kill for a faster CPU, and more RAM.
Some things boost moral and make workers more productive, so the employer benefits twice.