A list of technologies can help a reader scan your background, but it does not show what you can do with them. Pair the skills most relevant to a role with examples that make your experience easy to evaluate.
Give each skill useful context
- Separate tools you used in production from tools you explored in a personal project.
- Mention a concrete task, such as testing an API or improving a form, instead of rating yourself with vague stars.
- Remove skills you cannot discuss comfortably in an interview.
Make the evidence findable
A resume bullet, portfolio case study, or repository can support a skill claim. Keep the tool name consistent across those places so a reviewer does not have to infer that two different labels mean the same thing.
Choose a short list based on the role rather than copying every keyword from the posting. Accuracy and evidence help both human reviewers and any later conversation about your experience.