I have worked with IBM for over 10 years in a variety of roles.
There are pockets of really, really talented and great people.
Part of the benefit of working for such a large company is the ability to sync up, learn, mentor, etc., with these pockets of people.
The flip side of working for such a large company is the more common pockets of teams that are either bureaucratically challenged, stale, and/or not high-performing. The trick is to connect with the right people to avoid becoming one of these teams.
Don't become stale.
The interview process was very rigorous. Questions covered development methodology, release processes, large group development, and more. On the software side, specific programming skills were tested. A large project was given as an example, and can
The process is simple. Recruiters reached out to me, and after an initial discussion, I shared my resume. A tech interview was set up, followed by another tech interview, and then a manager interview. The process is long; they took almost 15 days to
It was a phone screen for about 30 to 45 minutes, focusing on the concepts of what I have done. The discussion centered on networking and OS concepts. Then, there was a direct onsite interview. This focused on C coding, reversing a linked list, and
The interview process was very rigorous. Questions covered development methodology, release processes, large group development, and more. On the software side, specific programming skills were tested. A large project was given as an example, and can
The process is simple. Recruiters reached out to me, and after an initial discussion, I shared my resume. A tech interview was set up, followed by another tech interview, and then a manager interview. The process is long; they took almost 15 days to
It was a phone screen for about 30 to 45 minutes, focusing on the concepts of what I have done. The discussion centered on networking and OS concepts. Then, there was a direct onsite interview. This focused on C coding, reversing a linked list, and