Cloud engineers play an integral role in the development and implementation of software in technology companies. Typically, in interviews for cloud engineer positions, employers are interested in how you follow current trends in the field and how you would address problems that come up in these paradigms. You should be vocal about your skills, providing as much detail as possible about how your solutions-oriented thinking proved valuable in earlier work situations. Lastly, you'll want to speak to the field-at-large in relation to other fields within technology companies, demonstrating that you know the ins and outs of cloud computing and why they're so contemporarily relevant.
Most questions were related to previous experience in this field of work as well as product related knowledge which was applicable to my previous and now current role. Besides technical questions, there were also behavioural questions, to make sure I had an understanding of the company's culture and would fit in.
What are your strong sides in AWS?
The interview questions covered a broad range of topics, including my experience in AWS and Kubernetes architectures, problem-solving abilities, and scenarios related to application modernization. They assessed my technical proficiency, understanding of industry best practices, and how well I could articulate complex concepts. The questions were thought-provoking and designed to evaluate both my technical skills and my ability to contribute effectively to the team.
AWS service specifics, like for EC2, S3, Cloudfront.
There were various interviews but the technical one was not that difficult. The core of the questions was infrastructure, networking components, and at time implementation details for typical clients use cases.
How would you secure a public facing API
There's packet loss between an EC2 and an RDS instance, how would you debug it?
How can a large enterprise apply the principle of least privilege and other best practice in their cloud environments?
Lots of questions, but here's a few: Describe your typical day as a consultant. How do you handle context shifting on the job? In Linux everything is considered what? Describe in detail end-to-end what happens when you load a web page? What steps would you take to troubleshoot an unresponsive instance?
Give some examples of non-functional requirements. What is the one thing that you would carry along with you and one that you not want to carry?
Viewing 7581 - 7590 interview questions