I agree with Jessica that the leet code section shouldn’t be there. It shouldn’t be “Programming Experience”, it should be work experience. If you don’t have programming work experience, then just have projects.
I may repeat some of what Jessica has said, but let me just run through it…
It is too wordy. And they’re often the wrong words. You don’t need 9 lines to say that you got an MA in an unrelated field. They don’t care. This should be two lines at most.
My philosophy of resumes is that it’s some HR person that has a stack of 300 resumes to read through - you have 5 seconds to convince them to consider you for the “keep” pile. In 5 seconds I should be able to tell what you are looking for, what you can do, and what your experience is. Everything else is a distraction and an excuse to put yours in the bin.
I agree with Jessica that the projects section should be more prominent. Do you have a third?
I might add things like FCC to the Education section. But the description should be 1 line, if that. Don’t say what you’re working on - you either know it or you don’t. List your certs if you like - those are good keywords.
Past work experience - you don’t have to explain to them what a barista does - it insults their intelligence and wastes their valuable attention. Any job that is not related to coding should be a one-liner.
What techs do you work with? I have to dig to find them. The HR person has a list that says, “React, Redux, SASS” and they are trying desperately to find those keywords. Make it easy for them. After you free up some space, I would add a “Skills” section and list your techs.
I would have your first section be “Objectives” - a 1-2 sentence saying what type of position you are looking for. Then I would have the Skills - that’s the next thing they’re going to want to know - if it’s even worth continuing to read. Next I would have Projects - the next thing they’re going to want to see.
After that, Education and Work. I know you’re proud of your MA - I was proud of mine. But my MA was also in an unrelated field so it was a one-liner. And they don’t need a link to your thesis. If you were applying for a job in communications or rhetorical studies or something to related to that, sure, they’d want it perhaps. They may ask you about it in the interview - that’s great, but here, it’s just filler.
I would also say that things like “Demo deployed on Netlify” should just be “Demo” - same with “Repo…” - just “Repo”. You can include “Netlify” in the expl;anation of what you used. But the text can be tightened up. If the title is “Troika Roleplaying Game System Reference Document”, then “Built reference documentation website fo a tabletop roleplaying game” is redundant - they could get all that from the title. The techs you used and the “retweeted” thing is what you need. They don’t care what “Troika”.
Do you have another project? I think three is a good number.
In general, don’t write filler. All things being equal, I’d rather have some whitespace than filler. At least the whitespace would allow their eyes to be drawn to what is important. You have a limited amount of space and a limited amount of attention of the person reading (or often skimming) it. Use them wisely.
Do you have a portfolio site? A linkedin page?
