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.
There's packet loss between an EC2 and an RDS instance, how would you debug it?
Explain when you would not use autovacuum on postgres? What makes you the happiest in your work? How does working remotely with limited face to face contact make you feel?
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 do you prioritize your workload?
Behavioural questions like "Tell me about a time..." and some technical questions relating to my core cloud competency/domain.
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?
How can a large enterprise apply the principle of least privilege and other best practice in their cloud environments?
What happens when user types in an address and accesses a URL on a browser.
Viewing 1621 - 1630 interview questions