Quantitative Software Engineer • Former Employee
Pros: - Compensation (for me was a 30% raise from my old job)
- Benefits, $10 to lunch every day and probably the best health insurance I'll ever have.
- Everyone has heard of AQR and they're considered to be one of the best in their respective industry.
- Extremely smart people and high standards which definitely helped me grow a ton as a software engineer.
Cons: - The location sucks. It's close to the Greenwich train stop at least. I can't help but think they'd be able to get more young talent if they had an office in New York. Before joining I justified the hour+ commute to Greenwich in my head but it wore on me over the course of the year that I was there.
- As a software engineer, you're going to end up spending a lot of time dealing with production issues as opposed to building out robust solutions to problems. Engineers with PhDs end up having to debug problems that at other firms would be done by production engineers.
- DevOps/infrastructure-wise, the firm has poured a lot of resources into improving in this area but the results aren't immediate due to the amount of legacy code and processes.
- The interview process is conducted by VPs from a variety of teams. The result is that you don't get a great idea of what the people are like on your future team if you accept an offer. I didn't do my due diligence in this area post job offer and
I ended up on a team that I never really vibed with unfortunately.
- The work culture: now this probably is team dependent but I never really felt like I was encouraged to ask questions about things that weren't clear to me; I didn't have a lot of exposure to finance before joining so a lot of concepts were foreign to me, so it was overwhelming to have to figure out everything on my own in addition to learning a bunch of new tools that I hadn't used before.