Exactly. A CV is a marketing tool to get you to an interview. These days you probably have to make sure all the right keywords are in there too so you don't g

Exactly. A CV is a marketing tool to get you to an interview. These days you probably have to make sure all the right keywords are in there too so you don't get filtered out by a machine, as well as getting noticed by a human. I've reviewed hundreds, if not thousands, of CVs in my time. This CV, while not absolutely terrible, is most definitely not great, and I'd go so far as to say below average. It does not help the person reading it make a positive decision. * It's hard to figure out what the skills and experience are. If I have to read the entire thing work to even know if you might be a fit, there's a good chance of just going on the rejection pile. * It's not clear what kind of role the person wants. Do you want to do front end? Mobile? Back end? Full stack? This can be tailored of course to a particular role if needed. * It's extremely passive. Saying "worked on X" is about as interesting as watching paint dry. * One page is not enough for a technical role. I know some people say keep it to one page, but to me, 2 (and sometimes 3) pages is OK if it's not horrid to read and I have reasonable confidence there might be a fit there (not if I have to read the whole thing though to figure out if there might be a fit). * There is absolutely nothing in it to make me think "ooh, would be good to talk to this person." Fundamentally, this CV says "I have built some different software for people. I have nothing interesting to say about it. I dont care if I waste your time reading it.". In a strong market that might be enough. In a weak market it will be straight to the reject pile.