How to Write a STEM Internship Resume

A STEM internship résumé has one job: to show a busy reader, quickly, that you can do the kind of work the internship involves. For most students, the best evidence isn’t a long job history. It’s what you’ve built, analyzed, coded or tested in courses, projects and campus roles.

This article covers how to structure and write the résumé itself. For finding and choosing internships, see our guide to STEM internships. If you’re starting from scratch, read how to get a STEM internship with no experience first.

Structure that works for most students

One page is usually enough. A common order:

1. Header. Name, email, phone, city and state, and a link to a portfolio or code repository if you have one.
2. Education. Institution, degree, expected graduation and relevant courses. Include GPA if the posting asks for it or you choose to.
3. Projects. Often the most important section for STEM students.
4. Experience. Jobs, research positions and internships, including non-STEM jobs.
5. Skills. Programming languages, lab techniques, software and tools, grouped sensibly.
6. Activities and leadership, if relevant and space allows.

Some employers use applicant tracking software to manage applications. Simple formatting, such as standard section headings, a clear single-column layout and no text inside images, is easier for both software and people to read.

Writing each entry

A good entry answers three questions: what did you do, how did you do it, and what came of it?

• Start with an action verb: built, analyzed, designed, tested, automated, presented.
• Name the tools you actually used.
• Add a result or scope: the size of the dataset, the number of users, what the work showed or improved.

Weak: “Worked on a group project about water quality.”

Stronger: “Measured pH and turbidity at six river sites over four weeks; analyzed results in R and presented findings to the class.”

The stronger version is specific, shows tools and scope, and could be discussed in an interview.

A fictional sample, annotated

This sample is entirely fictional. It’s not a real person or a real application, and it isn’t a template to copy. Use it to understand structure, then write about your own true experience.

Jordan Rivera (fictional) · jordan.rivera@example.com · Columbus, OH · portfolio.example.com

Education Example State University (fictional), B.S. Mechanical Engineering, expected May 2028 Relevant courses: Statics, Intro to Programming (Python), Materials Lab

Projects Bike-rack load tester (course project, team of 3): designed a test rig from scrap steel; measured deflection under 5 loads; wrote a Python script to plot results. Campus energy dashboard (personal): pulled public building-energy data into a simple web chart; documented the code on GitHub.

Experience Shift lead, campus dining (fictional employer): scheduled 8 student staff each week; trained new hires on safety procedures.

Skills Python (coursework level), SolidWorks (basic), Excel, hand tools and drill press (lab-certified)

Why it works:

• Projects come before experience, because they’re the strongest evidence of engineering skill.
• Each project names tools, scope and the student’s role. “Team of 3” is honest about collaboration.
• The non-STEM job still counts. Scheduling and training show reliability and responsibility.
• Skill levels are stated honestly. “Coursework level” and “basic” set accurate expectations, which interviews will test.

Tailoring for each posting

Read the posting and mark the skills and tasks it emphasizes. Then reorder your projects so the most relevant appear first, and use the posting’s terms where they truthfully describe what you’ve done. Don’t add a skill just because the posting lists it. If you’re learning it now, say so in a cover letter or interview instead.

Common mistakes

• Listing duties instead of results. “Responsible for data entry” says less than what the data was for.
• Overstating skills. Rating yourself “expert” in a tool you’ve used once is easy to expose in a technical question.
• Dense paragraphs. Short bullet points are easier to scan.
• Typos and inconsistent formatting, which suggest carelessness in exactly the kind of detail technical work needs.

A checklist before you submit

• One page, readable at a glance
• Contact details correct, and a professional email address
• Projects described with an action, tools and a result
• Skills and levels honest
• Tailored to this posting
• Proofread, ideally by someone else

The STEM internship résumé template gives you the section structure as a starting point.

A practical next step

Rewrite your two strongest projects using the action, tools and result pattern above. Read each one aloud. If you couldn’t comfortably explain it in an interview, revise it until you could.