Just give you one suggestion whatever you have written in your resume be ready to prove it eg if written worked on lamda/glue/sql scripts: be ready to write some code/queries if written optimized code : be ready with what was the optimization, how did you measure the success, any issues you faced. if written build end to end pipeline: be ready with questions like issues faced, duplicate issues, data quality, data size, errors face and solution provided(with code), how to handle idempotency, how was data validation performed, monitoring and alerting, how to handle scd data with code, bookmarking(for aws cloud and glue service) , decide no of workers and how to calculate no of workers, transformation performed (with code), how were the reports validated?, no of team members, your role in it. Basically whatever you explain be ready with the code or atleast the pseudo code and this can be achieved easily using chatgpt. More on reddit.com

Write most of your lambda code as a set of code that doesn't know anything about the mechanics of Lambda. Then test these in the normal way for your programming language. Then write the lightweight Lambda part that calls the aforementioned code. This then means all that is left to test are AWS permissions, the translation from Lambda events to your code, and the triggers. More on reddit.com

How good are you at Github actions? 10/10 since i let Claude Code generate the yaml. More on reddit.com

This is a classic "Systems Design" interview question. There are lots of resources available to prepare for it. This question isn't testing your knowledge of AWS, it's testing your ability to plan and design a large software system around specific constraints. More on reddit.com