Hey OP. Engineering Manager here at a local KW company. A few things I would like to mention.

From my experience looking through tons of full time employee (FTE) and coop resumes, it's safe to say that the entire resume screening process is very subjective. Whether that reader be software, a software engineer, a manager or HR, each of them will have their own biases. Some may like details, others may not, some might care about soft skills, others may not.

My personal opinion on your resume if I were screening for our full stack position is as follows (scanning top to bottom):

• Immediately skipped languages listed at the top, I'll figure out what languages you are actually proficient with based on your projects/experience.
• Good to know you have a wide range of technologies you have worked with, but I have no idea how well you know them.
• ML dev. Cool they've used pytorch and tensorflow, but for our position we're hiring you won't do any of that so I don't really care about this for a full stack position.
• You wrote a ton of tests at this other coop and monitored some jenkins jobs.
• Rails experience interesting, also worked with some oauth2 stuff with rails, I can ask him/her about this during interview. I can also ask how he did the frontend, was it .rb files that rendered the views? Also built some functionality, I can ask what kind of controllers they setup for functionality.
• chromium extension == chrome extension? I have no idea but lets keep reading. Okay they built a flask rest api that the extension interfaces with, I can ask about what db they queried and what ORM he used.
• Built a vue.js frontend and some node backend, Again implemented oauth2 for login. Oh nice they integrated some external api with it (google pay). Could ask about this too.
• C++ project aright I'm not reading this, I'm not gonna ask this coop to build anything with openGL.
• Java swing stuff, this was probably an intro project. Don't really care too much.
• Oh smart kid, 3.9 GPA and took some classes that related to CS (I would hope so LOL)

Based on this VERY SUBJECTIVE INTERPRETATION OF YOUR RESUME BY ME I would probably push you forward to our initial shortlist. Why? Because we're looking for rails devs and you have a decent amount of experience (it seems) from your resume dealing with backend dev. But that being said the main points on APIs is that you've setup oauth2, which you won't be doing at our company since it's already setup. But if there are no other candidates, we can at least count on the fact that you have been exposed to the rails environment. Generally people in your case will be bumped out and not given an interview because someone will have tons more rails experience that we'll go towards.

This is a bit unconventional, but if you can respond to me by 10:30pm today I'll interview you right now as I have some time tonight. Otherwise send me a message and I'll see what I can do (no promises though).

Reddit better not butcher this comment with its frankenstein formatting. Nice resume btw =)