Feedback on my resume?

I like that you used the template from Alex and it looks like you’re using about the right amount of space for each component.

I have two main suggestions:

• Try using the Accomplished [X], Measured by [Y], By Doing [Z] format as much as possible. For instance, your first line of “Displays current time on the page and updates it every second” could be “Shipped clock feature with 0 bugs in production by using test driven development (or some time zone library, or some frontend tool)”. Most every line with this format will start with an action word like implemented, increased, devised, found, debugged, presented, created, achieved, improved etc.
• Do a couple passes looking for subtle consistency bugs. I noticed that some job titles are italicized or capitalized while others aren’t, some bullet points start with capitals some not, one bullet point has a period at the end while others don’t. It seems silly but recruiters would care about this if they feel it shows missed attention to detail.

Agreed with Mistplay. For your work experience (and projects as well, although it's a bit harder), I'd like to see more numbers showing the impact of what you did.

How well-regarded is Amity University? If it's well known, I'd put that at the top since you're a recent graduate.

amity university is not well regarded, so should I put it at the top?

You have some work experience, so I wouldn't put the "Education" section at the top. It can be last honestly.

I have some other notes as well:

• Be consistent with capitalization - For example, one of your titles is "software developer". In another place, it's "Software developer intern". I would just capitalize all words. It feels more formal and the consistency makes the resume feel more organized (i.e. so have "Software Developer"). Recruiters are more than happy to toss out resumes over small issues like these, and in their defense, a lack of attention to detail is generally a yellow to red flag for an engineer.
• Make impact clear - Your experience (not just your projects but your work blurbs as well) are only talking about what you built. That material's indeed important so hiring managers know you have exposure to certain tech stacks, but you need to make to clear what your work actually accomplished (i.e. what business value it added). Anybody can write code. Far fewer can write code that actually matters in the world. Here's a great discussion that covers how to do this in far more detail: "What high-impact achievements should a full-stack engineering intern target for a stronger resume?"
• Hyperlink the project deployments directly - Having a "LINK" is very ambiguous and it adds to the inconsistent spelling issues. I would remove the code links as well - Recruiters aren't technical so they don't read GitHubs. Just have 1 link. If the project's name is linked, it's intuitive that clicking on it will go to it.

Overall, the resume is off to a good start as the format is good (nice job reusing my resume as a template), but I think there's more polish work to do be and the content can certainly be optimized.

Best of luck!

amity university is not well regarded, so should I put it at the top?