STEM Resume Guide

Format

  • Consistent font size – no smaller than 10pt smallest, dark enough to read when printed (no light grey)
  • Clean and even spacing, formatting looks clean and professional, not a lot of white or wasted space
  • Equal margins 
  • Dates and years right-aligned and in a consistent format (Apr 2019 vs. April 2019 vs. 4/2019)
  • Grammatically correct, no spelling errors
  • Resume is one page
     
      

Header

  • Name: largest font on the page
  • Github, LinkedIn, blog, personal site, Twitter (if relevant) 
  • List URLs – hyperlink, so all are functional
  • Email address, Phone Number, Location (city, state only)
  • Header is balanced (not three lines on one side and two on the other)
     
      

Technical Skills

Grouping/structure options – 

By proficiency: proficient, knowledgeable, familiar OR proficient, intermediate, basic/comfortable – there are various ways to express this. Make sure you group at the appropriate competency level (to the best of your ability), and can speak to how you’ve leveraged your skills if asked about in an interview. 

By type: languages, tools, frameworks, databases, etc. 

List out all technologies under the ‘technical skills’ section, without differentiating by competency or type, though this implies proficiency across the board.

Either type that you choose, ensure that you list out from most to least proficient. 

Don’t leave out anything (even really basic). If you used Ionic in a project, list it in tech skills. If you learned C or Python in a class 4 years ago, you have some familiarity.  

Consistent formatting throughout the resume. I.e. Angular vs. Angular.js vs. angular.JS  
  

Projects (optional but STRONGLY encouraged for Data Science, Analyst, and Software Engineer roles as tech recruiters expect this on a resume)

Project Name | Your Role (Software Developer, Full-stack Developer)

Project Link | Date

Technologies: A, B, C

 1-2 line description 

  • Contribution 1 
  •  Contribution 2

Note: Do not start your contributions section with “I contributed…” that is implied. Use strong action verbs. Do not use the same verbs for each project, when starting each bullet. People are often inclined to write “I worked in a group of X” – THIS IS NOT NEEDED. 

Ask yourself….

  • What problem did your project solve? Clearly articulate the need or challenge addressed.
  • What was your specific role and contributions? Highlight your technical responsibilities and leadership within the team.
  • What technologies or tools did you utilize? Showcase your technical proficiency and problem-solving skills.
  • What were the project outcomes and achievements? Quantify your impact using metrics or results whenever possible.
  • How does this project demonstrate your potential as a future professional? Highlight the transferable skills and knowledge gained.

This will help you write bullets for your projects! 

Contribution Example: “Built a e-commerce website from the ground up utilizing x, y, and z creating a platform which included more than 30 features such as a, b, and c with fully functioning x which did y.”
  

Experience

Reverse chronological – most recent listed first

Your Role is listed for each experience. For projects, this would mean Software Engineer, Data Scientist, etc.

Use bullets, not paragraphs. No hanging lines (when the bullet point extends over the line just like this) 

All bullets start with meaningful and powerful action verbs; focus on the impact

Understandable by core audience: technical recruiter, developer interviewer, CTO

Should include prior experience, even if unrelated to Tech/ STEM. Highlight your transferable skills.

Quantify prior work experience! Beyond a list of tasks, think about your accomplishments and results. Seek advice from your coach if needed!

Add “So What?” at the end of each bullet,  when trying to decide which experience(s) to keep on your resume

Education

List the degree you received if applicable, including BA or BS (not just your major) 

Add any relevant coursework (optional)

 

Volunteer Activity (optional)

Do not take up space on Interests if you could use more detail in Tech Projects or Work Experience.

Format Example: 

Line 1: Organization Name  (if wanting to keep anonymous > Name Type of Organization)| Your Role/Title| 

Location (City, State) | Date range of participation

Line 2: High level summary of your role and contributions. 

Alternative line 2: Provide 1-2 bullets, staring at line 2, of specific achievements.