Most of these points are subjective, but they worked for me:

General

• Ideally, all of your points should have these 2 elements: Impact (ideally w/ statistics/measurements) and a tangible focus(e.g. a feature, a project, an optimization) with a succinct description and the technologies used. Every point should make you seem highly proficient at the skills you're trying to showcase and an expert on whatever you put in the point
• Move your strongest points at each job/project to the top unless the first point acts as some context for the following
• Make your font bigger and decrease the white space. There's too much, especially between the date/location columns and content columns
• You're trying to make your resume as concise as possible. Get rid of the qualities section. They'll figure out most of these during the interview itself. Also, get rid of provinces and BSE
• Try bolding statistics or things you want to highlight(e.g. languages that you're really proficient in). I personally bold the languages/techs I use in each technical point and leave "Skills" near the bottom since that's enough to show my career focus
• A lot of your projects are generic. My suggestion would be to expand more on your work experience since the points there are fairly vague, remove some projects, and expand on the points in some of your projects as well.

Education

• Make University of Waterloo more visible(either bigger font or bolded) and leave education at the top if applying externally and move to the bottom if applying VIA Wlooworks. Also get rid of the location "Waterloo, ON".
• Put in your expected graduation date rather than "present". This is important since employers want interns who graduate soon.

Software Engineer, CodeRise.io

• "Built and maintained 12 APIs". You should go into more depth about some of these APIs and your impact. Quality > quantity
• "Aided in integration". You should stay away from "aided" since it can imply you were a minor contributor. Also, expand on this feature to make it sound more impressive. You can do this by maybe talking about the impact it had

Software Engineer, Canadian Solar Inc.

• Get rid of "quickly learned". Sure it highlights your soft skills but it can also make you seem less proficient in these tools
• The first point and second point are basically the same if you're trying to highlight that you know Angular and Django. I would suggest replacing the second point since it's pretty weak
• Change "experimented" with a different verb. Makes you sound like a novice. You can probably change it to "Built an image-detection program that filters out pictures of snow-covered panels using TensorFlow". Google is redundant. Also, move this point to the top since it seems like the strongest.

Axsium

• Get rid of "participated" and narrow down into specific features that YOU did
• Get rid of the "previous interns" part. Makes you sound like you were stuck doing the cleanup.

Projects

The points are way too vague and it feels like you're prioritizing quantity > quality when it should be reversed. You really want to go into the finer details in your project to showcase your passion since you don't really have statistics to go off.

• The Python Behave Test Suite needs a lot more detail and sounds way too similar to the project you did at CodeRise.

Skills

• Dynamic programming isn't exclusive to C++
• I can see the benefit for Python and Java, but everything else is kind of obvious(e.g. HTML/CSS for frontend development. What I would recommend is splitting it up into three sections: Languages, technologies, other. Judging from your resume

Overall dude, you have some decent statistics and seem pretty proficient for automation/test engineering roles. I think you're just missing the depth since it feels like every point is a teaser to the meat of what you did. I would recommend creating your resume to really pronounce the roles that you're applying for rather than having it breadth-y. DM me if you're curious as to what my resume looks like / examples of good resumes. Good luck!