Great management with supportive colleagues. Might be an exception in the financial industry, as we worked in the technical department. Mostly a 9-6 deal.
Work is not incredibly interesting. Also, the supported technology being used is a bit behind the curve. It can be very intense and stressful during release periods, but that's probably normal anywhere.
Reduce the silo'd structure and create more integration, especially between former ML employees. This seems to be in process, but a lot of progress remains.
One phone interview with the hiring manager, and one in-depth face-to-face interview. The overall process took one month, start to finish. During the face-to-face interview, there were software engineering questions as well as behavioral questions.
It was good, not very organized though. The recruiter was not very sure of the requirement. The questions posed were good and required thinking. It tested the basic knowledge of coding. Someone who is able to write a program will succeed in the int
They had an initial written test, which was mostly on the core Java API. This was a bit awkward, as most of the class names started with a lowercase letter, which in the real world, none of the projects may have. After this, there was a technical rou
One phone interview with the hiring manager, and one in-depth face-to-face interview. The overall process took one month, start to finish. During the face-to-face interview, there were software engineering questions as well as behavioral questions.
It was good, not very organized though. The recruiter was not very sure of the requirement. The questions posed were good and required thinking. It tested the basic knowledge of coding. Someone who is able to write a program will succeed in the int
They had an initial written test, which was mostly on the core Java API. This was a bit awkward, as most of the class names started with a lowercase letter, which in the real world, none of the projects may have. After this, there was a technical rou