Cover image for Put dev.to on your resume!

Put dev.to on your resume!

isaacdlyman profile image Isaac Lyman ・1 min read

You can do it like this:


Why? Because writing on dev.to suggests some important things about you to potential employers:

  • You do more than the bare minimum - you're thoughtful about your work.
  • You enjoy sharing knowledge. When you change jobs, you probably leave documentation behind for the person who will take your place.
  • You're a good writer. If you ask me, technical writing is 2018's most undervalued skill for software developers. Communication is at least half of what we do, and with remote work growing in popularity, writing clearly is becoming essential throughout the industry.
  • You're part of a large and active professional community. This is a force multiplier when you're working on obscure scaling problems or difficult bugs.

You might be shy about including this on your resume because you haven't gotten a hundred ❤️s or been mentioned in the dev.to newsletter. Don't worry about it. Some of the most useful and well-written posts I've seen on this site never got a lot of attention. But they helped me when I needed them, and that counts for a lot.

Oh, and while you're at it, do you have a GitHub #graveyard? Add that too. You're doing cool stuff. Make sure people know it.

Posted on by:

isaacdlyman profile

Isaac Lyman


Author of Your First Year in Code (leanpub.com/firstyearincode). Find more of my writing at isaaclyman.com/blog.


Editor guide

Yes, 100% agree. People have been using Twitter, GitHub and LinkedIn in this regard for a while, and feeling like DEV profiles could be much better representations of people's full picture as a candidate was a big driving force in how we developed the platform in the first place.

As a matter of wonderful timing, as of today you can now also use the DEV badge via FontAwesome for personal portfolios etc.


Hey @ben How about a resume generator?


Where did you found statistics about top 7 author and total views?

I'm still curious about it.


Total views is a membership feature. You can see it in the dashboard.



Total views is available on your dashboard if you have a Sustaining Membership.


I don't know if follower count is a membership feature or not. My Top 7 badge appears in my profile, in the right-hand column underneath my GitHub repos.



I haven’t put dev.to specifically on my resume, but my blogging activity definitely has its place there. Agreed with what’s been said on what it tells about your communication skills and commitment. I’ve already received messages from recruiters referring specifically to one of my blog posts, which only confirms the point! That is, if you don’t have a separate blog, dev.to is definitely a good choice — most people out their GitHub on their CV, so why not?


I have this same experience. Regular blogging is a great way to gain attention.


Thanks for the idea Isaac!

I was thinking about mentioning a few of my most popular posts on my resume, but your example is way shorter and would probably fit into a single page (depending on your history).


I can confirm that writing / personal blog and promoting said writing helps a person stand out from peers. Not a requirement of course, but if you want to stand out, write and promote your knowledge.

Myself, I list my professional social accounts (GitHub, StackOVerflow, Dev.to) on my resume. I really believe the "You are your own best cheerleader" mantra.

Thanks for the article Isaac.


Can I get that resume font/template ?


Sure! Email resume@isaaclyman.com and I'll send it to you.


Sent you an email too. 😄


Where can you find those stats i.e. follower count, total views etc? I don't even see an option to see who I am following or who are my followers.


Total views is available on your dashboard if you have a Sustaining Membership.


I don't know if follower count is a membership feature or not. My Top 7 badge appears in my profile, in the right-hand column underneath my GitHub repos.



Thanks, I can find the follower/following list now.


I'll be on the lookout!


Great post!

Do you feel dev.to writing has a place on a Linkedin profile as well? Would you put it under 'Publications', 'Projects', 'Volunteer Experience', somewhere else?


I have put this under Volunteer Experience although it could as well be under Projects. I think Publications is better suited for peer-reviewed academic articles which DEV does not publish (as of now).

Looks nice on my profile as well!



What a great idea :)


Not all companies/hiring managers/recruiters are involved online. Most still ask for paper resume.

If you network, the paper resume is just a formality for HR (in USA).


There should be a free trial of the membership subscription like first-week free :).


I think it's interesting expiriense.
Need more test on a HR's and Employeer's. 🤓


Thanks for your idea!
I think the young as me should actively participate in the communication like this to get more and more knowledge and experiences.


I have a dev story, but so far nobody's asked for it. Recruiters still request my resume.


I did, but do not think anyone reads them anymore. Ppl are so crazy to calculate how many years of React you have 😀


I've been wondering about a similar thing for some time. So let me ask you:

Is it better to have your own url (hence own blog) in the CV?

isaaclyman.com/blog looks more pro than dev.to/isaacandsuch, right?

(We all love dev.to but as a potential employer that doesn't need to be aware of dev.to)

Just asking because I've been thinking of hosting my own blog, I've created it and everything but I can not be bothered having to maintain it. Hitting publish here is just easier than pushing to whatever platform then coming back here and doing it again.

I'll probably end up doing so, as everyone seems to be doing it, but letting the dev team take care of the hosting seems simple for the moment.

Great advice btw.

Oh, also, where do you get those statistics for dev.to, is that a feature I don't know about


It is a bit of a hassle to cross-post, unfortunately. But I think both options are relatively impressive. I mean, most devs don't blog at all. So while having your own hosted site proves that you know how to build and deploy a website, I think a link to dev.to is just fine.


Thanks, that's what I thought.

Maybe I edited the comment after you read it, I was wondering, where are we able to see the number of views here? (you added them on your CV)

I see them on dev.to/dashboard. I think it's a perk of being a paid member of the community: dev.to/settings/membership.