* Bad projects. 99% of the projects are legacy, because ESW capital buys bankrupted companies, then pays you to make it better. Just think about it. You will be responsible to make failed legacy project work. By legacy, I mean, there is no documentation, code can't compile, etc. You have to arrange knowledge sharing sessions with legacy team (who by the way don't want to share it, because they will lose their jobs after that), you have to adopt all the code base to XO ecosystem. If you thinks it's inspiring, good luck!
* Very stressful environment. You have to deliver specific number of tasks completed every week. Most of the people can't deliver it because of the blockers you can't resolve. But management keeps pushing. You will feel a lot of pressure from them, which makes environment unhealthy.
* Very low chance to do what you know best and love. I was a .Net chief software architect for about 2 years, but never got a change to architect anything. In 99% of the time, you will be a regular software engineer, who tries to fix some undocumented stupid spaghetti code or if you are lucky, you may be part of the team who tries to rewrite it.
* Forget latest technologies. Well, they may be using AWS, docker, team city, etc. but as a .Net chief software architect, I care more about on using .net core not asp.net web forms.
* 90% of jobs are coming from one company (Aurea). This makes working at Crossover very risky in the long term.
