Resume Checklist

Everything you need for a good resume!

Resume checklist ✅

Download the following to assist you with the resume.

15KB

Resume_Checklistinternshipclass.docx

By now you should have a strong draft of your resume.

But let's make it even better! Check all these boxes for an even better resume!

• File Naming convention: “FIRST_LAST_Resume_Company Name_2021”+ make PDF!

• Personal information: name, phone #, City, email, github, linkedin

• Formatting: simple

  • No fancy typeface, stick to: Helvetica, Avenir, Baskerville or similar.

  • Avoid images, icons or pictures, stick to black and white.

• List your languages and frameworks: list your strongest first and weakest last

• List your experiences and projects.

  • Ordering: put work most to your intended job role first

  • Bullet point format: AR [Action - Result]

    • Action: Emphasize your skills and contribution - start each bullet point with the actions/skill verb you used in the project. Why? Recruiters skim resumes. Start with verbs to make your contribution pop-out. What verbs should you use? Use the buzzword verbs in job descriptions of your intended role. For instance, when applying to startup jobs use verbs like “built” “initiated” “created”. When applying to frontend roles, use verbs like “designed,” “interviewed,” “managed,” etc.

    • Result: Use data to quantify your impact: show your accomplishments in numbers, not just words.

      • Product: # of users / downloads / reviews / page visits - this communicates the scope of the project, impact, scale. It’s way more impressive to say my “app reached #X users” than to simply say, “I launched an app”.

      • Work: # of people managed / # partnerships / #contest won (“1st place out of 200 students”) / # people collaborated with / “worked with X company’s API”

    • Model your resume off these examples

      • Weak: Coded that app’s backend

        Strong: Applied OOP, algorithms, pointers, memory allocation, and data structures such as: binary search trees, queues, lists and doubly linked lists.

      • Weak: Designed the frontend of the app

        Strong: Designed using Sketch, 20 user tests, and iterative wire-framing process.

      • Weak: Managed a budget to plan hackathon events for students Strong: Managed $9,000 budget to plan hackathon events for 1,400 students

      • Weak: Wrote articles on code infrastructure

        Strong: Wrote 3 articles on code infrastructure, generating 10,300 page views, 2,804 likes, and 523 tweets. [shortlink to post]

• Exclude Icons: Icons look pretty but can’t be read by some recruiter resume scanners. They can throw off the formatting of your resume. Keep format simple with plain text and simple columns.

• Length: One page max

Keep improving your resume until you check all the boxes.

Adapted from makeschool.org