Amazing management. Extremely kind and flexible to your external schedule. Meetings with your first-line manager don't feel like interrogations but like casual conversations where you chat about work and some common interests. Speaking with an executive feels the same as casually chatting with a coworker.
Great culture. People go out of their way to help you if you ask. There is no "cutthroat" attitude; everyone works together as part of a team and supports each other when needed.
Tons of great communities full of people who share similar passions. Great places to connect with other IBMers from around the world who share the same interests (hobbies, crafts, etc.) as you do.
Good pay; competitive and above average.
Lots of opportunities and incentives to work on skills that lead to promotion.
Depending on your team, you may have meetings either very early in the morning or very late in the day. This is due to the global nature of some teams.
Dental benefits could be better. There's little coverage for 'major' surgeries.
Requirements for moving up the band system are defined too broadly. For example, there are docs and even badges for "Software Engineer" career paths, but there is no distinction between Cloud engineers and Z (Mainframe) engineers, even though the type and scope of work is vastly different between them.
It was quite simple for me because I was a contractor on a small team of contractors. This is a good way for potential employees to learn about IBM and also for IBM to learn about them—a sort of test drive. Key things are execution, being thorough, a
The interviewer was thorough in the questions that she asked. The questions themselves were appropriate for the position that I was interviewing for. The interview process as a whole was pleasant enough.
The interview process began with a HackerRank test featuring two easy-to-medium level questions. Following the test was a technical interview where the primary focus was on Object-Oriented Programming (OOPs) concepts and Java basics such as methods
It was quite simple for me because I was a contractor on a small team of contractors. This is a good way for potential employees to learn about IBM and also for IBM to learn about them—a sort of test drive. Key things are execution, being thorough, a
The interviewer was thorough in the questions that she asked. The questions themselves were appropriate for the position that I was interviewing for. The interview process as a whole was pleasant enough.
The interview process began with a HackerRank test featuring two easy-to-medium level questions. Following the test was a technical interview where the primary focus was on Object-Oriented Programming (OOPs) concepts and Java basics such as methods