DEV Community

Sagar Chakravarthy
Sagar Chakravarthy

Posted on

4 reasons to write your resume in Markdown

As Software Developers, we often use Markdown to write readme files, take notes or write a blog post like this one πŸ˜›. Its simple syntax helps format content easily. Apart from quick formatting there are several reasons why I would recommend writing resume in Markdown

🎯 Increased focus on your content

Content is the heart of your resume. But quite often we spend more time on its design and aesthetics. With Markdown’s syntax, you can write neatly formatted content first and then apply various themes or designs tailored to your needs.

πŸ“„ Easier to keep it updated

It is recommended to revisit your resume at least twice a year to keep it updated with your latest achievements, responsibilities and skills. With file formats like DOC, PDF, Tex or JPG it is extremely difficult (sometimes impossible) to edit without using any additional tools. In contrast, Markdown is just a text file which can be easily edited. Moving your sections around is as simple as cutting and pasting text. You can even store this file in a git repository to keep track of the changes made over time.

🎨 Flexibility to switch design

Markdown is rendered as HTML. And with a sprinkle of CSS you can create a beautiful, crisp and unique design for your resume. You can even change this design at any point of time without making any changes to your core content. A bunch of CSS themes for Markdown are available online.

πŸ‘€ Better readability

Markdown provides structure for your content in a relatively simple way because of its simple plain-text-formatting syntax.

Markdown is a great tool for formatting your resume with advantages like maintainability, readability and flexibility. When I was looking for a job, I created a bunch of designs for my resumes. I have now converted it into a web application where you can write your resume in Markdown, try out these designs and download as PDF. Check it out at Resumey.Pro and let me know what you think in the comments below πŸ‘‡

Discussion (0)