Big ship, but lots of hierarchies and bureaucracy
Big ship, but lots of hierarchies and bureaucracy
Relatively stable job. Big name. Open-source friendly. Good process management for development. Some very cool tools and advanced research (but not always accessible to software engineers).
Too much bureaucracy. Too many hierarchies, and bloated. Too much politics. Bad compensation. Technologies aging, too old for the fast-paced tech world today. Moving slowly when it comes to innovation and new ideas. Work/life balance is bad. Sometimes you have to work 60 hours a week and be on standby or work on weekends, and managers will bug you after you leave the office for the weekends/holidays. Firefighting is a common thing. Testing is not thorough enough. Weak in the internet world. No great engineering/creative culture and belief. The company is more and more business/money-making focused.
Reward your core contributors well. Foster less politics, less bureaucracy, and fewer hierarchies. Cultivate a great engineering culture and move fast when it comes to new ideas. Move to the internet; the traditional software days are counted.
Was this helpful?
IBM Interview Questions
IBM Interview Experiences
Software Engineer
Worst. No management and valid justifications. They hire in bulk and don't value cream candidates. They called for a scheduled interview, but it happened to be a walk-in. My suggestion is to never go for it. I went at 10 am in the morning and got the
Software Engineer
The interview process included one online assessment (OA) followed by two behavioral interviews. The OA consisted of one LeetCode easy question and one LeetCode medium question. I passed all test cases for the first question and approximately half
Software Engineer
It was a 3-stage interview process. The first was a phone screen from the recruiter, followed by a technical phone screen, and then an onsite interview. I talked to a few managers, and they decided I was the right fit for the job. Most of the questio
Software Engineer
IndiaSeptember 28, 2014Worst. No management and valid justifications. They hire in bulk and don't value cream candidates. They called for a scheduled interview, but it happened to be a walk-in. My suggestion is to never go for it. I went at 10 am in the morning and got the
Software Engineer
Washington, District of Columbia, United StatesMarch 8, 2022The interview process included one online assessment (OA) followed by two behavioral interviews. The OA consisted of one LeetCode easy question and one LeetCode medium question. I passed all test cases for the first question and approximately half
Software Engineer
Toronto, Ontario, CanadaJanuary 1, 2015It was a 3-stage interview process. The first was a phone screen from the recruiter, followed by a technical phone screen, and then an onsite interview. I talked to a few managers, and they decided I was the right fit for the job. Most of the questio
