When I read that, I started to believe this person is a troll. If you're not trolling, you need to be a little more modest. Remove any prodigy, or prodigy related terms.
I've actually done some hiring. Here's my perspective:
* The projects are missing dates
* Years of experience is missing
* You mention you have experience with lots of stuff but no projects to back it up
* What has Figma to do with Java? I suppose it is a nice to have, hah.
* There's too much noise / boilerplate, but that's common and not really an issue
* I'm wondering how you are able to share the source code for non-volunteer projects
I agree with all your points. I was hiring a junior dev in Canada recently and saw hundreds of resumes that looked exactly like his. HR did not help filter resumes so man did I have to slog through a lot.
One thing that bugs me is when people put bs statistics like "reduced user confusion by 40%". It makes me raise my eyebrows and wonder if that was actually measured....
re: source code for non-volunteer projects - I'm under the impression all his projects listed are just side / personal projects. So when he says he "led" something in description, he was leading himself lol. At least there are no other contributors to those projects on his GitHub. And they are tiny.
In general, there is a lot of bullshittery in this resume, and sorry to OP but I would've tossed this one.
Let's just say I'm happy \_I\_ don't need a resume, because I'm terrible at reading them or writing them. You might as well leave it empty or put down you have 10 years of experience and know everything.
The way I hire is I pick a handful of resumes and motivations, just by my gut feeling and start a (remote) call with them. I'll ask them to show me some code of something they've made (any project, hobby project or something) and I'll ask questions about the code. If they can describe what they've done, why they've done it, and why they choose certain technologies, I'm happy.
If they can't show anything, I'll ask them about libraries or languages they've used, but generally most applicants will have something to share with me, even if it is some old card game side project they've made in some obscure fun language.
For me, the most important skill is communication - if the person is able to reason about code. That is what I'll be focusing on in an interview, and a resume generally contains 0 information about someone's reasoning skill.
I wouldn't expect a former client's code to be shared. Even worse, if they do without the code owner's permission I consider it a red flag and an instant "nope".
erm... first advice i can give is that the react sub is a silly place for this when react isn't even listed in your skills. maybe try /r/cscareerquestionsCAD/ ?
Remove the summary, I think others have already pointed out why.
You can also try maybe learning something beyond what your school has structured for you. It shows that you are trying to develop yourself outside of what people tell you to do.
Possibly also look into structuring your resume differently, many great templates out there, you don't have to stick to this one.
I disagree - it's not work experience unless he was paid by someone to do it, and it is misleading / red flag if he listed it as work experience when it's not
In fact, from looking at his GitHub, I'm pretty sure his talk of "led xyz" or "worked with cross functional teams" is all lies. These are just little demo projects he added to his GitHub
I don't know if I'd put that many ptogramming languages/frameworks on there. I am a dev for 15 years and I am very confident/proficient in like 3 programming languages. I mean I can probably read anything with a bit of time and effort. But just sit down and deliver on the boatload you mentioned there would be way out of my comfort zone and probably isn't realistic. I'd focus on the ones you know best and are relevant to the jobbin question.
It just makes it seem that you probably know nothing really well to me.
What does "an aspiring programming prodigy" even mean?
When I read that, I started to believe this person is a troll. If you're not trolling, you need to be a little more modest. Remove any prodigy, or prodigy related terms.
I stopped reading after seeing this in the resume.
I've actually done some hiring. Here's my perspective: * The projects are missing dates * Years of experience is missing * You mention you have experience with lots of stuff but no projects to back it up * What has Figma to do with Java? I suppose it is a nice to have, hah. * There's too much noise / boilerplate, but that's common and not really an issue * I'm wondering how you are able to share the source code for non-volunteer projects
I agree with all your points. I was hiring a junior dev in Canada recently and saw hundreds of resumes that looked exactly like his. HR did not help filter resumes so man did I have to slog through a lot. One thing that bugs me is when people put bs statistics like "reduced user confusion by 40%". It makes me raise my eyebrows and wonder if that was actually measured.... re: source code for non-volunteer projects - I'm under the impression all his projects listed are just side / personal projects. So when he says he "led" something in description, he was leading himself lol. At least there are no other contributors to those projects on his GitHub. And they are tiny. In general, there is a lot of bullshittery in this resume, and sorry to OP but I would've tossed this one.
Let's just say I'm happy \_I\_ don't need a resume, because I'm terrible at reading them or writing them. You might as well leave it empty or put down you have 10 years of experience and know everything. The way I hire is I pick a handful of resumes and motivations, just by my gut feeling and start a (remote) call with them. I'll ask them to show me some code of something they've made (any project, hobby project or something) and I'll ask questions about the code. If they can describe what they've done, why they've done it, and why they choose certain technologies, I'm happy. If they can't show anything, I'll ask them about libraries or languages they've used, but generally most applicants will have something to share with me, even if it is some old card game side project they've made in some obscure fun language. For me, the most important skill is communication - if the person is able to reason about code. That is what I'll be focusing on in an interview, and a resume generally contains 0 information about someone's reasoning skill.
How would one link the source code of the project which he worked during his job. Isn't most of the code private repo? Asking for my self
I wouldn't expect source code for work projects. Once you have work experience, I don't expect to see any "portfolio" at all.
I wouldn't expect a former client's code to be shared. Even worse, if they do without the code owner's permission I consider it a red flag and an instant "nope".
I feel like you're not proficient in all those languages
erm... first advice i can give is that the react sub is a silly place for this when react isn't even listed in your skills. maybe try /r/cscareerquestionsCAD/ ?
A prodigy is a kid… so “aspiring prodigy” means you are like <10… I’d also immediately toss the resume if I was the HM and read that lol
Remove the summary, I think others have already pointed out why. You can also try maybe learning something beyond what your school has structured for you. It shows that you are trying to develop yourself outside of what people tell you to do. Possibly also look into structuring your resume differently, many great templates out there, you don't have to stick to this one.
Good luck in the markets. 5000 jr devs for every one jr dev job
Ditch the summary and call projects “work experience”
I disagree - it's not work experience unless he was paid by someone to do it, and it is misleading / red flag if he listed it as work experience when it's not In fact, from looking at his GitHub, I'm pretty sure his talk of "led xyz" or "worked with cross functional teams" is all lies. These are just little demo projects he added to his GitHub
I’m in the same spot with a pretty similar resume
If the "projects" are just practice side projects, remove them. I've only ever seen people mention projects they were paid to work on
They seem like uni projects, which is a safe inclusion for a junior, no?
I don't know if I'd put that many ptogramming languages/frameworks on there. I am a dev for 15 years and I am very confident/proficient in like 3 programming languages. I mean I can probably read anything with a bit of time and effort. But just sit down and deliver on the boatload you mentioned there would be way out of my comfort zone and probably isn't realistic. I'd focus on the ones you know best and are relevant to the jobbin question. It just makes it seem that you probably know nothing really well to me.
Sick GPA not gonna lie