I interviewed at Amazon Web Services (Herndon, VA)
Interview
A screening call with the recruiter followed by a 1 hour video call that was technical and behavioral. The final round was 4 one hour interviews in a 5 hour period. A mix of technical and behavioral. We disagreed on salary and never made it past this stage.
Process is ridiculously long since most interviewers repeat questions from other interviews. I was also told a different, much higher salary range than what was provided by the managing recruiter at the end. All after wasting all this time.
Interview questions [1]
Question 1
Describe DNS. Trouble shoot a web server issue. Explain OSI model. Typical stuff.
I interviewed at Amazon Web Services (Seattle, WA)
Interview
initial phone screening + Loop interview with 6 hours of continuous interviews. Questions were asked from all different domains of cyber security. Specially focused on the domain you are interviewing for.
Interview questions [1]
Question 1
Incident response lifecycle describe the steps and framework
I applied online. The process took 3 weeks. I interviewed at Amazon Web Services (Seattle, WA) in Jul 2025
Interview
Application: Applied online.
Timeline: About two weeks after applying, a recruiter reached out with some initial screening questions.
Process:
The recruiter responded to my answers saying the hiring manager wanted to interview me. He sent over a list of items to help me prepare for the upcoming call and scheduled a prep call with me to review them before I met with the hiring manager.
However, he didn't show up for our prep call. He followed up later saying he’d had computer issues with Amazon's in-house Chime service and said he still wanted to prep with me before the manager interview. Unfortunately, he rescheduled that prep call after my actual interview with the hiring manager.
As a result, I went into the hour-long hiring manager call knowing nothing about the role or team beyond the generic job description. The conversation consisted of leadership questions, situational problem-solving, and multiple technical questions that I hadn’t been briefed on.
Overall Impression:
While the recruiter was polite and communicative via email, the scheduling mishap left me unprepared. I would have appreciated a more reliable or better-coordinated process to understand the team, role expectations, and technical focus areas ahead of the interview.
Interview questions [1]
Question 1
Describe the differences between a root CA and an intermediate CA, When you build and run a Python script in Linux, what actually happens?, and It’s a Friday evening and you’re about to leave work. One of your main services is hit with a zero-day bug. How do you handle it? What do you do? How do you see how many systems are affected?
