I do have the opportunity to work with technologies that I love, and I do have the opportunity to learn other things.
A very diverse company, with a lot of cultures and different people who share a common sense of respect for each other.
I love this. I have good hardware to do my work.
Very traditional company (in a bad way), prefers "tradition" over their employees. It is totally against remote work. The company will make you travel for 2 hours to be in the office to just talk to people that are remotely in another office. (I am the only employee of my team in my country, so I go to the office just to enter an online meeting to talk to my colleagues from another country that are also in another IBM office, just to talk to me via online meeting.)
Not organized when it comes to the real work. Engineers commonly execute multiple functions, such as being an informal product owner, informal lead, and informal team manager (because real managers are busy with other things than managing people), and are still considered just an engineer. On top of this roles accumulation issue, raises are mostly never given, even if you keep accumulating roles and responsibilities.
Development budget? Forget about it. It doesn't exist, and this is not because it is low or hard to get; it indeed doesn't exist at all! They will give you some free courses on their internal platform to learn. (The really good courses that are offered also to people outside are paid, even for IBM employees!!!)
The immediate manager of the engineers often struggles to arrange things for you. Engineers' environments take weeks to be in place. New positions in teams that we need people take months to be approved (approved, not hired).
I talk to my manager only once per month, and luckily neither me nor him are on PTO or sick leave, otherwise, it could be 2 months without seeing each other.
Read the cons.
The IBM interview process was quite clear and crisp. I attended a total of three rounds: * The first round was a written test of my technology. * Then, there were two technical rounds: a telephonic discussion and a face-to-face discussion. * T
The telephonic round was critical. A lot of algorithms and good technical understanding were tested. Questions around JavaScript Promises and the async mechanism were tested in depth. The complexity of algorithms and knowledge around algorithm analys
They conducted two technical rounds and one managerial round. They have a good interviewing process and usually stick to the requirements. The real problem arises during salary negotiation. They usually outsource hiring, so the consultancy agreed to
The IBM interview process was quite clear and crisp. I attended a total of three rounds: * The first round was a written test of my technology. * Then, there were two technical rounds: a telephonic discussion and a face-to-face discussion. * T
The telephonic round was critical. A lot of algorithms and good technical understanding were tested. Questions around JavaScript Promises and the async mechanism were tested in depth. The complexity of algorithms and knowledge around algorithm analys
They conducted two technical rounds and one managerial round. They have a good interviewing process and usually stick to the requirements. The real problem arises during salary negotiation. They usually outsource hiring, so the consultancy agreed to