Computer Science Internship resume examples by experience level

Entry-level Mid-career Senior-level

Use this example

A computer science internship resume is a one page document built from three things that are not a job history: coursework with an artifact attached, one project with a real decision in it, and whatever job you already have, written for what transfers.

Most students write this page as an apology. They open with an objective explaining what they hope to learn, list six courses by catalog number, name four projects in one line each, and hide the campus dining job at the bottom in a smaller font. Every one of those instincts is backwards, and fixing them takes an afternoon.

Resume guide for a computer science internship resume

This guide and the corresponding computer science internship resume example will cover:

• How to write a computer science internship resume, section by section
• The three things that go on the page instead of a job history
• Three adaptable summaries: first internship, returning intern and new graduate
• What the published survey data says about how interns actually get hired
• What this work pays as an internship and what it pays afterward

How to write a computer science internship resume

Five sections: contact header, a two-line summary, projects, education with coursework, and experience. One page, and one page is not a limitation here. It is the correct length, and a recruiter who sees two pages from a second-year student reads it as a judgment problem before they read a word.

The order is unusual on purpose. Projects sit above education because a project is evidence and a transcript is a claim. Experience sits at the bottom because it is the section a reader reaches already convinced or already gone.

Run the finished file through the ATS resume checker before you apply. Internship programs at larger employers receive applications in volume and parse them into a structured record first.

Choosing the best resume format for a computer science internship resume

Reverse chronological, single column, one page, with projects promoted above education. This is not a functional resume and it is not a skills-first template, whatever a student resume builder suggests.

Reviewers for internships read for trajectory. They want to see that you were doing something last summer, that you are doing something this semester, and that it has been getting harder. A format that flattens the dates removes the only story a two-year career has.

Include your contact information

Two things in that right column do most of the work: the expected graduation date, because internship eligibility is often written in terms of it, and the profile link, because it is the only line on a student resume a reviewer can verify in ten seconds. Also check the email address. Nobody will mention it, and it will still cost you.

Make use of a summary

Two lines, not four, and no objective. Say what you are, what you have built, and what you are looking for, in that order.

Second-year computer science student at The Ohio State University, comfortable in Java and Python, looking for a summer software engineering internship. Built a course scheduling tool in Java that 140 students in my residence hall used during registration week, and currently work 15 hours a week on the university technology service desk, closing about 45 tickets a week across 3 operating systems.

Third-year computer science student at The Ohio State University with one completed software engineering internship, seeking a second summer placement in backend or platform work. At Deer Creek Software I shipped 14 merged pull requests to a production Django service, including a caching change that cut a report endpoint from 3.4 seconds to 380 milliseconds. Strongest in Python and Java, currently learning Go on a personal project.

Computer science graduate from The Ohio State University, May 2026, with two completed software engineering internships and a returning offer from the second. Built and shipped an ingestion service in Python at Granville Health Analytics that handled 2.1 million records a day, and wrote the retry design after an outage in my first week there. Looking for a backend or platform engineering role with production ownership.

Right vs wrong: the same computer science internship summary, twice

The right column has two numbers a student can actually produce and one thing a reader can open. The left is what almost every file in the stack says, which is why almost every file in the stack is skimmed in four seconds.

Outline your experience without a job history

You have experience. It is not the experience you think they want, and writing it as though you are ashamed of it is the mistake.

Technology Service Desk Assistant, The Ohio State University, Columbus, OH, January 2024 to Present
Close about 45 tickets a week across Windows, macOS and Linux, covering account access, network configuration and device encryption for staff and students.
Wrote 11 knowledge base articles for recurring issues; the two on virtual private network setup cut repeat tickets on that topic by about a third over a semester.
Cover the Saturday morning shift alone, which is the only shift with no escalation path available on site.
Shift Lead, Grandview Provisions, Columbus, OH, June 2022 to December 2023
Opened the store five mornings a week at 5am for 18 months with no missed shifts, and trained 6 new staff on the register and stock systems.

That last entry does more than it looks. It answers the question a reviewer cannot ask directly: whether you turn up, whether you can be left alone with something, and whether anyone has trusted you. A student who has opened a store alone at 5am for 18 months has a stronger answer than one who has not, and it has nothing to do with programming.

The three things a computer science internship resume has instead of a job history

Everything on this page reduces to three substitutes. Get all three right and the missing job history stops being noticeable.

Coursework with an artifact attached. Do not list six courses. Name three or four and attach what came out of each. "Systems Programming: wrote a shell in C supporting pipes, redirection and job control, 2,100 lines." A course name is a claim about attendance; a course plus an artifact is a claim about capability, and the artifact is the part a reader can check.

One project with a decision in it. The most common error on these resumes is describing a project by what it does. A reviewer does not care what your app does; there are ten thousand student projects and most do similar things. They care whether you made a choice.

Course Scheduling Tool, Java and SQLite, 2024. github.com/example
Built for the registration week problem in my residence hall: 140 students used it to find non-conflicting section combinations across their shortlisted courses.
Chose a constraint solver over brute force after the naive version took 40 seconds on a realistic 8-course shortlist; the solver version returns in under 300 milliseconds.
Kept it on SQLite rather than adding a server, because nobody was going to run a database for a two-week tool, and the whole thing had to be a single file students could download.
Known limitation: no support for variable-credit courses, which broke it for about 6 percent of the shortlists students tried.

