I want to see the code that you are proud of. I want to know how you name the variables, how to decompose the system, how to check the input conditions and how much you like to complicate things. It is very desirable if there is a description of the problem, otherwise the understanding of the code and solution is difficult.
If you have an account on GitHub - great. If not - archive in zip will do (do not use rar for this purpose, please). If you have everything under the NDA - well, anything can happen, in this case we will do without a code.
Blog, articles, books
If you have a blog, include a link to it. If you have articles on any topic - include links to them in the summary. It is very interesting to see how a person puts his thoughts on paper. If you wrote a book - include a link to it in the summary.
Your interests, books and resources
I want to know what you read, how you deepen your knowledge in your craft. If you have an account on Shelfari or another similar resource - great (I have one). No, then I would like to see in the list a few books that have had a great influence on you. Well, for example, SICP or Patterns of Enterprise Application Architecture, or something else.
Even so (it can be shorter):
Such a list immediately makes it clear what the person is interested in. It helps to better prepare for the conversation, to ask more interesting and deep questions. If you do not read books, well, anything can happen. But I, perhaps, with caution will look at you when you first met. And it will be extremely interesting for me to learn how you develop. Maybe you are at leisure studying the code of open source projects. Or immersed in fresh preprints on
No need to repeat, no need to describe in detail all the projects where you have worked for the last 10 years. There is no need to repeat the entire list of technologies and an even more identical set of responsibilities in each project. Describe only the most interesting projects for you and tell why they were interesting for you, what problems you solved there (at a high level).
Your desire to emphasize your own importance with the volume of the resume does not work. I understand that writing a 4 page summary is easier than one.
Skill tables don’t interest me. But here is a simple list of technologies where you are an expert - completely. He takes a little space and helps to understand what it makes sense to ask a person, and about what - no.
Here is a list of very valid, well, a little bit could be reduced:
I wonder where you studied and when. I wonder which companies you worked for and how often they changed jobs. If a person changes jobs every 6 months, this will alert me (if there are no clear explanations for the reasons). If a change occurs every year, then it is within the normal range. If a person spent 5+ years in one place (which I must say is rare), you need to look more closely at his outlook (it may happen that in 5 years there was not enough diverse work that is not particularly good, although everything depends on the context).
By and large, I do not care what the font will be in the resume and what dash in the sentences. I perfectly understand that aesthetics are not always close to programmers, that they hardly read books on typography and design. For me, it is important that the summary will either:
a) available online by reference (and there is also a link to the PDF version somewhere).
b) sent in pdf format.
Ease of design is welcome.
The perfect resume is 1-2 pages of information written in human language for other people. It is very important for me to see a person in the resume, not a robot with stitched skills. Help me do it.
But no less important is the grammar. Use the site for this. Good luck to you. I hope it will be useful