The pros of this job are that it's a 9-5, but the hours can be flexible. You never have to take your work home. It's challenging in the sense that there is always something to learn and grow. Since HANA is such a huge product, you can never entirely learn everything.
This is an incident type role. When you start, you get the impression that you are part of development, but you quickly learn that it is a support role. Every day involves endless amounts of tickets to solve, and you never feel productive because it's a continuous conveyor belt.
You will quickly feel the effects of being pigeonholed.
You don't have much time to work on your own personal development because you are constantly working on tickets.
Progression in this role doesn't seem fair overall, and there is not a lot of transparency in this role.
Interview Stages: * Phone interview * Team leader interview * Group manager interview * HR interview
Primarily a technical interview. There were some Leetcode-style questions (easies) that used arrays, strings, and stacks. There was an emphasis on writing test code as well. Also conceptual questions related to Java and describing what your typical t
Interview for a co-op/intern position in Vancouver. It was around an hour online. I interviewed for two teams at the same time, so one software developer from each team was present. The interview was pretty standard.
Interview Stages: * Phone interview * Team leader interview * Group manager interview * HR interview
Primarily a technical interview. There were some Leetcode-style questions (easies) that used arrays, strings, and stacks. There was an emphasis on writing test code as well. Also conceptual questions related to Java and describing what your typical t
Interview for a co-op/intern position in Vancouver. It was around an hour online. I interviewed for two teams at the same time, so one software developer from each team was present. The interview was pretty standard.