Recruiter Call.
Technical Call.
Recruiter call again before the 1st technical round to go over LPs and expectations.
Met him again the next day with one of the engineers at the same level over the Chime app. The engineer asked about 10 questions. Overall, it was okay, but he didn't seem satisfied with my answers to some follow-up questions.
There was very disturbing and distracting noise in his background (I'm not sure if an environment/technical setup prep email is sent to the interviewer), where I had to ask him to repeat questions several times (I also felt miscommunication due to a lack of language skills).
He had to change his location 2 times. I don't think the atmosphere was professional, as I lost my focus when trying to concentrate.
I didn't feel I was being listened to well, where he interrupted while I was directing my conversation to his point using the STAR methodology.
He asked questions for 54 minutes, and 6 minutes were left for my questions. This felt disrespectful to the candidate's time and priorities.
I asked him a question where he wasn't able to answer but just escaped by saying it's company confidential.
IR
Protocols
Incident handling
Zero-day
Phishing
The following metrics were computed from 1 interview experience for the Amazon Security Operations Engineer role in Seattle, Washington.
Amazon's interview process for their Security Operations Engineer roles in Seattle, Washington is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Amazon's Security Operations Engineer interview process in Seattle, Washington.