Good salary, interesting customers and work, and exceptional peers (for me, at least).
It will depend where you are. IBM, particularly on the product side, is not one company but a collection of small companies. This is good; it allows that product the flexibility to operate as its own entity.
Highly unstable environment. Every few years, they will, without warning, just axe about 20%—seemingly just to keep everyone on their toes. This is usually sales and tech sales; lab services (where I was) are rarely touched.
Massively bureaucratic. It needs to be; it's a lot of people, but if that's the kind of thing that bothers you, think twice.
They make a big deal about there being amazing growth opportunities, but the reality is that if you are good at a job, you will stay there or get promoted into a management position, where you will stay. If you are not good, it's entirely possible to hide, which isn't great. Almost everyone knows someone who adds no value, shirks responsibility, and just collects a paycheck.
Listen to the voices from the coal face, the people who actually go and work with customers – lab services, CTPs, GBS. These are the people who can tell you how we are perceived and how to improve.
Ensure that across the workforce, everyone is productive. There are too many bad apples hiding in the organization.
Interviews with Red Hat HR. Asked about current and desired salary. Asked about past experiences, career plan, and what the main difficulties faced in their career were and how to deal with them.
It was good. All questions were clear, and everything was explained, including expectations from the candidate, the job profile, team vision, working hours, and work-life balance. Overall, it was a good experience.
Previous personal and technical aptitude tests. Interviews with various IBM architects. All of them disorganized, without a clear definition of the tasks for the role being hired for. Recruitment interview with Human Resources.
Interviews with Red Hat HR. Asked about current and desired salary. Asked about past experiences, career plan, and what the main difficulties faced in their career were and how to deal with them.
It was good. All questions were clear, and everything was explained, including expectations from the candidate, the job profile, team vision, working hours, and work-life balance. Overall, it was a good experience.
Previous personal and technical aptitude tests. Interviews with various IBM architects. All of them disorganized, without a clear definition of the tasks for the role being hired for. Recruitment interview with Human Resources.