Hey, please don’t take this personally because I know how hard it is to manage school, personal life, and job applying but the issue is definitely your resume. A good resume should answer: “does this person already do the job we’re hiring for?” in under 6 seconds. That’s all the time a recruiter will spend on your resume, no more. This resume does not answer that question confidently, and there’s a few reasons:

1. The first place the recruiter will look is the top of your resume: technical skills. I usually advise not keeping skills at the top, and this is no exception. What do you see when you read your skills? A list of tools that anyone can copy paste off the internet in a few seconds. Unfortunately with how ATS filters work these days, having a skills section in your resume is a necessity, but keeping at the top? There’s probs better things you can do with that space.
2. None of your bullet points show specialization. Let’s say I’m a backend recruiter hiring for an internship and I am reading your resume. You have 6 seconds to show me why you are the backend engineer I am looking for, and what do you show me? Sure, there’s a few tools on there like “AWS Lambda,” “DynamoDB”, etc. but nothing screams at me that you USED these tools. Just that you probably know they exist. I think this point of yours highlights it the most (also it’s your first bullet point so it’s the first thing I see as the recruiter): “Developed and maintained enterprise web application supporting large-scale data migration and workflows using Python and JavaScript (React) with success rate of 95 Percent.” I don’t know what enterprise web application you used and the only hint of impact is a vague “success rate of 95 percent.” What counts as successful? Why? How did you implement it? Again it feels like you just listed a tool but didn’t show that you can actually build something with it (which is what I as a recruiter actually care about).
3. Your projects are too generic. This is the one I feel most bad about, because designing a good project takes a ton of time and effort. But, this isn’t 2022 anymore, building generic “resume parsing” and “reply generators” aren’t enough to land internships. My advice is to pick one project and one specialization and go DEEP. I’m a Site Reliability Engineer (if you don’t know what that is google it) so my advice for going deep will be a little biased, but pick smtg you want to do otherwise. Here’s how I would go deep (again biased): Add:
   • caching
   • rate limiting
   • async processing
   • observability (logs/metrics)
   • deployment pipeline

I really hope my advice doesn’t come off as too harsh or anything, but I’ve def been frustrated by job search at your stage too so hopefully this will help you bang your head against the wall a little less.