Pros: Smart people: some work is boring, some is fun.

Cons: Sometimes bureaucracy can be a challenge.

Pros: Citadel is a true meritocracy with a strong culture of ownership and "getting stuff done." There is a lot of autonomy given to developers. You are encouraged to diversify your skillset by constantly learning on and off the job. On different projects, I have not only been the software developer but also a product manager, quant researcher, or product evangelist, based on what aspect of the project interested me. Talented peers from different backgrounds are always willing to help you learn new skills. As someone who joined through the new grad program, a lot of support and guidance was provided in terms of classes, tech talks, speaker series, and various mentorship programs. The rotational program also allows you to find a team that is a perfect fit for you. Titles mean very little at Citadel, and the organization structure is very flat. Junior people who show promise are encouraged to take on more responsibility and are pulled into mission-critical projects. Portfolio managers, traders, and analysts appreciate the importance of technology and quant research and are constantly trying to incorporate it into their investment process. Citadel is especially rewarding for those engineers who are willing to put the effort to understand financial markets. Software developers are constantly reminded that they are there to solve problems and not just write code.

Cons: Citadel demands 100% from its teams and individual members every year. This leads to a cycle of a multiyear period of stability (4-5 years) followed by a short period of turnover (6-8 months). This cycle has its obvious cons, but for ambitious team members, the period of turnover actually creates a lot of opportunities. Software developers are encouraged to understand and solve problems. Sometimes these problems are ambiguous, and the specs provided are loose. If you are scared by ambiguity, then this may not be the best place for you. There's a 60-40% split of long-term vs. short-term projects. Engineers, especially in the front office, may be required to context-switch based on market conditions. Citadel is a big consumer of open-source projects but doesn't have a strong culture of contributing back to them.

Pros: The comp sets the bar for the entire industry. Free, albeit largely bad, food.

Cons: The vast majority of the "engineering" work at Citadel is low-level maintenance and end-user support. The focus is keeping the lights on, with effectively zero thought given to longer-term projects. The engineers who succeed here are the types who can produce huge amounts of exceedingly mediocre code on short notice. Despite the nature of the work, this is a high-pressure environment. Management talks a big game about investing in technology to scale the business, but ultimately this means turning the screws on lower-level employees, rather than actually building scalable systems. Eventually, systems/groups end up in crisis after one too many patches/hacks. The response to such a crisis is inevitably a kind of Banzai Charge – throw guys at the problem until it has been hacked into submission in the immediate term, then pray it stays working through the next bonus cycle. I can only speak for the engineering side; I assume, given the success of the fund, that other areas are better.