Excellent work environment, job security, benefits, salary, and work-life balance. A great place if you have a young family and need to spend a lot of time at home. Akamai also lets you transfer to any of their international offices once you've proven yourself.
Extremely limited opportunities for advancement. No room for great ideas, mavericks, or chronic innovators. Also, not a very good place for young people, which is very unfortunate. Really, only choose Akamai if you have a young family and don't need your job to provide you with friends and fun.
Actually, I like Akamai the way it is. It is safe, reliable, has a steady stock price, and makes me feel stable. I enjoy the graduate-school, research-lab-like work environment, and management treats the rank-and-file with respect. However, if you want to attract those young superstars, then make a dev office in downtown San Francisco. The San Francisco Akamai office is super fun but is only for business types. You would have new grads from Stanford beating down your door if you dangled a downtown San Francisco coding job in front of them.
I have never attended this kind of interview before. The requirements for the role they shared were different from the interviewer's questions. The requirements were for Python, REST API testing, Jenkins, and Git. The interviewer did not even ask
First contacted by a recruiter, she asked a few questions over the phone, such as TCP handshake and what HTTP code 301 means. Then there was a personal interview at the Prague office. It was with two guys, but conducted separately. Both were quite f
Phone screenings with recruiters. This was followed by phone interviews with hiring managers. The on-site interview included 2:1 or 1:1 rounds, averaging about 45 minutes a round. Well-paced, staying close to the proposed schedule and agenda. Each r
I have never attended this kind of interview before. The requirements for the role they shared were different from the interviewer's questions. The requirements were for Python, REST API testing, Jenkins, and Git. The interviewer did not even ask
First contacted by a recruiter, she asked a few questions over the phone, such as TCP handshake and what HTTP code 301 means. Then there was a personal interview at the Prague office. It was with two guys, but conducted separately. Both were quite f
Phone screenings with recruiters. This was followed by phone interviews with hiring managers. The on-site interview included 2:1 or 1:1 rounds, averaging about 45 minutes a round. Well-paced, staying close to the proposed schedule and agenda. Each r