Morgan Stanley Associate Software Engineer reviews

- 1 hour lunch time that should be taken off - Parking fee

Work can get repetitive. Many times I find myself doing a glorified refactoring of poorly written or poorly planned code. You'd think there would be an extensive process in check to prevent poor code from going into production, but that's not the case. Teams need to enforce their own code review and audit policies and sometimes that's difficult when you are trying to hit big deadlines. IT support staff could use some work. There are no doubt talented individuals who keep good notes and are very good at drilling down issue solutions, but that doesn't save QA overall from being a giant sink. I think the QA teams need to be closely situated with the developers and create their test-cases co-dependently so they can actually understand the software; otherwise, developers may as well be the first point of contact. Ranking and compensation improvement is slow. There's a big bureaucracy in place for promotions and it can be very frustrating to work year after year without seeing any improvement. Getting ahead requires you to be very social which is not always the easiest thing to do.