Oh hey, someone else who went to Plymouth uni. Anyway, I'm getting sidetracked.
Don't take this the wrong way, but my first impression was that it's ugly/hard to read. There's just so much blank space around the edges and you've used what looks like a tiny font. I know it's subjective, but if the person going through it has the same reaction as me, you're off to a bad start.
The summary, have you recently graduated or do you have 4 years of experience? To me, recently would be in the past 6-12 months damn I can't read apparently. Definitely highlight that because it is rare and sets you apart from the crowd. I would remove the links as they do add visual noise and add a section for projects and other bits and pieces. You also have phrases like "I’m highly motivated to learn" which don't really add anything. The summary is often what some people will limit themselves to so it needs to have a few hooks to draw them in. Here's a suggestion of what I'd write as a summary for you.
I’m a full-stack software engineer with nearly four years’ experience in the aerospace industry and a 2:1 from Plymouth University (BSc Computing) that I completed alongside. I’m keen to expand upon my existing skills and am currently looking for a Java or web development position.
In my spare time I enjoy learning new technologies and frameworks, the most recent of which being React. I have completed both personal and collaborative projects, one example being a decoupled command delegation & undo/redo library.
Skills, do you need the distinction between proficient and familiar? And with familiar skills, is it enough to be on your CV and/or applicable in a job? I also notice that they're all technical skills, do add some soft skills in there. Coupled with the "I code in my own time too" from the summary, it does paint you as one dimensional.
Experience, pretty much the format I've used. Explanation of your role and highlighting things you've done there. I would add the benefit to each bullet point. Taking "Proposed and developed a new source configuration management strategy (using Git) for new and existing projects in my area", my counter would be "so what?". I have no idea what "source configuration management strategy" is in practice and how it helps a company. Does it reduce costs/prevent error/allow more flexibility?
I wouldn't mind showing you my CV and maybe it could help, but I don't want to post it publicly on here. Send me a message if you'd like to see it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Oh hey, someone else who went to Plymouth uni. Anyway, I'm getting sidetracked.
Don't take this the wrong way, but my first impression was that it's ugly/hard to read. There's just so much blank space around the edges and you've used what looks like a tiny font. I know it's subjective, but if the person going through it has the same reaction as me, you're off to a bad start.
The summary,
have you recently graduated or do you have 4 years of experience? To me, recently would be in the past 6-12 monthsdamn I can't read apparently. Definitely highlight that because it is rare and sets you apart from the crowd. I would remove the links as they do add visual noise and add a section for projects and other bits and pieces. You also have phrases like "I’m highly motivated to learn" which don't really add anything. The summary is often what some people will limit themselves to so it needs to have a few hooks to draw them in. Here's a suggestion of what I'd write as a summary for you.Skills, do you need the distinction between proficient and familiar? And with familiar skills, is it enough to be on your CV and/or applicable in a job? I also notice that they're all technical skills, do add some soft skills in there. Coupled with the "I code in my own time too" from the summary, it does paint you as one dimensional.
Experience, pretty much the format I've used. Explanation of your role and highlighting things you've done there. I would add the benefit to each bullet point. Taking "Proposed and developed a new source configuration management strategy (using Git) for new and existing projects in my area", my counter would be "so what?". I have no idea what "source configuration management strategy" is in practice and how it helps a company. Does it reduce costs/prevent error/allow more flexibility?
I wouldn't mind showing you my CV and maybe it could help, but I don't want to post it publicly on here. Send me a message if you'd like to see it.