I want to add that you need to remember that your CV has two audiences:
- Recruiters/HR who don't know how the technology is being used, and are possibly just looking for some key buzzwords.
- Technical leads who do know how the technology is used, and aren't going to be impressed with just a list of buzzwords, or self-assessed x/10 ratings for technologies.
The challenge is - you need to appeal to both people.
The way I solve it, is at the start of my CV I have a section that looks like this:
Core Skills Some Exposure
This is to appeal to the recruiter who just needs to tick some boxes.
Later in my experience section, I write it like this:
Acme Ltd 2005-2007
I was responsible for creating a frontend with React/Redux,
working from designs from a designer,
and a REST API spec from the backend team.
I also created frontend tests using Jest and Enzyme.
ImmutableJS, Jest, Enzyme, Git, Jira.
The technologies used list is to provide more credibility to the recruiter for the technologies you have used (ie. how recent it is), while the description of the task is to provide credibility to the technical lead (ie. that you're not just listing some technologies), and give them some context for them to ask further questions.
You'll note that I include 'git' and 'jira' in the technology list. This is more for the recruiters sake - as this may be one of the things they are looking for, whereas a technical lead really doesn't need a sentence explaining how you used git and jira, unless you were doing something particularly special with it.