lowkey i just stumbled onto this breakdown of twelve aws networking questions that rly hits home. the author mentions asking abt ec2 connectivity issues in roughly forty interviews, but only seeing a few people nail it. most candidates fail bc they focus on
defining terms instead of actually troubleshooting.
>they answer the question they wish had been askedit is the difference between knowing what a nat gateway is and being able to
diagnose a broken route.
it turns out technical definitions are useless if you lack diagnostic logic . has anyone else noticed interviewers moving away from rote memorization toward these weirdly specific scenario tests?
link:
https://dev.to/maheshbandaru_ba8cc2/twelve-aws-networking-questions-and-what-the-interviewer-is-actually-listening-for-3506