• 11 Posts
  • 1.76K Comments
Joined 11 months ago
cake
Cake day: July 2nd, 2023

help-circle











  • Neatly put resume with some obvious things to improve. Order of elements should be different, for example working experience and references usually come last because when we are looking to hire we are quick glancing over skills first then look where you worked. Those being on top of the page matter.

    So I’d list things this way: Education, Technical Skills & Certifications, Projects, Experience, References (if you have any).

    Another thing I’d like to point out is if you have GitHub/GitLab account do link that. Your code speaks a lot louder than CV and might get you past first round of elimination. Managers do look at that and it matters a lot. Am not in the job market for past 10 years or so but I still get job offers regularly just because I have publicly available code and few open source projects of some popularity.

    You are already doing a great job at keeping things short but I’ll say it anyway: Don’t inflate skills and knowledge to make the resume look richer. Write what you are confident in using and what you’d like to use eventually. Any developer can say ah I can write 15 different languages, because once you learn syntax and few intricacies all of them more or less are the same. But if you don’t know standard library and have experience working with it you might paint yourself in the corner where you’d get a job and have to work on language you are not comfortable with or even worse get tested using it and then fail on a stupid thing. Most managers know if you are proficient in one language, learning another is matter of time. That and you want to put the best foot forward.

    Good luck. Your sneaking suspicion is wrong. If only all the resumes I had to review were this concise.