CV assistance

I did get a coding certificate and advice from the program I was in to make a resume that is appropriate for the tech industry. I have not found a job yet, but I know that other people in the program have, using the format that was recommended to me. I also, had 14 years experience in another field and wanted to completely change careers.

1. Make a resume and not a cv. That means just 1 page. That means removing a lot of stuff from your cv. (This was a pain point for me, but I had to remember that I am changing careers and I have to fully embrace it). You, instead, will have a fully-loaded linkedin that will be like your cv with probably even more info than your cv.
2. If you are looking for a Front End/Full Stack position give your resume some style. My previous advice in my previous career was always 12pt Times New Roman black, with traditional formatting and bullet points on white. But don't go too crazy. So take inspiration from any one of the simple ones from here : http://www.hloom.com/download-professional-resume-templates/ (do not include a photo if you are applying for a job in the US, however, in other countries a photo is expected- be sure to check, if you are applying outside the US). But if you google 'creative resumes' - you will find images of resumes that I was told were way over the top unless you are a designer/going for a highly creative position. Also don't give your self points or rankings/levels on your skills- that was a big 'no no'- as your resume is supposed to be your brag sheet and giving that visual may be unintentionally negative.
3. Include your name, email (preferably me@mywebsite)- but an appropriate gmail one is fine, phone number, linkedin username (customize it into your name- rather than a long link) and github (you should have a github). You do not need to include your home address.
4. Top section after your header: skills - write the languages and skills you have, in my previous life I had to put ms powerpoint and word etc., but I have gotten mixed feedback about including these for a coding position.
5. Next section projects - this would be anything that you've worked on that is live on the web/on github that you want to show. (again, I did a program so they made us do projects that ended up here- so this was easy for me to put together).
6. Experience (this would be jobs that you've had) - write a brief 1-2 sentence summary, rather than listing each responsibility if it has nothing to do with coding)

7. Education (all the way at the bottom- another total opposite!)

8. No summary - though this is the MOST contested thing I hear. People seem completely divided about inducing a section like this. I currently do not have one and instead I always include a cover letter that addresses what would have been my summary.

I can say that with this version of my resume (no more cv!) and linkedin, no one asks me about my previous career and things stay focused on the new stuff.

It is very bare bones and jarring to look at compared to a cv.

I hope this helps!

Karolin's answer is fantastic! Thank you for the insight!

Russell Kree, you mention you don't have a portfolio yet. If possible, I'd highly recommend creating one that can highlight some of your works. Just because you don't have one now doesn't mean you can't have one next month! As I'm sure you know, the job finding process is all about framing and selling yourself. While you may not have much you can put on your resume, showcasing your knowledge and skills via a portfolio will be the next best, and perhaps most critical, way to selling your developer skills. We wish you the best of luck with this!