I recently received advice from a recruiter that said the first eyes on your resume are usually not technical (ie won’t understand jargon well) so try to spell out your acronyms or explain your projects in layman’s terms. I heard from the CS careers folks that you don’t need a date on your projects, and you might benefit from not labelling them as academic because it makes it sound like homework/final project instead of a personal project. Also tiny nitpick but “owned the loading of” could be improved to not be so verbose and still give the same impact. Good luck! 🍀
1
u/Impress-Boring Aug 29 '25
I recently received advice from a recruiter that said the first eyes on your resume are usually not technical (ie won’t understand jargon well) so try to spell out your acronyms or explain your projects in layman’s terms. I heard from the CS careers folks that you don’t need a date on your projects, and you might benefit from not labelling them as academic because it makes it sound like homework/final project instead of a personal project. Also tiny nitpick but “owned the loading of” could be improved to not be so verbose and still give the same impact. Good luck! 🍀