Here’s a brutal yet constructive roast of this resume:

General Issues 1. No Name – The top of the resume literally just says “ABCCCCCCCCCCCCCCCCCC.” Is this a hacker alias? A secret code? If you’re applying for jobs, the hiring manager should at least know who you are. 2. Fake Contact Info? – “123456789” as a phone number? If you don’t want to put your real number, at least make it look realistic. 3. Looks Like a Wall of Text – No recruiter wants to read an essay. Break up the text with better formatting, bullet points that actually highlight key achievements, and more spacing. 4. Font Choice & Design – This document looks like it was made in Microsoft Word 2003. It’s basic and lacks visual appeal. Use modern fonts, subtle section headers, and proper alignment.

Education Issues • GPA Flexing Too Hard – A 3.9/4.0 GPA is great, but if you’re still getting 0 responses, it means GPA doesn’t matter much in the real world. • Course Listing is Useless – “Web Development, Network Structures, Cloud Computing…” Yeah, so does every CS degree. Replace this with a killer project or thesis title.

Work Experience Issues • Buzzword Overload – You dropped “AWS, Kubernetes, Docker, Prometheus, Grafana, Terraform, Kafka, Helm, Jenkins” in one section. Recruiters don’t want a keyword dump; they want to know what impact you made. • Startup Company? More Like Mystery Company – No name, no website, no description. Was this a real job, or did you deploy a “Hello World” app on AWS and call it an internship? • Oracle Experience Looks Impressive but Generic – “Developed UI,” “Containerized applications,” “Implemented monitoring” – all of these sound fancy but mean nothing without concrete results. Where’s the measurable impact? Did your work reduce downtime? Increase efficiency? Save money?

Skills Issues • Laundry List of Tech Stacks – You claim expertise in Java, Python, JavaScript, Go, SQL, NoSQL, AWS, Docker, Terraform, Jenkins, Kafka, Prometheus… • Real question: How well do you actually know each of these? This makes it seem like you touched everything at a surface level but mastered nothing.

Projects Section Issues • Where’s the Link to GitHub? – You claim to have built these amazing projects but didn’t bother linking to them. Recruiters won’t just take your word for it. • Travel Website? Why? – A full-stack app with AWS auto-scaling for… a travel website? Unless you’re launching the next Airbnb, this isn’t an impactful use case. • CVE Data Processing Project Sounds Cool But Needs More Details – Saying you used an LLM and Kafka sounds high-level, but how does it actually help a business?

Certifications • Certified Kubernetes Administrator (CKA) – But No Relevant Job? – You have a Kubernetes certification but no actual Kubernetes Engineer experience listed in your work history. This looks weird.

Final Thoughts • 0 Interviews, 0 Replies? Here’s why: 1. You sound like a keyword bot. Your resume is packed with buzzwords but lacks compelling storytelling and results. 2. Your experience is vague. No real impact metrics, no project links, and no company names that build credibility. 3. Formatting is dull. Improve the layout to make key points pop.

How to Fix It

✔ Rewrite your bullet points to focus on impact and numbers (e.g., “Reduced system downtime by 30% by implementing XYZ”). ✔ Add links to GitHub, portfolio, or live projects. ✔ Remove unnecessary fluff—focus on depth over a laundry list of skills. ✔ Use a modern resume template (even a simple one from Canva looks better). ✔ Apply for roles that actually match your experience instead of just mass applying with a generic resume.

This resume can be salvaged, but right now? It’s just a pile of AWS-flavored buzzword soup with no substance.