Akamai reviews

Most of people only keep to themselves. You never know when and who will stab you from behind even just when you think everything is going alright. A lot of managers are extremely short-sighted. They bend forward and take every requirement from Product team and turn them into a CR (change request, just like a bug) without even considering the overall impact to the system and pushing back when necessary. I guess that the manager's performance is evaluated by the no. of CRs they close. That's why they want to open/close as many as possible. There is hardly any chance for advancement. Unless you're one of the boss's pets, you're pretty much stuck in the same position for many years until either your boss moves up or you can't take it and get moving yourself. Advice for the potential employees: work hard to get the level as high as possible since it'll be very hard to move up once you join.

- Technical debt - Nobody with the ability to hire staff or allocate budget to addressing technical debt is really doing that - Horrifying lack of reasonable quality assurance (as in, key systems do not have unit tests) - QA staff as a whole have no idea what they are doing and are stuck in the year 2000 at the latest. Most testing is done manually and by the seat of one's pants, console-cowboy style. - Service incidents caused by aforementioned techincal debt and lack of quality assurance have prompted the company, not to address technical debt of prioritize improving the pre-release QA process, but to instead create a tight chokehold on teams' ability to release new software at all (including bug fixes for issues which couldn't be caught in those whacky pre-prod half-baked testing setups which are in danger of causing new service incidents!) - People who complain about this stuff are not challenged on the validity of their frustrations, but also nothing happens to materially improve the situation