More emphasis on cutting costs than on producing great products and technology
More emphasis on cutting costs than on producing great products and technology
Lots of great people, and many teams are highly committed to customer success.
Constant cutting of benefits, corporate strategy to cut US jobs to fund expansion in China and India.
IBM was a better place to work 10 years ago than today. Few top SW engineers would want to work at IBM. Is this going in the direction you want?
Was this helpful?
IBM Interview Questions
IBM Interview Experiences
Applications Developer
Be very straightforward. Just relax and be yourself. Don't oversell yourself. Don't lie. Show interest and try to get an understanding of your job role to see if that's what you want to do. It's an amazing job, but you have to be really interested a
Advisory Software Engineer
After sending my resume, it took one month before I heard back for a telephone interview. Another three weeks later, there were two rounds of technical interviews before I received the job offer.
Compiler Tester
The interview was a 35-minute phone call. First, the interviewer asked me to briefly introduce myself, my project, and my programming background (e.g., how many lines of code I have written). Then, he discussed his team and their current projects,
Applications Developer
Portland, Oregon, United StatesOctober 14, 2022Be very straightforward. Just relax and be yourself. Don't oversell yourself. Don't lie. Show interest and try to get an understanding of your job role to see if that's what you want to do. It's an amazing job, but you have to be really interested a
Advisory Software Engineer
Portland, Oregon, United StatesDecember 1, 2011After sending my resume, it took one month before I heard back for a telephone interview. Another three weeks later, there were two rounds of technical interviews before I received the job offer.
Compiler Tester
Toronto, Ontario, CanadaMarch 1, 2015The interview was a 35-minute phone call. First, the interviewer asked me to briefly introduce myself, my project, and my programming background (e.g., how many lines of code I have written). Then, he discussed his team and their current projects,
