FactSet Software Engineer II reviews

Factset is Hub to most of the laziest people in this world. Bad engineering practises and manager pleasing attitude is prevalent across all management hierarchy. Most of the people working in the company have no clue what company does and how they make money. The culture is like a financial bank where you have to report your manager with the monotonous work you are given every week. Creativity is not encouraged nor professional growth. I worked there for 2.5 years because I got used to doing nothing. The company just wants cheap mediocre engineers to keep things going on. Many people stick to the company because of their personal gain and have no professional interest within FactSet. Poor coding practises and legacy code is all over the place. Too much of internal politics to push back work. All managers try to please each other instead of focusing the real work done. There are always some re org changes going on. Upper management has no clue about their products. It's really a good company for mediocre people. Afterall not everyone is ambitious. All smart people leave the company in less than a year. Those who can't find a job are just stuck there.

* Huge inconsistency in how various teams and departments are run, so the overall quality of one's general work experience can be hugely dependent on the luck of the draw when one is assigned to a team (such as when initially applying and being hired). * Engineers are generally kept very much separated and isolated from other departments, especially the sales side, so required interactions (to respond to client issues and the like) can sometimes be somewhat tense and unpleasant due to the general social psychological principle of communication with an "Unfamiliar Them" often being more difficult and more prone to misunderstandings and latent subconscious attitudes about dealing with another group that one perceives is treated wildly differently from oneself. * A very outdated codebase that as an Engineer, one will frequently have to dig through to implement a requested change or bug fix, including, but not limited to, code written for an OS that is technically obsolete, with much of the current Engineering work being part of a multi-year effort to completely remove the reliance on this obsolete OS by re-writing code to be compatible with Linux. * Company-wide move to converting all office space to open-floor plans leading to increasingly noisy and distracting workplace. * Engineering advancement seems to largely fizzle out after one makes Senior Software Engineers, with a combination of hard work, managerial/people skills, and luck required to be offered any real expansion in role or responsibilities beyond that point.