ASML reviews

Some times a bit more of bureaucratic

- GLs are chosen because they work long for ASML, no because their leadership qualities. Ironically most GL believe otherwise (in own exceptional leadership skills) and it makes them...funny. Especially when they try to "exercise" those leadership skills on employees. - Doing more, writing more code/tests without clear thinking why and what is the end result, instead of achieving more with less. - Code legacy problems. Because of the thing above took place for the past 10 years, it is hard to trace exact root-causes of occurring problems. It can sometimes take day or two to find what happens there. - If you are a tester, who dreams about writing "smart" test cases and find tricky issues, forget about that. Most of the time you will spend debugging, looking WTF happens in the code and trying to find a root cause in long long logs with a lot of garbage information. - Many un-nonsense meetings with long presentations. If you appreciate a common logic, clear sense, transparency and added value of all things you do at work, then WTF feeling you will get very often during meetings there. - The huge difference between "official" message and way how this message is implemented by GLs. ASML claims that quality is important and they aim on Zero-defects policy, while in fact many GL focus on making themselves more important within the organization and political games rather than on bringing value to customers or making customers' lives easier. - Nobody cares to make things more efficient, well to make things with more people. - Strypes an an outsource provider for ASML is another story. They are capable of giving you a big headache in the end of the day. It is very known at ASML, but (again) because of political reasons nothing is done about it.