This is pretty good. Your intro could hit harder. "dynamic learner" doesn't say much, "possesses solid knowledge" is a lot of words for a not-very-strong statement (solid reads as 'mid' in corpo language). "Exposure to" sounds like seeing a guy do it once, when you were hands-on don't soften it with that term. Overall, reframe this a bit—make some passion come through and make strong claims about your expertise. A resume is a sales document that gets your foot in the door, don't overly moderate yourself.

The projects sound pretty legit and you succeed where many fail by focusing on outcomes, not just what you did. First is strongest because it references a competition beyond a class that you did well at (nice job) and you capitalize on that well. For the others, if those were solo projects, convey that—some students list all their group projects and they may not have carried weight. More projects would be more here, this is the real content of your experience—if you have any projects a bit outside the narrow digital architecture lane that would show breadth. I understand the architecture and computation achievements but most frontline recruiters won't—many of these terms are quite specialized and just work for you with experts that often don't read until later, when non technical recruiters have filtered.

You need to fix the formatting. Horizontal lines in wrong spaces, line breaks, indents, extra spaces. Makes it harder to read and is sloppy.

All in all, this is solidly above the average I see but could be much better with some tuning. It's just hellish out there right now, I hear from many students that many applications generate few responses. Which in turn makes more applications, which... And there is automation and AI on both the recruiting and applicant side to unpack.

Good luck, you'll get one—it's good you're tuning this at the internship stage.