Summary of programmers. Part 1 (bad)

    Honestly, when I was looking for work, my resume could be safely classified as bad. Yes, there were several good sections (like, but I wrote 2 books and 30 articles), but also there was a table of skills with a line: C #, 1 year of experience, Intermediate (!).

    Now I read a lot of resumes and invite people to interviews. Over the past 3 years, I have conducted about a hundred interviews, and I have seen a resume 5 times more. So now I have a pretty clear idea of ​​what I want to see in the resume. But first, I’ll tell you what I don’t want to see in the resume.

    Patterns


    Many outsourcing companies have come up with resume templates. The motivation, in principle, is understandable, they want to unify everything in order to use machine learning to extract good candidates, they all looked the same as ordinary soldiers in the ranks. However, these templates are the same for all positions and are made up by the wise CTO -minded HR, who have no idea what a really cool programmer is.



    Filling out such a template is like signing up on your own insolvency to think and make a normal resume. This is such a gesture in the direction of the potential employer "here is a resume for you, not especially I want to work for you." Do not particularly want, do not send him, damn it. Why waste your time and others?

    Templates align developers. Good developers in them look average, and bad, which is typical, too. Therefore, it is such a convenient mechanism to jot down a lot of text and numbers without saying anything useful.

    Skill tables


    They came from templates and firmly stuck in the minds of developers. Most half consider it their duty to insert a list of technologies, the years of their use and level of knowledge. Well, it’s good if there is something specific in the list, such as TDD or DSL creation. But no, usually there is PHP, 4 years old, an expert.



    Such lists contain very little useful information and, at best, are scanned in 3 seconds for something interesting. And in any case, this is a minus to the overall impression of the resume.

    List of projects


    To talk about the projects in which I took part seems pretty logical. Unfortunately, this story is often approached from the wrong side. I am interested in what you specifically did in these projects, what difficult tasks you decided, what was interesting to you in them and what was not. I'm interested in the facts. Instead of facts, a list of technologies and general phrases such as "developing an application architecture, implementing basic modules, requirements analysis, bug fixing" are usually given.



    Tell me better what you achieved in this project, what you learned new, what you are proud of - it is much more interesting.

    List of personal qualities


    Another section that is useless to browse through is personal qualities. These are, for example: I



    must say that this is a list from my resume of the 2004 sample. In principle, everything is true, but everyone writes it, so the benefits of such a section are vanishingly small. You will not write that you are "an introvert who wants to work alone on complex projects." You write "teamwork." Personal qualities must either be confirmed by examples or not written at all.

    Empty letters


    The saddest thing is to get something like this:



    Well, of course, I’ll open a resume, but the first impression goes bad. And if there is nothing interesting in the resume, then our acquaintance will end there.

    In this case, the person turned out to be an excellent programmer (and the resume was not bad).

    Another mistake is this:



    It looks like a person is interested in nothing but money. This, of course, has the right to life, but hardly a good way to start dating. Like, you come to a meeting with a girl, sit down at a table in a cafe, and start a conversation:
    - Hello, I'm Vanya.
    - Hi, I'm Alexandra. What car do you have? Is there an apartment?

    It is best to write something personal, interest, show your level - this can be done in just a few sentences. Even one:



    Total


    The vast majority of resumes contain only what is listed above. Therefore, you have to literally read between the lines to form an opinion about a person. Remove it all from your resumes and think, than to replace.

    And yet, never send resumes from mail.ru. This is a bad sign.

    UPD: They complain that I rate people by resume and that's it without talking. Well, how else to evaluate if at first you have nothing besides a resume on your hands? I’m complaining here that very often good programmers do not differ from bad ones by resume . I would like to be different. That's all.
    I call everyone who has a glimpse in the resume. And more than once it happened that a bad resume hides an excellent developer.

    UPD2: Summary of programmers. Part 2 (good) continue the conversation.

    Also popular now: