Not good for development
Not good for development
Good for experienced engineers who want to coast until retirement.
Old tech, no pressure to perform.
Good on resume.
Old tech, low pay compared to other F500 tech companies. No incentive to perform, so it's awful for young developers. Random layoffs; nobody is safe any quarter.
Stop laying off every quarter. Hire good engineers by raising pay, and then you’ll get a good product.
Stop acquiring companies and then placing money in sales to sell them to clients while engineers suffer.
Additional Ratings
Was this helpful?
IBM Interview Questions
IBM Interview Experiences
Software Developer
I was contacted by a college alumnus who was employed at the company. The initial process was a phone screen and technical questions to see which role I would fit based on my experience. After the initial phone screen, the recruiter set up a call wit
Software Developer
Intermediate level Java questions revolved around Core Java principles like Object-Oriented Programming and the usage of Data Structures. The coding assessment was like a LeetCode easy and medium. The behavioral test was very standard, based on com
Software Developer
Simple coding and puzzles. Asked detailed questions about my projects: * What problems did I face in completing them? * Given a situation, how to implement it in my project. HR was tricky.
Software Developer
Austin, Texas, United StatesFebruary 1, 2014I was contacted by a college alumnus who was employed at the company. The initial process was a phone screen and technical questions to see which role I would fit based on my experience. After the initial phone screen, the recruiter set up a call wit
Software Developer
United StatesFebruary 12, 2025Intermediate level Java questions revolved around Core Java principles like Object-Oriented Programming and the usage of Data Structures. The coding assessment was like a LeetCode easy and medium. The behavioral test was very standard, based on com
Software Developer
Cochin, Kerala, IndiaSeptember 1, 2022Simple coding and puzzles. Asked detailed questions about my projects: * What problems did I face in completing them? * Given a situation, how to implement it in my project. HR was tricky.
