I applied online. The process took 5 days. I interviewed at Amazon in Jul 2016
Interview
The first stage is an online assessment that asks you a few open ended and some close ended based on the role that you applied for e.g I applied for the networking role with windows so the questions were geared more towards that aspect. After this, the next stage is a 1 hour technical phone interview with a cloud support engineer. I'm currently at this stage so can't give any more feedback.
Interview questions [1]
Question 1
1) When you type amazon.com in your browser what happens?
2) What are the types of routing protocols that we have?
3) What happens when you connect your PC to the network?
4) What is DNS loadbalancing and how does it work?
I applied online. The process took 2 weeks. I interviewed at Amazon (Herndon, VA) in Apr 2016
Interview
Amazon flew me to Virginia to meet their AWS support team, all expenses paid. The interview process is about 3 or 4 hours long and I met with 4 people. One meeting was via video chat. 3 of the people I met with were people I would be working with. The questions seemed fairly simplistic in nature, less than what I would've expected for the position. It seemed almost as if they were more concerned about the type of person and personality and how that fits with company culture rather than skill level. There are a lot of "tell us about when..." questions.
Interview questions [1]
Question 1
Tell me about a time when a client was not happy, what happened, and how did you handle that?
I applied through a staffing agency. The process took 2 months. I interviewed at Amazon (Sydney) in Jul 2016
Interview
The interview process is long and drawn out over two months - easily the most unpleasant interview experience I have ever had in my 10+ year IT career . There are preparation sessions for initial interviews, initial interviews, preparations for tech challenges, then taking the tech challenges, preparation for more tech interviews, then more technical interviews, preparation sessions for the final interviews, then finally a long five hour block of interviews. It's very time consuming, especially if you have a job or are applying to other companies. If you get to the final five hour interview and then don't get an offer for all your trouble, you will feel that you've had your time wasted. This is especially true if you pass all their technical challenges only to be told "you're not a fit for the role".
OK, fair enough. So why didn't they tell me this first before they got me to waste my time on multiple technical challenges, long interviews, and trivial technical questions? I had other interviews with other companies to manage too!
Many personality questions centre around their touted Leadership Principles. You should write a story about some experience where you displayed these traits. However they will seem to expect that your story to go a certain way that they are only prepared for. Most interviewers are taking notes and not responding which makes the interviews awkward, one-sided, and non-personal. It feels like more of an interrogation or impromptu test where you need to give them the exact thing they are looking for so they can check off the boxed on their pre-planned forms. If you don't answer the question the exact way they want, they get frustrated.
Their jabber server also cut out several times during the interview, and were quick to blame my setup despite my having tested it as working the day before with one of their colleagues. I'm not sure if handling false accusations calmly and rationally is part of the interview or not, but I was uncomfortably put on the spot.
Amazon seems to want to bluff you with the impression that they are exclusive to get into by making the interviews a run of the gauntlet, but given the length and number of tests all aimed at trying to disqualify you (as opposed to trying to find ways to hire you), I simply felt abused. What sane and in-demand engineer would be on the market long enough to wait around and tolerate this kind of treatment? How could they keep talent? I posit that their interview process doesn't yield leaders, but rather spineless "yes men" who think that being dragged around like this before being hired makes them "lucky" to be part of the company.
After the final interviews, and before I knew the result, I discovered the many serious complaints about Amazon work culture. Given my experience with the interviews, I was inclined to believe the horror stories. I was actually quite relieved that they didn't offer me a job.
I was told that the company doesn't like complainers. I am suspicious as to why this is because if done respectfully it's usually effective in getting positive change... that would shows leadership traits, right?
I probably should have displayed the one leadership principle that trumps all of theirs:- not to put up with entities who waste your time.
Interview questions [1]
Question 1
If you are taking the technical test or any of the online challenges, then you should prepare by reading this site as well as practicing and planning the online challenges in order to complete them in a fast time. The interviewers all have a standard batch of questions that they ask all applicants. Chances are good you will get the same "cookie-cutter" questions as the ones listed here and you will be able to ace the technical interviews.
Most of the technical questions are purely academic and seemingly trivial in nature. Others involve things you would only see in problem edge-cases. Other questions are way too broad to express in detail in a limited time interview without any planning or reference material. If you're a decent system engineer who actually reads manuals, plans your configurations, and sets things up properly the first time so that you don't revisit low level problems constantly - you probably won't be able to answer them because you won't have dealt with the same problems on a constant basis in order to remember them. I assume the role must require you to rush to fix things in a short space of time that customers manage to repeatedly break horribly.
I had mostly network questions for some reason even though I told them it wasn't my strong suit, despite wanting to improve in this field.
- What is HTTP error 400 (Bad request)
- Explain TCP congestion control and how it works (average round trip timer retries)
- Explain everything in detail that happens when you type www.amazon.com into your browser (you will have to explain everything that happens in all the OSI layers, DHCP, DNS, routing protocols, HTTP ports and commands, TCP, load balancing, reverse proxies, CSS, databases, etc)
- An FTP download starts slow and then speeds up towards the end. Why is that?
- If you were to set up amazon.com from scratch, what would you do? (essentially describe everything involved in filling a datacentre with networking, hardware, software, storage, and getting it seen on the internet)
- What does a router do if the MTU is too small for the packet (packet fragmentation, but you can talk about MSS and PMTUD)
- What kind of DNS record that tells the name server to find it's own domain by looking at it's own records to avoid a recursive loop? (A DNS glue record)
- Describe the Phases of IPSEC (IKE phase 1 - establish security association policies and Diffie helman key exchange, IKE phase 2 - establish the security association and regularly retest it)
- How can a filesystem say it has free space but you are unable to write anything into it (out of inodes)
- What happens when a router receives a packet? (describe routing, forwarding, and encapsulation processes)
- What are the differences between OSPF and BGP? (OSPF is link-state used internally in sites, BGP is path vector - and connects sites via AS numbers to the public internet)