Exactly this. Its one thing to know how to build things with AWS, its another to actually build AWS. Same way being able to customize cars doesn't necessarily mean you have the skills to be an automotive engineer. From what I gather neither Amazon nor AWS really care what technologies you know. They only care that you exemplify their leadership principles, perform well on classical CS problems and raise their bar. Have you solved scalability and/or performance issues without AWS or other prepackaged solutions? Alternatively, look at Solutions Architect roles.
Exactly this. Its one thing to know how to build things with AWS, its another to actually build AWS. Same way being able to customize cars doesn't necessarily mean you have the skills to be an automotive engineer. From what I gather neither Amazon nor AWS really care what technologies you know. They only care that you exemplify their leadership principles, perform well on classical CS problems and raise their bar. Have you solved scalability and/or performance issues without AWS or other prepackaged solutions? Alternatively, look at Solutions Architect roles.
Actually, knowing AWS is very important and many AWS services are built on top of other AWS services.
What do you base this assertion on?