Teams sabotage each other to ensure that their competing ideas win; it seriously happens all the time.
Sadly, people play on Tom's personality to get projects done or tanked.
Many in senior leadership are clueless, or willfully ignorant, about what is happening in their teams.
Good ideas, especially those based in industry best practices, are often ignored or discounted because of "Not Invented Here" or early inventor syndrome. Because Akamai's tech was truly so great in 1998, they struggle to let go of parts of it that have now been leap-frogged, leading to a bizarre state of advanced and very clunky or backward and outdated technology, and not just for legacy systems but even new work.
As an example: The VP in our office showed up to work less a couple times a year, only when bigwigs would visit. Effectively delegating his entire job, even direct reports wouldn't be able to reach him for weeks at a time. He never did perf reviews or gave feedback. Nearly non-existent leadership for his teams, but he talks just enough of a good game to leadership to somehow get away with it for years now.
Get a CEO. Tom is an amazing scientist and mathematician, but focuses on numbers so much that he doesn't see the games played at the next level down, or how bad the politics have become.
This was a smooth, efficient, and quick process. A recruiter contacted me via email, and I had two more calls: one with the recruiter and one with the hiring manager. The recruiter scheduled an onsite interview (with travel). The onsite interview wa
Firstly, the technical recruiter called and asked about background and some basic technical questions. Next, there was a phone round with the hiring manager. Two programming questions were asked, and the questions were not difficult. There was no r
First, a manager telephone interview, followed by on-site interviews by other senior product architects and a product manager. The on-site interview was almost four hours. Interviewers were nice people and asked questions relevant to the position.
This was a smooth, efficient, and quick process. A recruiter contacted me via email, and I had two more calls: one with the recruiter and one with the hiring manager. The recruiter scheduled an onsite interview (with travel). The onsite interview wa
Firstly, the technical recruiter called and asked about background and some basic technical questions. Next, there was a phone round with the hiring manager. Two programming questions were asked, and the questions were not difficult. There was no r
First, a manager telephone interview, followed by on-site interviews by other senior product architects and a product manager. The on-site interview was almost four hours. Interviewers were nice people and asked questions relevant to the position.