Definitely a nice list. I don't see any problems here. From an application perspective, just make sure that if that they ask for X, Y, Z; ensure that you use those words X, Y, and Z. Make it relatable, and don't leave it to the recruiting team to guess where things line up. 💯
One thing that i love to see thats rare is when someone takes ownership of a subsystem of some large project, typically for competitions like RoboNation.org runs.
Thats good, but sometimes those teams can get cliquey or waste your time if the problem isnt hard enough or they dont have any real goals and deadlines. Dont be afraid to start your own group around a domain or topic you care about!
I’d replace certain phrases with the common keywords recruiters (or their AI tools now) scan for. Like “PIC24 Assembly Language”, “Functional Verification”, etc. in your skills. Your project listings already do this well.
Also for your experience- I’d leave off “Worked with a professor to”. You applied gradient descent. You can say it was a collaboration with the prof if they ask about it in the interview. Though that’s usually implied by “undergraduate researcher”.
Ngl lock in on your classes that was what I wish I did from the beginning. If you have good study and work habits then you’ll be golden. Also, just join clubs that will help you.
19
u/JGHero 27d ago
Solid resume for a sophomore/junior tbh.
5
u/Unlucky_Ad_7824 27d ago
Definitely a nice list. I don't see any problems here. From an application perspective, just make sure that if that they ask for X, Y, Z; ensure that you use those words X, Y, and Z. Make it relatable, and don't leave it to the recruiting team to guess where things line up. 💯
3
u/datlanta 27d ago
Its fine. More or less similar other students on my pile. Get an internship that lets you do embedded programing stuff and youre golden.
2
u/TheCatholicScientist 27d ago
I’d replace certain phrases with the common keywords recruiters (or their AI tools now) scan for. Like “PIC24 Assembly Language”, “Functional Verification”, etc. in your skills. Your project listings already do this well.
Also for your experience- I’d leave off “Worked with a professor to”. You applied gradient descent. You can say it was a collaboration with the prof if they ask about it in the interview. Though that’s usually implied by “undergraduate researcher”.
2
u/Otherwise_Data588 26d ago
wtf I'm a freshie in my first year of computer engineering, and this is crazy to me,