A lot of brands, units, and an infinite amount of projects with great flexibility to move among them. This enables employees to change roles and move into new projects. Sometimes this even happens when the employee has no previous knowledge or experience in the new area.
Stable company, very focused on earnings and always with a vision for more growth.
We all work for the company stockholders.
This seems much more like a financial company than anything else (service, IT, etc.). Everything is calculated, and there is always a cost/risk pair to it.
Companies nowadays call their employees "resources"; IBM calls them "cost".
Too deep hierarchy. It's hard to know what is going on up there.
Managers are moved from projects/areas/units/brands every 2 years, so you get a new manager who might or might not know about your project and how your team works. This is usually really bad. As always, there are some exceptions.
Get to know your team, and also learn about Critical Chain.
The time between my first contact from the hiring manager and the offer was 8 days, which was very fast. I was contacted by email. A technical phone screen was scheduled for the following day, lasting 30 minutes. This screen had two parts: one was m
1. Phone interview with manager. 1 round-robin, in-person technical interview with the team (6 people). There were a lot of technical questions covering broad topics: * Networking * OOP * Infrastructure Virtualization * General Linux admin
One phone interview, which asked a few basic conceptual technical questions, as well as a number of non-technical questions. One onsite interview, mostly technical, but also behavioral. Spoke to two different software engineers during this role. D
The time between my first contact from the hiring manager and the offer was 8 days, which was very fast. I was contacted by email. A technical phone screen was scheduled for the following day, lasting 30 minutes. This screen had two parts: one was m
1. Phone interview with manager. 1 round-robin, in-person technical interview with the team (6 people). There were a lot of technical questions covering broad topics: * Networking * OOP * Infrastructure Virtualization * General Linux admin
One phone interview, which asked a few basic conceptual technical questions, as well as a number of non-technical questions. One onsite interview, mostly technical, but also behavioral. Spoke to two different software engineers during this role. D