A recruiter will touch base with an initial phone call to discuss yourself and the role. Most often, recruiters do not fully understand the role they are recruiting for and do a poor job of setting expectations for the initial interviews. They bombard you with a lengthy email and attachments on AWS, company values, etc., most of which is not relevant until you reach the loop interview stage, if you make it that far.

The company preaches "depth and breadth," but the reality is that no matter your response to a question, they are looking for you to give a life story background on a topic rather than a more focused and to-the-point response, which is often the case in the day-to-day world. My experience included interviewing with a more senior individual, but overall it was a bad experience. The company does not seem to have any interest in a person's background, certifications, or potential. They also state AWS experience is not required, yet they then begin to try and trip you up with AWS-related questions, even if your experience may be limited.

1st interview: Recruiter 2nd interview: Technical with a member of the team. Not much on leadership values; strictly technical.

If the interview process is any indication of how the company operates, then it explains why they have so many open roles. I wouldn't recommend it.

The following questions were included:

• Explain application attacks.
• Discuss OWASP Top 10 vulnerabilities.
• Cover privileged access management.
• Explain TLS and why it is better than SSL.
• Discuss asymmetric/symmetric encryption.
• Explain how to protect an EC2 instance or server in general.