Instead of Cons. I put my review from the perspective of technologies.
== Technologies ==
I don’t recommend this company, especially for engineers. If you want to have some experience with CDN, go to Fastly or AWS.
Akamai CDN is based on old physical server technologies, there a lot of legacy operations that seem to be automated very easily. Akamai is trying to move on to new technologies, but it's too slow.
The number of CDN servers is still number one in the world and the strongest point from the perspective of capacity. But Akamai started losing the advantage as other cloud vendors are focusing on CDN.
And I feel making things more complicated by dividing into many manual tasks is the typical Akamai way while many tech companies making things easier with technologies.
There are many small products based on CDN which could be a simple product with other venders. I would say they are coming from too many organizations and politics. The way I look at it, to create more positions, Akamai has needed to divide one product into many products.
Maybe there is so much to do. But that would be because of a lot of manual work which comes from the immaturity of legacy product architectures and approval processes which have to go through many people. It's very common for engineers to say that they feel they are wasting their time, should be able to consolidate these tasks.
For example, with AWS, you may be able to do a task in 5 minutes. With Akamai, it takes one month or impossible. If it's a simple task, these things could happen very easily.
And roles are divided into many job titles. So, your responsibility would be very small. Depending on your situation, most of the tasks you do could be clerical tasks.
At least I know a few guys who weren't satisfied with their roles and quit saying that their responsibility is too small and they can't understand why a simple single task requires many people. So, if you have good work ethics to learn more and work hard, I think this is not the place you should belong to. You would encounter a lot of red tapes and politics, local rules by cliques.
For example, in other companies, one person can manage and complete one simple task. But in Akamai, sometimes it can be called a project and may require three or four people. But you can’t tell these things from job description open on the internet.
Akamai is trying to expand into new technology areas such as enterprise security which are completely different from CDN.
But Akamai has track records keep failing new business. You can find them if you look up on the internet carefully.
As I see it, Akamai tries to put those new businesses into the same business framework as CDN. So, Akamai still has difficulties to get those new business rolling. So, you shouldn’t expect much in these areas. Some people may like birth pains to create new things and get new business rolling.
But I think only you can encounter there would be politics and red tapes, a lot of reasons "we don’t do that" by old cliques who stick to the experience of CDN. I've seen a few people left in very short terms, again and again, saying that they had trouble with those situations. It seems a typical innovation dilemma. If you have good experience in those areas, it wouldn't work here.
Even with CDN business, Akamai doesn’t allow customers to sign up online. You need to sign a contract that is really complicated and hard to understand and takes a lot of time. From outside, as many cloud companies allow customers to sing up online, it seems an easy thing. But Akamai has a lot of reasons why "we don't / can't do that".
There are a lot of people involved in one product development, but even the specifications of a product are very vague. Most of the specifications are "not defined". So, learning a product takes a lot of effort and time then even with that effort and time, you will still be not sure about the product.
Actually, there are many materials online, but most of them are sales/marketing materials even though they are supposed to be targeted at technical people.
In most cases, you need to work based on some kind of rumors. Product information is usually exchanged verbally or through chatting. In most cases, the source of information is someone's blog on the intranet.
No culture to write down information. Everyone is not sure who is responsible for a product even though there are many product managers.
Product managers (I don’t know why there are many product manager titles for one product) are in most cases not able to be responsible for their products probably because of a lot of red tapes.
