Software Engineering Intern Resume Example

A software engineering intern resume is judged on projects, and a project only counts if the reader can open it. Put a GitHub link in the header, write each project as a role with what you built, which language and framework, and one measurable thing it does, and list languages honestly by how much you have shipped in them.

The Sample resume below is for a third-year computer science student in Minneapolis who completed one internship and is recruiting for a second summer. The internship entry reads like a junior engineer's: pull requests merged, tests written, an on-call issue fixed. The hackathon and the teaching assistant role are written as jobs too, because to an engineering manager a working demo built in 36 hours and the ability to explain recursion to 60 first-years are both evidence.

Recruiting for software internships starts in August for the following summer, so this page is built for a fall application. If you are earlier in the degree, the internship example and the computer science example cover a first application with coursework projects only. The software engineer example and the front-end developer example show what the first full-time resume will need to say. The Campus template keeps projects and education on one page without losing the links.

Updated . The person and employers in this Sample resume are fictional.

Software Engineering Intern sample resume

Noah Bergquist

Computer Science Student (BS, May 2027) | Python, TypeScript, Go | GitHub and Project Links in Header

Minneapolis, MNnoah.bergquist@example.com(612) 555-0134

Summary

Third-year computer science student at Twin Cities Polytechnic University (BS expected May 2027, GPA 3.7) seeking a summer 2027 software engineering internship in backend or full-stack work. Completed a twelve-week internship on a payments reconciliation team, shipping 23 merged pull requests to a Go service in production. Teaching assistant for Data Structures, and lead of a four-person hackathon team whose transit app placed second of 41 entries.

Experience

Software Engineering Intern, Mill District Software

–

Minneapolis, MN

  • Merged 23 pull requests to a Go reconciliation service that matches about 2 million card transactions a day, after code review from two senior engineers.
  • Built a retry-with-backoff wrapper for a flaky third-party settlement API that cut the nightly job's failure rate from roughly one in ten runs to zero over the last six weeks of the internship.
  • Wrote 140 unit and integration tests with the team's Go test tooling, raising coverage on the matching package from 61 to 84 percent.
  • Investigated a paging alert during an on-call shadow week and traced it to a timezone bug in a date comparison; the fix shipped the same day with a regression test.
Team Lead, Civic Transit Hackathon Project, Independent project

–

Minneapolis, MN

  • Led a four-person team over 36 hours to build a React and TypeScript web app that predicts bus crowding from public transit feeds, placing second of 41 teams.
  • Owned the data pipeline: a Python service that polls the agency's GTFS-realtime feed every 30 seconds and stores vehicle positions in PostgreSQL.
  • Kept the project live after the event; it has had 600 unique visitors and is linked from the repository README with setup instructions.
Undergraduate Teaching Assistant, Data Structures, Twin Cities Polytechnic University, Department of Computer Science

– Present

Minneapolis, MN

  • Run two weekly lab sections of 30 students each covering linked lists, trees, hashing and graph traversal in Java, and hold four office hours a week.
  • Grade about 60 programming assignments per week against a rubric and wrote 15 new autograder test cases that caught edge cases the old suite missed.
  • Received a 4.7 of 5 average on the department's end-of-semester TA evaluation across two semesters.

Education

Bachelor of Science in Computer Science (expected May 2027)

Twin Cities Polytechnic University, Minneapolis, MN

GPA 3.7. Completed: Data Structures, Algorithms, Operating Systems, Databases, Computer Networks, Software Engineering (team project with weekly sprints). In progress: Distributed Systems, Compilers. Member, Competitive Programming Club.

Skills

  • Python
  • Go
  • TypeScript and JavaScript
  • Java
  • SQL and PostgreSQL
  • React
  • REST API design
  • Git and GitHub pull request workflow
  • Unit and integration testing
  • Docker
  • Linux command line
  • AWS (S3, Lambda, basic IAM)
  • Debugging with logs and profilers

Start yours from this example

Opens this sample in the editor, in one of the templates below. Swap in your details, then tailor it to each posting in about two minutes.

Use this example

Templates for the software engineering intern resume

All templates

How the resume changes with experience

The same software engineering intern resume, written at three levels: a summary and three bullets for each.

Entry level

Zero to two years, or a first role in the title

Second-year computer science student with coursework in Java and Python and two personal projects on GitHub, seeking a first software engineering internship or a summer research position.

  • Built a command-line budgeting tool in Python with SQLite storage and 40 unit tests, used daily by myself and two roommates.
  • Completed Data Structures and an intro web development course, with a final project deployed to a free hosting tier.
  • Chose to open-source the class project and respond to the two issues strangers filed rather than leave it private.

Mid level

Three to seven years, owns a process or a workload

Third-year computer science student with one completed software engineering internship on a production Go service, a hackathon placement and a teaching assistant role, recruiting for a second internship.

  • Shipped 23 merged pull requests and 140 tests to a service processing about 2 million transactions a day.
  • Cut a nightly job's failure rate to zero by wrapping a flaky API call with retries and backoff.
  • Picked a backend team over a more visible mobile team for the internship to learn how production systems are run.

Senior

Eight years or more, leads people, budgets or programs

Graduating computer science student with two software engineering internships and a return offer, deciding between the offer and new-graduate roles at smaller companies.

  • Second internship owned a feature end to end: design document, API, migration, rollout behind a flag to 5 percent of users and then everyone.
  • Reduced p95 latency of an internal search endpoint from 900 to 180 milliseconds by adding an index and caching a hot query.
  • Asked for a backend-leaning new graduate team in the return offer rather than the team with the open headcount, and got it.

Skills to put on the software engineering intern resume

Hard skills

Languages you have shipped in
Recruiters match the list against the posting, and interviewers probe the first one you name, so order them by real use and leave off anything from a single lecture.
Git and pull request workflow
Internship teams run on branches and reviews, and a student who already works that way needs less of a senior engineer's time.
Testing
Test counts and coverage numbers show you think about correctness, which is the trait managers most often say interns lack.
SQL and a database
Nearly every internship project touches stored data, and a schema you designed or a query you tuned is a concrete talking point.
A deployed project
A link that opens and works answers the question of whether you can finish things, which no course grade can.
Data structures and algorithms
Technical screens still test them, and the course plus a competitive programming club line signals you are prepared for that round.
A cloud or container basic
Knowing enough Docker or AWS to run your own project tells the team you will not be blocked by the deployment step.

Soft skills

Writing things down
A README with setup steps, a clear pull request description and a short design note are how interns earn trust on a remote or hybrid team.
Asking a good question
Interns who get stuck quietly for a day cost more than interns who ask after an hour with a summary of what they tried.
Working in a team with a deadline
A hackathon or a sprint-based class project shows you can split work, merge it and demo something on time.
Explaining a technical idea
Teaching assistant and tutoring work proves you can make a hard concept simple, which is what code review and standups require.

Mistakes that cost software engineering intern interviews

  1. Projects without links or results

    Built a web app using React tells the reader nothing. Add the repository link, what the app does, the stack in one line, and one number: users, requests, test count, placement in a competition, or a measured speedup.

  2. A skills section that lists everything you have heard of

    Fifteen languages on a third-year resume invites the interviewer to pick the weakest one. Keep the list to what you could write a small program in today, and group tools separately from languages.

  3. Describing the internship team instead of your work

    Worked on the payments team that processes millions of transactions describes your coworkers. State what you merged, fixed, tested or built, and what changed because of it.

  4. Burying the GitHub link

    Put the profile link in the contact header where a recruiter sees it in the first second, and make sure the pinned repositories are the ones you describe on the page, with READMEs that run.

  5. Leaving out the teaching assistant or tutoring job

    Students drop these as not real engineering. Managers read them as proof you can explain code, review others' work and grade against a rubric, all of which an intern does in review.

  6. Starting the search in the spring

    Large companies post summer internships in August and September and fill many by December. A fall resume with last summer's work on it is the one that gets interviews; a spring resume competes for what is left.

Questions about the software engineering intern resume

How do I write a software engineering intern resume with no internship yet?

Lead with two or three projects written as roles: the problem, the stack, the link and a result. Add relevant courses with the hardest project from each, any teaching or tutoring, and hackathons. A single polished project that runs beats five half-finished repositories.

Should I list my GPA on a software internship resume?

Include it if it is 3.5 or higher, since some large companies filter on it. Below that, leave it off and let the projects and the internship carry the page; most interviewers never ask.

How many programming languages should I list?

Three to six that you could use in an interview without warning, ordered by how much code you have written in each. Frameworks, databases and tools go in their own groups so the reader can see the difference.

Do hackathons count as experience?

Yes, when written with a team size, the duration, the stack, what you personally owned and the outcome. A hackathon entry that is still deployed and linked carries more weight than a placement alone.

Should the resume be one page?

One page for every internship application. If you have two internships, three projects and a TA role, trim the oldest project and the coursework list before you let it spill over. Recruiters at large companies read hundreds a day.

Is it worth putting coursework on the resume?

List the courses an engineer would recognize as substantial: data structures, algorithms, operating systems, databases, distributed systems, compilers. Skip general education and introductory programming once you have anything more advanced.

Related resume examples

All examples

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.