Three of those four lines are decisions and the fourth is an admitted limitation. The limitation is worth writing: a student who states what their project does not handle is saying they tested it against reality, which is a stronger signal than anything in a feature list.

The job you already have. Write it fully, with numbers, in the same format as any other job: volume, duration, responsibility, and anything you were trusted with alone. If it is technical, say what you supported and how much. If it is not, do not translate it into technical language, which reads badly. Write it accurately and let it work.

Build a snapshot of your key skills

Short, grouped, honest, no rating bars. Eight to twelve entries is plenty, and a longer list makes the page less believable rather than more.

Languages used regularly: Java, Python, SQL
Languages used in coursework: C, JavaScript, Go
Tools: Git and GitHub, Linux command line, Docker for one project, PostgreSQL and SQLite, pytest and JUnit
Coursework strengths: data structures and algorithms, databases, systems programming, software engineering

The two-tier split between languages you use regularly and languages you met in a course is the most useful line on the page, and almost nobody writes it. It costs nothing, since the second tier still carries every keyword. What it buys is the assumption that the first tier is literal, which is what you want a technical interviewer to assume before they open a shared editor with you.

List your education and coursework

Degree, institution, expected graduation date, and three or four courses with artifacts. Include your GPA if it is 3.5 or above and leave it out otherwise.

Bachelor of Science, Computer Science, The Ohio State University, Columbus, OH. Expected May 2026. GPA 3.62.
Relevant coursework with artifacts: Systems Programming (wrote a shell in C supporting pipes, redirection and job control, 2,100 lines); Databases (implemented a B-tree index for the course engine, 1.8 million lookups a second); Software Engineering (three-person team project, 9,000 lines, owned the merge policy and review rota); Algorithms.
Undergraduate grader, Data Structures, autumn 2024 and spring 2025: graded 60 submissions a week and held a weekly office hour.

The grader line belongs in education rather than experience, and it is worth having. Departments give grading work to students they trust with other students' code, which is a small endorsement but a real one, and any reviewer who went through a computer science department will read it that way.

Choose the right layout and design

Single column, 10 or 11 point type, one page, PDF, no photograph, no skill percentage bars, no icons. Name the file for yourself and the role.

Skill rating bars deserve a specific warning here. "Python 80 percent" invites the reader to work out what the other 20 percent is, and the honest answer at this stage is usually most of it. The two-tier list says the same thing without inviting the question.

Computer science internship job market and outlook

The Bureau of Labor Statistics publishes no Occupational Outlook Handbook profile for a computer science internship, because an internship is a stage in a career rather than an occupation, and the Handbook classifies by the work done.

The occupation you are applying into is software developers, quality assurance analysts, and testers, and one line in its Quick Facts table is worth reading carefully.

Source: U.S. Bureau of Labor Statistics, Occupational Outlook Handbook, May 2025 wage data and 2025 to 2035 projections, published 27 August 2026.

The line that matters is the third from the bottom. For entry into this occupation the Handbook lists no related work experience and no on-the-job training. The internship is not a formal requirement for the job you are eventually applying for; it is a market convention, and the survey data explains why employers keep it.

What salary you can expect from a computer science internship

There is no Handbook wage figure for a computer science intern, because BLS does not publish pay for a training stage, so any number attached to this title comes from an employer survey rather than federal wage data. Two published figures are worth knowing, and they answer different questions.

For the internship itself, the National Association of Colleges and Employers reported an average intern hourly wage of $23.35 in its 2026 Internship and Co-op Report, drawn from 284 U.S. employers surveyed in March 2026. That figure covers all disciplines rather than computer science alone.

For what the internship is actually buying, look at the occupation. Software developers, quality assurance analysts, and testers had a combined median annual wage of $134,040 in May 2025. Split by title, software developers earned a median of $135,980, with the lowest 10 percent under $82,460, while software quality assurance analysts and testers earned $104,300, with the lowest 10 percent under $61,440 (BLS, May 2025).

That $31,680 gap between the two sub-titles is the most useful thing here for a student choosing between offers. An internship on feature development and one on test automation are both good internships, and they point at occupations with medians more than $30,000 apart. Neither is the wrong choice, but it is worth knowing which door you are walking through, and it is a fair question to ask in an interview.

Key takeaways for a computer science internship resume

1. One page, projects above education, no objective statement.
2. Attach an artifact to every claim; cut any line without one.
3. Write one project by its decisions and admit a limitation.
4. Name three or four courses with what you built in each.
5. Write your current job fully, including a non-technical one.
6. Split the languages you use from the languages you have met.
7. Put your expected graduation date in the header; eligibility depends on it.

Build your computer science internship resume in 15 minutes with our AI resume builder.

Related information technology resume examples

• Computer science resume
• Entry-level software engineer resume
• Software developer resume
• Software engineer resume
• QA tester resume
• Python developer resume
• Java developer resume
• Front-end developer resume
• Web developer resume
• Data analyst resume
• IT help desk resume
• Automation tester resume

Pair it with a matching computer science internship cover letter.