HTML is missing from the skills-list. I'm not even kidding. Lots of HR-folks just compare lists of required skills with CVs and if HTML is missing, it's a pass. Add everything no matter how basic. Add HTML, CSS, Ajax, REST, jQuery. Don't just add the latest buzzwords. Lots of companies require knowing the old stuff, because they still use old stuff.
The other thing I'm missing is a more detailed description of your projects and your concrete role in them.
I'm a developer-turned-business owner who loves to explore the right tools for the job. I enjoy writing and documenting my journey. I use code as one of the tools to solve real problems.
Good catch, I'll be sure to add those! About the projects, I was trying to keep everything on a single page, would the projects be something for a potential second page?
Yes, if it's on the web, you can collapse details. If it's a PDF you could add one or two more pages. TBH I don't get the 1-page-ism. It's not like printing or scrolling is super expensive. The only caveat is that it's easy to become messy, the longer it is. As long as it's readable, 2 or 3 pages are fine.
The 1-page makes sense if other devs read your CV and can infer most missing info (oh they worked 10 years in front-end, they surely know HTML). I think it's good to have both, one for the HR-departments, one for the informal intro.
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.
HTML is missing from the skills-list. I'm not even kidding. Lots of HR-folks just compare lists of required skills with CVs and if HTML is missing, it's a pass. Add everything no matter how basic. Add HTML, CSS, Ajax, REST, jQuery. Don't just add the latest buzzwords. Lots of companies require knowing the old stuff, because they still use old stuff.
The other thing I'm missing is a more detailed description of your projects and your concrete role in them.
Good catch, I'll be sure to add those! About the projects, I was trying to keep everything on a single page, would the projects be something for a potential second page?
Yes, if it's on the web, you can collapse details. If it's a PDF you could add one or two more pages. TBH I don't get the 1-page-ism. It's not like printing or scrolling is super expensive. The only caveat is that it's easy to become messy, the longer it is. As long as it's readable, 2 or 3 pages are fine.
The 1-page makes sense if other devs read your CV and can infer most missing info (oh they worked 10 years in front-end, they surely know HTML). I think it's good to have both, one for the HR-departments, one for the informal intro.