So, we have this issue about what it is you’re communicating. I’m not a hiring manager, but if you read the critiques of prior people posting their resume and/or portfolio, I can sum the similarities briefly:
Drop the fancy design, go for plain-text machine-readable. You’re not a graphic designer, so there is no need.
As said before, it depends on whether you’re a back-end, front-end, or full-stack guy. You said you were a back-end guy in a previous post, but in your resume you say you specialize in:
(Except Git/Github, which is neither front nor back, these are all front-end technologies.)
It looks like you opted for the template, which would be fine for a back end guy, but:
Literally no backend technologies or certificates listed. And the source code says
<!--Template is licensed under CC BY 3.0. -->. Which would lead me to ask: if all you can do is front-end, why didn’t you do this yourself? Given the difference in polish between the portfolio and the projects within, I’d be surprised if someone didn’t look at the source code like I did.
My advice would be: If you have back-end projects, present them, and change the thrust of your sales pitch of you, the commodity. If you don’t, use the concepts in the portfolio, but make one yourself. You can do it. You have the technologies
I noticed spelling errors as I finished scrolling. Search and destroy:
Built uding ReactJS
Increased department productivity by over 50% greatly reducing overtime cost
needs a comma after “50%”