Your resume is mostly about word smithing.  What you have done, major projects, accomplishments and career goals.  Make sure to include the alphabet soup of acronyms for technologies you have worked with, and reinforce them in your work history.  Proof&#x2F;portfolio work is a separate issue.<p>Build something slightly more than trivial for yourself, and host it somewhere.  This can even be your resume&#x2F;personal website.  Put the relevant code up on Github under an appropriate license.  Bonus points for actually using Github Pages to self-publish your project.  Bonus points for automating this.  Travis-CI is a free option, and you can encrypt your GH credential information to publish on a merge&#x2F;commit to master.<p>If you&#x27;re using modern JS tooling, modularize what you can into discrete npm modules, and re-use what&#x27;s already available.  This will show far more than what is on your resume.<p>These are just suggestions, if your work history doesn&#x27;t demonstrate a strong knowledge&#x2F;aptitude on its&#x27; own, your GH profile can account for a lot.<p>Also, interview and other soft skills are important.  About half of the work I&#x27;ve had the past decade has been via connections at local user groups.  If you have local C#&#x2F;.Net or JS&#x2F;Node user groups, start going regularly.  Most will meet once or twice a month in most major metro areas.  Phoenix, for example, has 5 technology groups around .Net, 3 around JS&#x2F;Node and others on IoT and Web tech that you could go to meetings every evening if you wanted to.  Every meeting tends to have at least a few people actively hiring.