All the individuals who I worked with at FactSet were fantastic. They're all motivated, skilled, and eager to help out coworkers. In ten years at FactSet, I never worked with anyone I wouldn't happily recommend.
In the ten years I worked at FactSet, communication between teams, individuals, and management progressively deteriorated. The problem accelerated when many experienced engineers started leaving, and left their systems unowned, because nobody else had the knowledge necessary to maintain them.
Management seems to think that when someone leaves, they can just assign a new person the job of being the expert on their product. But there's rarely any decent documentation, and no clear plan for transferring knowledge to the new "expert", so they're often left scratching their heads.
The use of "microservices" has exacerbated this problem: Now it's often difficult to find where the relevant code base lives. It's often split among dozens of interdependent projects that are hosted on multiple different cloud hosting services - and very little of this architecture is documented.
In general, all the individuals who work at FactSet are great, but they're constantly held back by a lack of basic information about the company's systems and products. By the time I left (2021), my job felt more like archaeology than engineering, because I spent nearly all my time trying to figure out how our existing systems were designed and what they were meant to do.
Management has been focused on high-level buzzwords like "Agile" and "Microservices". My advice is that before worrying about the high-level stuff, they need to make sure the basics are attended to. Make sure that every important system has at least two people who understand what it does and how to interact with it. Make sure that when people leave, their knowledge is transferred to someone else. For really crucial systems, maybe even have some written documentation.
These are the sort of things that nobody thinks to check, because they seem so basic and obvious, but that just makes it even more important to be sure they're taken care of.
Round 1: High level design - parking lot from class and DB structure and thinking out loud process how system will work Round 2: Removing inplace duplicates and provide what is maximum lexicographical string e.g. --> 1. Bab -->ba 2. Aabbxx --> abx
Major focus is on algorithms for the mid level candidates, for more experienced there is a lot of emphasis on design. There are different teams and each team interviews the candidate on different technologies. The teams work in C#, C++, Angular JS,
They conducted 3-4 rounds of interviews and then disregarded my expectations in terms of CTC. I was just expecting a 50% hike which they could not give. It was a waste of time to interview for such a company.
Round 1: High level design - parking lot from class and DB structure and thinking out loud process how system will work Round 2: Removing inplace duplicates and provide what is maximum lexicographical string e.g. --> 1. Bab -->ba 2. Aabbxx --> abx
Major focus is on algorithms for the mid level candidates, for more experienced there is a lot of emphasis on design. There are different teams and each team interviews the candidate on different technologies. The teams work in C#, C++, Angular JS,
They conducted 3-4 rounds of interviews and then disregarded my expectations in terms of CTC. I was just expecting a 50% hike which they could not give. It was a waste of time to interview for such a company.