Experience matters for sure. Number of years working with a specific technology don't matter much. List the experiences, the details, your impact, your challenges. Not how many years you spent working with Java.
I have definitely seen candidates being rejected because they did not have "enough experience", meaning that they…
It could work, but there are several ways it could also go wrong. How would you like to read a book or news website that is divided in two columns. It could work… sometimes. It's hard to say without seeing it in practice.
I prefer to keep it simple. But if you feel strongly about it, go for it! And feel free to share with me if you want.
To be honest, I think it does look bad. Whenever I see a link, it's the first thing I look at. If it's a front end dev, I immediately check the source code quickly just to grasp some insights.
In my opinion, a simple page like this one gives A LOT more credibility than a template. Why? Great content, simple structure, an…
Thank you Polina Stoyanova! I'm glad you found it useful and that it inspired you to revamp your resume.
I think those two sections seem to be an excellent extension of my proposed structure. I would definitely keep them concise (half a page seems extravagant).
First of all, congrats on all those achievements! I think they're super cool, interesting, something you should definitely bring up at one point. But I'm not sure your resume is the best place to write that. I would not write those.
However… You seem quite invested. This is important to you. I've never won a half marathon…