Cloud Support Associate applicants have rated the interview process at Amazon with 3.2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 73% positive. To compare, the company-average is 57.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Cloud Support Associate roles take an average of 32 days to get hired, when considering 178 user submitted interviews for this role. To compare, the hiring process at Amazon overall takes an average of 28 days.
Common stages of the interview process at Amazon as a Cloud Support Associate according to 178 Glassdoor interviews include:
Phone interview: 27%
One on one interview: 18%
Presentation: 17%
Skills test: 10%
IQ intelligence test: 9%
Group panel interview: 6%
Personality test: 5%
Drug test: 4%
Other: 2%
Background check: 2%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at Amazon (Dallas, TX) in Jan 2016
Interview
I applied for multiple positions and was contacted by many recruiters simultaneously. One of the recruiters moved very fast with the hiring process after I was asked If I already got an offer somewhere else and how much time I had to accept the job offer. I already got an offer with another company but wanted something better.
A phone interview was set up the following week. The position requires knowledge of Networking, Windows/Linux OS, Database and Programming. My strength is in Networking, so I thought it would be a cakewalk and dedicated most of my time brushing up other areas.
The recruiter sent me an email about an hour to the interview apologizing for a time conflict and that the interview would be postponed. I accepted the apology and was waiting for a reschedule appointment. To my surprise, I got a call from the interviewer at the scheduled time and I was just disorganized (not in a comfortable environment at that time). I told him about the email I got and He was confused about the update. He said He accepted to interview with me that day and it was a good time for him. He said He would be testing my networking skill but sadly, because of my state of disorderliness, I was unable to give concise answers to very simple basic networking questions and some scenario to analyze (This would have been better answered on a whiteboard). It was obvious to him I knew the answers but had lots of incoherence in my explanation.
He said the recruiter would contact me a week after about the next stages (interview on Windows/Linux, Database, and Programming) and they would decide on where I best fit. The recruiter never contacted me even after I sent follow-up email but I got contacted by another recruiter asking me to take the AWS Windows/Linux challenge online. I did great and that was pretty easy for me as I was preparing for MCSA at that time. This new recruiter later contacted me that He was sorry there was a problem/conflict on my candidacy so they would not be moving forward but I should apply later after 6 months.
Unpleasant experience with the hiring process with lots of conflicts but I learned my lessons. Perhaps it was a bad idea to apply to tons of different positions in different locations, hoping at least one would work.
Interview questions [2]
Question 1
stage 1:
Basic Networking questions:
What is the difference between Bandwidth, Delay and Latency?
What is MTU, Window Size, Segment (MSS)?
Describe 3-way handshake.
A scenario question about prefix-match and route summarization
A scenario question about Stateful/Stateless firewall.
A scenario question about packet flow in NAT
How DNS work
How DHCP work
What is BGP and describe the states - Idle, Connect, Active, Opensent, Openconfirm, Established.
Tell me a time you went out of your way to do something amazing for a client.
Do you have any question for me?
Stage2 - AWS Windows Challenge online:
what is Active Directory and why would anyone use it?
importance of time in a Windows domain
what is sysprep, sysvol, BSoD, DHCP, DNS, DFSR, WINS, Global Catalog,
Describe built-in tools to troubleshoot network issues.
Some best security practices and a scenario on a company under DoS attack and you choose best answers or suggest any additional answer.
Finally, A bonus project to build a system that is robust and fault-tolerance for a start-up ecommerce website. .
There was 3 rounds lost interview in depth knowledge is good each concept in depth in os networking subnets basic programming is enough to clear interview manager round they ask direct questions if u tell lie they can caught u
Interview questions [1]
Question 1
Program questions like string array
Basic on cloud
Os
Networking
The recruiters were helpful and provided insights on what needs to prepared, including a training workshop before interview.The process was easy and consisted of two interviews.First was HR and second was the technical round.The interviewers were helpful during the interview if you get stuck.
Interview questions [1]
Question 1
About computer science related experience and projects
2 major rounds which there are sub rounds
Based on Computer Networking, operating system and linux
First round is based on MCQs and some behavioural questions after that the major round two is there in which 3 sub rounds is there
1st sub round is based on operating system and linux
2nd sub round is based on Computer Networking
And 3rd sub round is hr and managerial round which is the last round of interview process
Interview questions [1]
Question 1
Basically you should now all the basics of your computer and operating system in your computer or laptop