| I'm Jeff's business partner / fellow programmer. We do both algorithms and infrastructure. The markets continuously adapt. It's a constant balance between writing the code you need right now, managing the code you wrote a bit ago, tweaking your existing strategies / finding new ones. We have to know how to trade, come up with new strategies, and write fast solid software that can adapt to get a new strategy to market in very little time. After that we have to analyze our trades constantly to stay in the competition. We are market-makers (MM), so we don't care all that much about forecasting / direction. We want to fill order flow at the cheapest price that we can make a profit on. All the competition in our little MM niche of High Frequency (HF) trading revolves around a fight amongst market makers to give the best price possible to customer orders. This leads to very tight markets. That works out very well for customers. I don't fault previous employers for paying us what they did as the article mentioned. It's a lot more than I ever expected to make coming out of college. The article seemed to have a programmers versus industry slant that I don't quite agree with. In my opinion industry is being taken over by programmers. Companies have a natural upper bound they can pay any employee. After that, and I have been on both sides of this, either you can accept the comfort of a regular paycheck or you can throw that all away to take a risk and grow in a different way. If you take the risk you're throwing away a sure thing for upside. I don't have a family yet so to me it was the right time to do this. The `programmers revolt` has been over for years. Programmer's won. Markets are all electronic or will be soon. It is inevitable and good that this happens, in the same sense it is good that we put robots into factories, use statistics to optimize business processes, etc etc. It's been a longer road to getting to this point than the article mentions, my first bit advice for someone who in the trading industry and wants to branch out on their own, is it's going to be hard, just like any startup. The money you see the company you are working for making is the result of a lot of work, that you just can't appreciate until you have to do it all yourself from scratch. Which we have, twice. The article was a bit off on this, we already had our first `failure` and are trying again. This time we learned to keep our IP. With a startup, we've had to wear all the hats that as employee we didn't have to think about at all ourselves. It's a combination of awesome, daunting, miserable and satisfying, like any challenging endeavor. Personally I find creating something from the bottom up a lot more rewarding than grinding out a paycheck. |
Is it worth taking "MFE" style classes, like the ones offered at Baruch and NYU? Are the systems Windows or Unix? How much "advanced" math do you need to know? How much high performance infrastructure do you need to know? (networking, specialized storage & I/O, etc.) Is there a way to go directly to a startup firm, rather than first working at a bank or larger hedge fund? Are languages other than C++ used? Is it easier to do this in New York or Chicago? What bars should I hang out at in order to bullshit my way into an interview or partnership?