Not really into software products
Not really into software products
Stable position once you are inside.
The networking can be very useful.
There is a culture of mentoring and networking that takes a certain amount of effort to get into, but does yield decent information.
Bureaucratic. Poor attention to quality. The overall software product strategy is lacking. Lots of vague, insincere, old-style rah-rah. Management tends to bring in their friends rather than hire for competency. Project schedules are set without understanding the details of what the commitments entail. The product designs tend to be overelaborated, inelegant, and user-hostile. They have a rigid, waterfall product management template, and they are attempting to ram agile development into it.
Make internal processes less complicated and more self-service. It is hugely surprising how inefficient the internal processes are.
Success at IBM lies in discovering what insane details and people you can just ignore.
Was this helpful?
IBM Interview Questions
IBM Interview Experiences
Advisory Software Engineer
Interviewed with two different hiring managers and four team members. Overall, it went well. Was very impressed with the working environment: labs, people, and etc. The questions asked were real-world questions, not from a book. Some were very tec
Advisory Software Engineer
I applied online, and two weeks later, I received an email inviting me for an interview. The process was quick. I was interviewed by four different people. After the interview, I was told they would get back to me in less than two weeks.
Advisory Software Engineer
The interview process typically involves initial screening, followed by multiple rounds of interviews with various stakeholders, assessments, and possibly a final interview or presentation before a decision is made.
Advisory Software Engineer
Austin, Texas, United StatesApril 1, 2010Interviewed with two different hiring managers and four team members. Overall, it went well. Was very impressed with the working environment: labs, people, and etc. The questions asked were real-world questions, not from a book. Some were very tec
Advisory Software Engineer
New York, New York, United StatesApril 1, 2014I applied online, and two weeks later, I received an email inviting me for an interview. The process was quick. I was interviewed by four different people. After the interview, I was told they would get back to me in less than two weeks.
Advisory Software Engineer
Chennai, Tamil Nadu, IndiaApril 3, 2024The interview process typically involves initial screening, followed by multiple rounds of interviews with various stakeholders, assessments, and possibly a final interview or presentation before a decision is made.
