Resume for the programmer? No, have not heard

    Summary is an increasingly useless artifact for a programmer.

    • Good programmers do not have time to keep it up to date. Often the most sensible candidates have the most unreadable and terrible resumes. Making a well-written resume takes a lot of time. As a rule, there is time for this only for those who are unemployed and, instead of engaging in self-education, endlessly draws up a resume.
    • A list of past jobs means little. Three years of experience in Yandex? Congratulations! But 100%, this only means that you were able to pass an interview. What exactly you did and how well - there are no answers in the summary. Most of the developers worked for unknown companies, many of which did not even reach the release.
    • The number of years of experience is useless if it is not known what tasks were solved. Perhaps you spent 5 years supporting the old project and you only know all the bugs of the closed library X, which is not used anywhere else.




    Well and most importantly - they’re not looking for a resume. A good profile on Github, Habré or Stackoverflow will give far more job offers than any super-duper resume. And if you really want to write something to the employer, it is better to spend energy on the cover letter - tell us why you want to work here and how your experience, skills and enthusiasm will help the company.

    What do you think, Khabrovites?

    Only registered users can participate in the survey. Please come in.

    Did the resume help you find your current job?

    • 17.9% yes, played an important role 167
    • 30.3% received an invitation to an interview 282
    • 20.7% seems to be no 193
    • 30.8% I have no actual resume at all 286

    What was the significance of the resume of the programmer you recently hired?

    • 18.6% played an important role 82
    • 54.3% filter for boyfriend 239
    • 27% did not even watch 119

    Also popular now: