Software Engineering Intern Resume Template

Free software engineering intern resume template for Word and Google Docs. Education and a Projects block come before experience, with a link slot per project.

Free, no signup. Want it filled in first? Download the software engineering intern example as Word.

What is in the file

[Your Name]

[Computer Science or your major] · [BS or MS expected Mon YYYY] · [github.com/yourname] · [City or open to relocate]

[City, State] · [email@example.com] · [(555) 555-0100] · [LinkedIn or portfolio URL]

Summary

[(Year) student at (school) looking for a (season YYYY) software engineering internship in (backend, front-end, mobile, ML or infrastructure). Strongest in (one or two languages), shown by (your best project or past internship, with one number).]

Education

[B.S. in Computer Science], [University], [City, State] · [Expected Mon YYYY] · [GPA if 3.5 or higher]

[Relevant courses: (Data Structures, Operating Systems, Databases, Distributed Systems, the ones the posting's work uses)]

Projects

[Project name] · [Language, framework, database] · [link to repo or live demo] · [What it does, who used it, and one number: users, requests, rows, test count, speed]

[Project name] · [Stack] · [link] · [Your part if it was a team or hackathon project, and how it placed or what it shipped]

[Class or research project] · [Stack] · [link if public] · [The hardest technical problem you solved in it]

Experience

[Software Engineering Intern, Research Assistant or Teaching Assistant], [Company, lab or department]

[City, State or Remote] · [Mon YYYY] – [Mon YYYY]

  • [Merged (N) pull requests to (service, app or library) written in (language), reviewed by (who)]
  • [Built or fixed (feature, test suite, script, bug) that (saved time, cut failures, raised coverage) from (before) to (after)]
  • [Something only interns who were trusted get: (on-call shadowing, a design doc, a demo to the team, a feature that shipped)]

[Any other job: tutor, IT help desk, campus web team, retail], [Where]

[City, State] · [Mon YYYY] – [Mon YYYY]

  • [The part of the job that involved code, automation, data or explaining technical ideas, with a number]
  • [A sign of responsibility: (rehired, promoted, trained others, ran a lab section)]
  • [Optional third line if the job taught something the posting names]

Skills

  • Languages: [Python, Java, C++, TypeScript: ordered by how much code you have shipped in each]
  • Frameworks and databases: [React, Flask or FastAPI, Spring, PostgreSQL, MongoDB]
  • Tools: [Git, Linux, Docker, a cloud provider, testing frameworks, CI]

An internship screen starts with eligibility: which degree, which school, and when you graduate. That is why this template puts Education directly under a two-line summary, with the expected graduation month in the first line of it. A recruiter sorting hundreds of applications for one summer cohort can confirm your class year without hunting for it.

Projects come next, ahead of Experience, because most students have written more code for themselves and for classes than for an employer. Each project slot asks for a link, the stack, what you built personally and one figure another engineer could verify. Experience follows for internships, research positions, TA appointments and any job in which you wrote code or automated a task. Skills close the page as short labeled lines, which is where a reviewer double-checks the stack after reading the projects.

Once you have finished an internship, move Experience above Projects; reviewers trust code that passed a real team's review. The page is a single column with standard headings and fits on one sheet, which is what intern programs expect. Bracketed text marks every spot to replace. For a filled-in page from a third-year student recruiting for a second summer, read the software engineering intern resume example.

Updated .

How to fill in each section

  1. Summary: class year, track, best evidence

    Two sentences are enough for a student. The first gives your year, school, the internship season and the track you are aiming at, so a recruiter routes you to the right team. The second points to the single strongest thing below it: a past internship, a project people actually use, or a competitive result. Skip career goals and personality words; interviewers ask about those in person.

  2. Education: graduation month first

    Intern programs hire by graduating class, so the expected month and year belong on the same line as the degree. Add your GPA when it is strong and leave it off when it is not; nobody marks you down for its absence. A second line of four to six courses helps when you have few projects, and helps most when the courses match the role: databases for a backend team, graphics for a game studio, statistics for machine learning.

  3. Projects: links, stack, your part, a number

    Treat this block as your work history if you have not had an internship yet. Each line needs a repository or demo a reviewer can open in one click, the languages and tools, and a fact that can be checked: daily users, a dataset size, a test count, a response time. On team or hackathon work, say which part you wrote. Three strong projects beat six thin ones; keep the ones closest to the posting's stack.

  4. Experience: code that went through review

    A previous internship is the most persuasive entry on a student resume because someone else reviewed and shipped your work. Describe it in pull requests, tests, fixes and features rather than the company's mission. Research assistant and teaching assistant roles belong here too, written with the same specifics: the code you wrote for the lab, or the number of students you helped debug each week. Non-technical jobs earn one entry if they show responsibility.

  5. Skills: three short lines you can defend

    Group languages, frameworks and tools on separate lines and order each by real use, since interviewers often start with the first item. Only list something you could write in a live coding round. A language from one course assignment can wait until you have built something in it. Match the posting's spelling of names you genuinely know, so a keyword search finds them.

Next steps

See it filled in

The software engineering intern resume example uses this structure with a realistic candidate, with versions for entry, mid and senior level.

Read the software engineering intern resume example

Or build it online

Start from the same content in the Campus design, tailor it to a posting and export a PDF. Free to start.

Open it in Resume Master

Questions about the software engineering intern resume template

Should a software engineering intern resume have a summary?

A short one helps when you are applying to several tracks, because it tells the recruiter which team to send you to. Keep it to two sentences, and drop it if the page runs over one side; the education line and the projects already say most of what a summary would.

How many projects should an intern resume list?

Two to four. Choose the ones with working links and a clear part you built, and favor projects that match the posting's language and kind of work. If a project only follows a tutorial, replace it with anything you designed yourself, even if it is smaller.

Where does a hackathon or coding competition go?

Put a hackathon build in Projects with its link, your role on the team and the placing. A competitive programming rating or a contest result fits as a line under Education or at the end of Skills. Either way, give the number: the rank, the rating or the size of the field.

Can I use this template for a data science or IT internship?

Yes. Keep the same order and change what the project lines ask for: datasets, models and evaluation scores for data science, or tickets, scripts and systems supported for IT. The data analyst resume template shows how an analytics page groups tools, and the internship resume example covers a first application from earlier in a degree.

Is it free?

Yes. The Word files and the Google Docs copy are free to download, edit and use for any application. There is no signup and no email.

Will it read correctly in an applicant tracking system?

The layout is one column with standard headings and real text: no tables, text boxes, icons, columns or images, which are the parts parsers most often misread. Keep it that way as you edit.

Word or Google Docs?

Use whichever you edit in. The Word file opens in Microsoft Word, Pages and LibreOffice. The Google Docs link asks you to make a copy in your own Drive; the original stays blank for the next person. Send the posting the format it asks for, usually .docx or PDF.

Every application goes out fitting the job.

Paste a posting, get a resume written for it in two minutes.

Tailor your resume — free

Free to start. No card. Same price on web, iOS and Android.