Computer Science Resume Example

A computer science resume is usually a new graduate's first real one, and it is judged on projects and internships rather than job titles. Recruiters screening campus applicants look for languages, one or two substantial projects and any sign you have written code other people used.

The Sample resume below belongs to a computer science graduate with one software internship, a research assistant role and a teaching assistant job. Education sits at the top because it is the strongest credential at this stage, followed by experience written the way working engineers write it: what was built, with what, and what happened next. Coursework is limited to the classes a posting would care about.

Send a version tuned to each role family: backend, data, security or research. Once you have a year or two in industry, the software engineer example shows how the page changes, and the Python developer example shows a language-first version. The Campus template and the student resume builder are both designed for this stage.

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

Computer Science sample resume

Marisol Quintero

Computer Science Graduate, Backend and Systems

Fayetteville, NCmarisol.quintero@example.com(910) 555-0128

Summary

Computer science graduate with a software engineering internship, a year of research programming and two semesters as a teaching assistant for data structures. Built a route-caching feature during my internship that the team shipped to production. Looking for a backend or systems role where I can own small services and learn from careful code review.

Experience

Software Engineering Intern, Brightfield Mapping

–

Durham, NC

  • Built a tile-caching layer in Go for the routing API that cut median response time for repeat map requests from 310 ms to 90 ms; the team shipped it the week after my internship ended.
  • Wrote integration tests for the geocoding service that caught two address-parsing bugs before release.
  • Presented the caching design and its trade-offs to the engineering team in a twenty-minute review.
Undergraduate Research Assistant, Distributed Systems Lab, Sandhill State University

–

Fayetteville, NC

  • Implemented a Raft-based replicated log in Rust for a faculty research project and measured recovery time under simulated node failures.
  • Automated the lab's benchmark runs with Python and GitHub Actions, so results for each commit were ready the next morning.
Teaching Assistant, Data Structures, Sandhill State University

–

Fayetteville, NC

  • Led weekly lab sections for 35 students and held office hours on trees, hashing and graph algorithms.
  • Rewrote the autograder tests for three assignments, reducing regrade requests to a handful per term.

Education

B.S. in Computer Science, minor in Mathematics

Sandhill State University, Fayetteville, NC

Relevant coursework: Operating Systems, Distributed Systems, Databases, Algorithms, Computer Networks

Skills

  • Python
  • Go
  • Rust
  • Java
  • C
  • SQL (PostgreSQL)
  • Git
  • Linux
  • Docker
  • Distributed systems
  • Data structures and algorithms
  • Unit and integration testing

Start yours from this example

Bring your own resume or start blank, then tailor it to each posting in about two minutes.

Use this example

Templates for the computer science resume

All templates

How the resume changes with experience

The same computer science 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

Computer science senior with one internship and a capstone project, looking for a first software role in backend or data engineering.

  • Built a course-scheduling web app with three classmates for a capstone, handling authentication and the database layer.
  • Solved and documented more than 150 algorithm problems, focusing on graphs and dynamic programming.
  • Organized a weekend hackathon for 80 students as vice president of the computing club.

Mid level

Three to seven years, owns a process or a workload

Software developer with a computer science degree and four years of experience building backend services, now moving toward systems and infrastructure work.

  • Own two internal services written in Go, including their deployment and alerting.
  • Cut a nightly data export from three hours to twenty minutes by rewriting its queries and batching writes.
  • Mentor interns each summer and run the team's code review guidelines.

Senior

Eight years or more, leads people, budgets or programs

Senior engineer with a computer science background and ten years of experience designing distributed systems and leading platform teams.

  • Designed the storage layer for a multi-region service that has met its availability target every quarter since launch.
  • Lead a platform team of seven and set its technical roadmap with product and security partners.
  • Chair the architecture review group that approves new services across the engineering organization.

Skills to put on the computer science resume

Hard skills

Data structures and algorithms
New-grad interviews test these directly, and naming courses or projects that used them prepares the ground for that round.
One or two languages in depth
Recruiters believe depth more than a long list, so lead with the languages you could code in live.
Git and collaborative development
Internship and team project experience with pull requests shows you can join a codebase without hand-holding.
Databases and SQL
Most entry-level backend work touches a database, and a project with a real schema stands out from coursework alone.
Testing
Graduates who write tests without being asked are rare, and a tested project signals professional habits.
Linux and the command line
Comfort in a terminal is assumed on most engineering teams, and systems roles ask for it by name.

Soft skills

Explaining technical ideas
Teaching assistant and presentation experience shows you can explain a design, which every interview loop tests.
Asking for and using feedback
Managers hiring graduates care most about how fast you learn, and code review stories are the best evidence.
Working on a team project
Almost all professional software is built in teams, so a group project with a clear role for you is worth a bullet.

Mistakes that cost computer science interviews

  1. A transcript instead of a resume

    Listing every course buries the work that proves skill. Keep four or five relevant courses on one line and spend the space on projects and internships.

  2. Projects with no outcome

    Built a to-do app in React tells the reader nothing new. Say what was hard about it, who used it or what you measured, and link to the code.

  3. Skill ratings and progress bars

    Four stars in Java means nothing to a recruiter and confuses tracking systems. List skills plainly and let the bullets show them in use.

  4. Burying the internship

    Professional experience, even twelve weeks of it, is your strongest line. Put it directly after education with the same care you would give a full-time job.

  5. An objective about what you want

    Seeking a challenging position to grow my skills is about you. Use the summary to say what you can already do and which kind of role you are applying for.

Questions about the computer science resume

Should I put my GPA on a computer science resume?

Include it if it is strong or if the employer asks for it, usually a 3.0 or higher. Drop it after your first full-time job.

How many projects should a computer science student list?

Two to four, chosen for the role. One substantial project described well beats six small ones listed in a row.

Do teaching assistant and research jobs count as experience?

Yes. Describe them like any job, with what you built or improved, and they show communication and technical depth at the same time.

Should a computer science resume be one page?

Yes, for students and new graduates. Recruiters screening campus applicants spend very little time on each page, so keep the strongest lines in the top half.

How do I tailor a computer science resume for different jobs?

Keep one master version, then reorder projects and skills for each role: systems work first for infrastructure roles, data projects first for analytics roles.

Related resume examples

All examples

Every application goes out fitting the job.

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

Tailor your resume — free

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