One thing I've always found to be good advice is the layout of your skillset if you're presenting that in some way. There are a few key points:
At some point someone responsible for recruiting will look over it. Sometimes, they need to review a lot of them in a short space of time, so you need to ensure you're not dropped in that first round of review.
Avoid scoring systems for your skills. I've had to review CVs where candidates had marked themselves 10/10 on a particular programming language, yet only had a few years experience.
Whatever you've got on the website might be printed out, so consider how that will look.
An approach I've found useful for myself is to present my skills in a table, and mark them with words like "fair" or "good" to explain my level of each of them. Lastly, I set up print stylesheets in the CSS to ensure that the table was presented well and looked good in grey without images.
Some comments have been hidden by the post's author - find out more
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.
One thing I've always found to be good advice is the layout of your skillset if you're presenting that in some way. There are a few key points:
An approach I've found useful for myself is to present my skills in a table, and mark them with words like "fair" or "good" to explain my level of each of them. Lastly, I set up print stylesheets in the CSS to ensure that the table was presented well and looked good in grey without images.