The first thing you should pay attention to is a neat structure. A brief description of HR will be read as an art book from the beginning to the end (which is why it is necessary to make a small booklet out of this book, which will not take a lot of time from the manager). At the same time, a full description will rather not be read, but viewed in search of the necessary information. So you need to make the “navigation” on the resume as convenient as possible.
No, of course, there is no need to make a subject index or arrange hyperlinks (although if you do, I think no one will be upset at least it will be original;)), but it’s still worth sharing the full description into parts and sections within each part. Usually the first part is devoted directly to skills and knowledge. Each section in this part should be devoted to one particular group of skills. Personally, I usually highlight the following sections: Main. Programming languages and platforms. Technology specialized language or platform. Operating Systems. Database. Foreign languages.
In the basic skills, you should specify everything that was listed in the brief description, plus what does not fit into other items, but what I really want to say. For example, if you go to a game dev, enter the math and physics; if in financial structures the economy; if you are going to be engaged in graphics and know the photo well indicate it. Programming languages and platforms are those that you know best or simply consider important, 5-6 languages are usually sufficient. Technologies in detail about all the technologies with which you have ever worked and which you still somehow remember. Here, every little thing can help interest the manager.
However, it should be understood that any of your technology can be used in an interview against you, and it will be very ugly if you can’t answer at least basic questions about it. Operating systems this item makes sense to indicate if you worked not only under Windows, but even under Ubuntu. Database and foreign languages, I think, is not worth explaining. A good example of a list of skills is a standard E-questionnaire: you specify three parameters for each skill in it: 1) experience (number of years of use); 2) the level of knowledge (from novice to expert); 3) the year when this technology was last used. The Epam questionnaire is primarily designed to automatically save to the database, so there are practically no “for people” fields. However, in your personal resume, no one bothers you to add another column a description of where and how you used this skill.