Developer Resume Review

• I'd try to clarify the nature of "Undergraduate Research" (Is it a thesis? A course? Did you go out of your way to approach a professor for the opportunity?) Basically, it's unclear to me if this is work experience (e.g. research assistantship) or coursework (something you simply signed up for).
• I'd try and narrow down "Relevant Experience" -- the category feels too broad/unfocused, and requires the reader to spend some energy trying to parse what the items are. (Is this a project? Is this a club? Was this for a Hackathon-type event?) Not so good when your reader is only spending a bit of time per resume.
• The items within Relevant Experience aren't formatted consistently. Sometimes the descriptions are in brackets in the title, sometimes they're in the subtitle... it makes it harder to quickly grok what something is.
• Ditto for date consistency.
• You're devoting a lot of space to simply listing the tools you've used. But... frankly, that isn't very useful information. As an undergrad, everyone gets exposed to a little bit of everything! An unfocused smattering of unrelated tech doesn't give me any clues as to whether you're worth hiring for <insert specific position>. It doesn't tell me anything about what sort of work you find interesting, it doesn't tell me anything about your personality or strengths or soft skills, and it doesn't tell me what sort of impact you've made in groups besides just showing up. (That's not to say don't list what you've worked with, but you can keep it to one bullet point per project. I use "Utilized: Django, React, DigitalOcean, PostgresSQL" per project and spend the rest of the time trying to signal more important qualities.)
• Similarly, I don't think you need to group tools by type (Languages/frameworks/etc). You can just have a one-liner for "Skills" to save space. That big block doesn't really tell me enough to be worth all that space... it's a bit redundant with the project sections.
• GPA?
• "University project, 1st in over 50 submissions" -- This is a great start, but I don't have a great sense of the importance here. How were you graded? What was your role in the team? I'm left wanting more information about why this was an accomplishment for you specifically.
• Maybe try and give your resume more focus depending on the role. The CV stuff is from a very different world than the fullstack stuff. Try to communicate why you're shooting for a specific role. What path are you trying to go down? The resume kind of gives off an "I tried a bunch of stuff and now I'm not really sure where to go from here" vibe, when I'd be looking for a "I tried a bunch of stuff, really liked <insert blank> for <insert reason>, and now I'm really curious and motivated towards a career in <blank>" vibe.

tl;dr The resume basically tells me "I worked with this thing" over and over. That could be anyone! I want to know so much more about you and your personality and your experiences and your transferable skills! You can condense a lot and use the remaining space to tell a story that makes you stand out.

I don't see anything strictly wrong, but you could consider including a list of courses you've taken, since coursework is relevant experience and would give a bit more about your background than you currently appear to. Otherwise maybe fix the "Sophomore Year" date entry and rework the various bolded project names/descriptions into a more cohesive set of titles.

Edit: Also be aware that it's a tough market right now, especially for internships.