Resume writing experience

    Problem


    Not so long ago, I needed to update my resume. The last time I did this a few years ago, so I decided to write a resume from scratch.

    In this post, I would like to talk about my experience in creating a resume: about the intended target audience and design details. I’ll make a reservation that I have never worked in the human resources department, so I should be skeptical about considerations.



    The target audience


    It seems reasonable to approach a resume as a user interface. Indeed, a resume solves quite specific tasks, a resume has “users”, at a certain level a person is judged by a resume. Let's look at the methods for developing interfaces: we will define users and usage scenarios, and then we will write a resume so that it satisfies eighty abstract percent of users.

    I decided to focus on small companies (up to 200 employees). I note, I will consider the general case. There are certainly exclusion companies. Such a standard approach may not work.

    We single out the users of the resume and their tasks, that is, what they can expect from the resume:

    1. Employment agents.On the table the agent has a bunch of resumes and a bunch of vacancies. The agent’s task is to look at the resume and understand what vacancy a candidate can apply for. It can not be assumed that the agent is versed in the subject area. Also, one cannot assume that an agent can spend a lot of time reading a resume. It should be noted that this user is not the main one: it is quite possible to send a resume yourself.

    2. Human Resources.An HR employee receives a resume stream from hiring agents or candidates. The employee’s task is to understand which resume best suits the requirements of the vacancy and whether the candidate is suitable for the company. It cannot be assumed that an HR employee is well versed in the subject area. However, it can be expected that he will devote some attention to the resume. The HR employee is one of the main users: his decision affects the future fate of the candidate.

    3. Project managers.An HR employee passes the most interesting resumes to the project manager where the employee is required. The task of the project manager is to understand whether it is worth inviting a candidate for an interview. I want to believe that the manager is well versed in the subject area and is ready to carefully read the resume. The manager is one of the main users: his decision affects the future fate of the candidate.

    4. Programmers conducting interviews. The programmer will receive a resume from the manager. Most likely it will be attached to an invite for an interview. The programmer's task is to understand what you can talk about with the candidate. I want to believe that the programmer is well versed in the subject area. It seems to me that one cannot assume that a programmer will read a resume. At the interview, everything will become clear.

    Resume structure


    I would suggest the following resume structure:

    1. Name, email and phone
    Agents, HR and managers should just contact the candidate without reading the resume text. Therefore, I would bring the contact information up.

    2. Block "About Me"
    This block is for hired agents and, most importantly, personnel department employees. They may not be well versed in the subject area, however, according to this block, they will be able to evaluate the “adequacy” of the candidate. Can this person tie two or three words together? Does he copy-paste stamps from the Internet? Can it pretend to be a normal person?
    It seems to me that this block should be written very carefully: they say that some HR departments for "work well in a team" (or another stamp) can send the applicant in the ass.

    3. Skills
    block And this block is for hiring agents and personnel department personnel. In this block I would put abbreviations of technologies with which the owner of the resume is familiar. This unit should help to quickly understand whether the candidate is familiar with the required technology. For example, if you are looking for a Java developer, it is enough for an HR employee to run this block through his eyes to see that the applicant is familiar only with Javascript. Moreover, this block can help the interviewer. If suddenly there is nothing to talk about, he will always be able to look into this block and ask a question about some other technology.
    The difficulty in compiling this block is to find a balance. On the one hand, it’s dangerous to indicate everything that I’ve ever met, because it can create a false impression (yes, I wrote a site on Rails a couple of years ago for fun, however, I can’t call myself a Ruby programmer). On the other hand, too few skills can deprive a candidate of interviews in companies where some skills are not perfect (for example, CSS knowledge may be indicated in the requirements for a J2EE position of a developer).

    4. The block "Experience"
    This is perhaps one of the most important parts. Most likely, the project manager will read it and decide whether it makes sense to talk with the applicant. Where did the candidate work? What position? How long? What was he doing there? Can he articulate what he was doing? During the interview for each line of this block, I am ready to answer, explain, tell in detail, show a screenshot and dance a jig. Therefore, it seems to me that it makes sense to focus on successful projects, and errors should be mentioned very carefully. I note that the programmer conducting the interview is likely to read with interest about the last job, and can start a conversation about recent projects.

    5. Block "Education"
    I would indicate a university, the highest scientific degree and specialty. Many indicate received certificates. An employment agent or HR looks at this block if the requirements indicate that higher education is required. Most likely, the manager or programmer will look at the university, hoping to see the "countryman". Certificates will certainly attract attention.

    6. Block "Other"
    It seems to me that this is a rather important block. Both the manager and the programmer conducting the interview will drop by. Here I would indicate any difficulties that the employer should know about (for example, the lack of a suitable visa, the inability to travel, and the like). Moreover, I would point out any projects that may not be directly related to work, but prove that the candidate is interested in IT in his spare time. Quadrocopter, a plugin for Chrome, an account on github, a blog about a secret bunker in Cupertino - all this perfectly reflects the interest of the applicant. For example, to make it clearer, I made a small site-supplement to my resume. On this site I have put together links to my personal projects.

    Decor


    There are a lot of fonts, flowers and pins. Learning “design” is not grateful, so I’ll try to talk about my experience. I tried to use the font created for computer displays, to use four styles: for the title of the resume, for the titles of the blocks, for the links and for the main text. Of the colors I used, only black and dark gray. Just in case, I was convinced that the resume looks decent if it is printed. Well, of course, I opened a PDF with resumes on different platforms, check that everything was displayed as it should.

    Conclusion


    I hope that these considerations seem useful to someone. You can see my resume here .

    I really hope for comments, suggestions and tips for writing a resume!

    Also popular now: