I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
OK, I'm going to poke as many holes in this as I can:
Consistency (i.e. evidence of attention to detail and caring about your presentation) is important.
Some of the skills are written as "Frontend - React, Vue, Bootstrap" and some as "Version control using git or svn". I'd recommend picking a style and sticking to it. Keep capitalisation consistent between technology names and use a dash to separate the label from the list instead of the word, "using". There's no reason for some lists to have "and" or "or" before the last item and some not to. I'd leave it out, because that makes the text look a little less dense on the page.
Lines like "provisioning of customer accounts in vendor systems" are pretty vague and look like filler to me. If I was interviewing you I'd maybe ask you to elaborate but I might make the assumption that you just put it in there to make the list have more than two bullet points.
Remember that when someone (well, someone like me) looks at a CV we're noticing the weakest parts and we're thinking that if the candidate included that bit, it's because they couldn't come up with anything better. The best CVs make it look like the candidate had just shown us some examples of how good they are, leaving the reader to imagine that everything else they've done is up to the same standard.
This is the most interesting line in your CV:
Utilize MongoDB aggregation framework and SQL to write reports to save company upwards of $300,000/yr
Instead of that I might choose to write this:
I planned and developed a reporting system for MongoDB which reduced operating costs for the company by $300k per annum.
Obviously it depends what you did and that might not be completely accurate anymore, but I'm trying to put the emphasis on you doing something. I'm also trying to avoid contractions like "/yr" and words like "utilize" which make things sound buzzwordy. I've also changed the voice so instead it's not so passive and it's more about you. I know some people say that you shouldn't use words like "I" too often in your CV, but, well, I don't agree :P
I don't think you need to include the heading on every page1. Reviewers are probably either going to be reading this on their screen or on a printout that they're bringing to the interview, so they're not going to get anything mixed up. This means you get more space on the page to sell yourself and you don't need to use titles like, "... continued".
The Education section seems padded compared to the rest, because it's spread out with extra line spacing and includes irrelevant information. When I read things like "August 29, 2018" I think, "why do I care what day you graduated?" It's also inconsistent with the way you write dates for the work experience.
The classes you mention will already be covered by your skills list... except I notice they aren't. You thought it was important enough to mention that you learned C++, but it's not something you list in your skills. My interviewer brain asks, "did you fail that course?"
I could also suggest you shorten the skills section to just include the skills relevant to the position for which you're applying. Maybe you could keep a copy of this "master" CV and let it flow over a few pages. Knock yourself out with writing this copy but trim it down for each role you apply for by removing things that don't matter.
Maybe change the heading "Work Experience" to "Relevant career history" or something2 because "work experience" is a phrase associated with people interning or still in education, and might put people off who just glance at the document.
It looks like you have a lot to offer, all I'm suggesting really is that you tidy it up a bit.
yes, I know you only have two; I'm being wildly general. ↩
that's terrible, too, makes you sound like a robot. But I can't do better before my morning coffee! ↩
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.
OK, I'm going to poke as many holes in this as I can:
Consistency (i.e. evidence of attention to detail and caring about your presentation) is important.
Some of the skills are written as "Frontend - React, Vue, Bootstrap" and some as "Version control using git or svn". I'd recommend picking a style and sticking to it. Keep capitalisation consistent between technology names and use a dash to separate the label from the list instead of the word, "using". There's no reason for some lists to have "and" or "or" before the last item and some not to. I'd leave it out, because that makes the text look a little less dense on the page.
Lines like "provisioning of customer accounts in vendor systems" are pretty vague and look like filler to me. If I was interviewing you I'd maybe ask you to elaborate but I might make the assumption that you just put it in there to make the list have more than two bullet points.
Remember that when someone (well, someone like me) looks at a CV we're noticing the weakest parts and we're thinking that if the candidate included that bit, it's because they couldn't come up with anything better. The best CVs make it look like the candidate had just shown us some examples of how good they are, leaving the reader to imagine that everything else they've done is up to the same standard.
This is the most interesting line in your CV:
Instead of that I might choose to write this:
Obviously it depends what you did and that might not be completely accurate anymore, but I'm trying to put the emphasis on you doing something. I'm also trying to avoid contractions like "/yr" and words like "utilize" which make things sound buzzwordy. I've also changed the voice so instead it's not so passive and it's more about you. I know some people say that you shouldn't use words like "I" too often in your CV, but, well, I don't agree :P
I don't think you need to include the heading on every page1. Reviewers are probably either going to be reading this on their screen or on a printout that they're bringing to the interview, so they're not going to get anything mixed up. This means you get more space on the page to sell yourself and you don't need to use titles like, "... continued".
The Education section seems padded compared to the rest, because it's spread out with extra line spacing and includes irrelevant information. When I read things like "August 29, 2018" I think, "why do I care what day you graduated?" It's also inconsistent with the way you write dates for the work experience.
I think this covers everything for that section:
The classes you mention will already be covered by your skills list... except I notice they aren't. You thought it was important enough to mention that you learned C++, but it's not something you list in your skills. My interviewer brain asks, "did you fail that course?"
I could also suggest you shorten the skills section to just include the skills relevant to the position for which you're applying. Maybe you could keep a copy of this "master" CV and let it flow over a few pages. Knock yourself out with writing this copy but trim it down for each role you apply for by removing things that don't matter.
Maybe change the heading "Work Experience" to "Relevant career history" or something2 because "work experience" is a phrase associated with people interning or still in education, and might put people off who just glance at the document.
It looks like you have a lot to offer, all I'm suggesting really is that you tidy it up a bit.
yes, I know you only have two; I'm being wildly general. ↩
that's terrible, too, makes you sound like a robot. But I can't do better before my morning coffee! ↩