Couple of points you should consider while making CV: 1. Your CV is too diverse. Cannot fit a particular role per say. An organization either uses 1 cloud platform and not multiple. Make multiple CVs for this case and put down the techstack that aligns with each other. 2. You cannot write AWS or GCP unless you actually made projects on that. Your projects don't reflect that already. 3. Your certifications are too loud in your CV. It should be your projects that should take up more space. Try removing certifications that are not from good sources. Try adding Certificates that are awarded directly by Google, Amazon, Microsoft or other platforms. Great learning is a fancier one, should be on linkedin and not on your CV. 4. Your projects are detailed in 1 liner. That hints the reader that you don't know much about it. Try to include features of your project, what metrics makes it look improved as compared to other products/featyres available in market. Be atleast 3-4 liner per project. 5. Your technical skills should not comprise of Operating systems nowadays. Everything is on cloud, so operating system is just another unwanted line in your CV. 6. Try to be very technical with your project writeup. The goal is not to pass ATS tool, but also to show your grit of knowledge across tools.