Stability, a reasonable salary, and an indoor kitchen.
Rotten inter-relationships and low development quality. SAP removed QA from the cycle, and nobody cares about quality. A large portion of the devs are either students, newly graduated, or temporary (6-month temp with one renewal). The veterans have been there for millennia and have not evolved professionally, so the development quality is horrible. Add this to the "quality within" strategy, where there is no professional QA in the cycle (the devs are responsible for quality, a sad joke), and you get a disaster. The rule of thumb says: "If it's bad enough, we will hear about it sooner or later from the customers."
The other issue is that it's a company where people want to keep their place at any cost and will do anything for it, including preparing "kill lists" on co-workers, documenting any minor screw-up of their "friends," and holding onto important technical knowledge just to remain a key element (passwords, accounts, knowledge of configurations, etc.). Politics is everything from the scrum masters level and up... just rotten...
Read the above... but everybody knows that nothing will be done by the management, so...
QA Automation Engineer. First round was entirely on Java. There were three rounds. The interviewee was knowledgeable. * Difference between final, finally, and finalize * Why are Strings immutable? Given an array of 0s and 1s, sort them. Count the
Technical interview. Asked a typical server client design question. On the one hand, wanted a high-level description of the solution, but mentioning all the hands-on bits. A bit confusing.
First interview: Over Zoom, LeetCode problems. Second interview: Over Zoom, LeetCode problems. Third interview: On-site, design OOP program for a given problem. Fourth interview: On-site with R&D manager.
QA Automation Engineer. First round was entirely on Java. There were three rounds. The interviewee was knowledgeable. * Difference between final, finally, and finalize * Why are Strings immutable? Given an array of 0s and 1s, sort them. Count the
Technical interview. Asked a typical server client design question. On the one hand, wanted a high-level description of the solution, but mentioning all the hands-on bits. A bit confusing.
First interview: Over Zoom, LeetCode problems. Second interview: Over Zoom, LeetCode problems. Third interview: On-site, design OOP program for a given problem. Fourth interview: On-site with R&D manager.