A shell of its former self... - Recensione dipendente - Program Manager presso IBM

companies still need mainframes, and IBM's legacy products still bring in revenue

management demands faster than necessary software release cycles which results in too much engineering time used on SDLC bureaucracy

Disclaimer: A lot of what I'm writing below of course depends on the work area and management chain. But I found this to be fairly pervasive policies in IBM in my 9+ years with the company. 1. IBM's policies and management are very flexible when it comes to working remotely or accommodating various life situations (sick days, doctor visits, etc.). Management is encouraged to measure an employee by their work and impact, and not by hours spent at their office. 2. Great colleagues! Though unfortunately, many have been leaving due to the instability of IBM's HW development business. 3. At least in my area, there's a high level of flexibility on which projects should I undertake based on my and my management assessment of business impact.

1. Unfortunately, IBM still uses the "normal distribution" rating system, where at the end of the year each employee is ranked as a top contributor (5%), above average contributor (15%), average contributor (~75%), and bottom contributor (5%). This curve is difficult to apply in the R&D world, where you may have many members of the team working long and hard hours, and end up being "average contributors" at the end of the year, because there just isn't room for all to be top contributors. 2. The above may not be so disturbing, if only IBM didn't practically cancelled all raises, performance bonuses and incentive for the non top-performers. I've had a consistent "above average" rating in the last 4-5 years, and my raise and performance bonus were ridiculous mere 1.5-2% of my salary. Were I rated "average contributor" I would have gotten NOTHING. So you can imagine that people can go year after year without any raise to their salary. From talking to manager friend, this is IBM's way to eliminate the non-top-performers without having to fire them, as part of its direction of reducing US manpower. 3. Hiring freeze in many areas - again, as part of IBM's attempt to reduce its workforce across North America and Europe we see many jobs move to the India and Far East markets. This is of course upsetting to see local teams shrink and disappear, especially when many great local IBM colleagues and experts begin to drop out. From my experience thus far working with India SW teams - they are still very far away from the standards I would have expected from US and Europe based teams. 4. Poor top down communication about company's and divisions' future. Employees learn from rumors and news websites what's about to come...