Computer Science Resume for Students and New Grads

A computer science resume for a student or a new grad has a problem a working engineer never faces: the Experience section is thin or empty. The fix is to move the evidence you do have (projects, coursework, hackathons, open-source contributions, internships) into the spots a recruiter reads first, and to write each item so it proves a skill rather than naming a title.

This guide covers internship applications, new-grad roles, and what India calls fresher roles. It includes a one-page template and a fictional example. If you have three or more years of professional experience, the software engineer resume guide has the template and examples for you.

What to put on a computer science resume with no work experience

The companies you are applying to have said what they want. Google’s hiring page tells candidates who are recent graduates or have limited work experience to “include school-related projects or coursework that demonstrate relevant skills and knowledge” (Google Careers, How we hire). The same page asks every applicant to be specific about projects, their outcomes, and how they measured success. Projects are the Experience section for a student, and you write them the same way an engineer writes a job.

Order the page by strength of evidence:

1. Education, because it is the one qualification the posting requires and the first thing a campus recruiter checks.
2. Projects, because they show you can build something that runs.
3. Experience, which for a student means internships, research assistant work, teaching assistant work and part-time jobs.
4. Skills, grouped and honest.
5. Activities and awards: hackathons, competitive programming, clubs, scholarships.

Each kind of evidence answers a different doubt. Coursework covers the fundamentals, and a project shows you can finish. A hackathon shows you can ship under time pressure with people you did not pick. An open-source contribution shows you can read someone else’s code and get a change merged, and an internship shows you can work inside a company. A resume with two or three of these covers more ground than a resume with ten tutorial projects.

Computer science resume template (one page)

Copy this and replace each bracket. Keep it to one page without exception; a student resume that runs to two pages tells the reader you could not decide what mattered.

# [Full Name]
[City, Country] · [email] · [phone] · github.com/[username] · linkedin.com/in/[username]

## Education
[Degree, e.g. B.Tech in Computer Science], [University], [City]
[Expected] [Month Year] · [CGPA or GPA, if 8/10 or 3.5/4 or above]
Relevant coursework: [Data Structures, Algorithms, Operating Systems,
Databases, Computer Networks, Machine Learning: pick 5 to 8 that match
the posting]

## Projects
### [Project name], [stack in three words], github.com/[username]/[repo]
- [What it does and who used it, with a number if you have one.]
- [The hardest technical part you built, and what it achieved.]

### [Project name], [stack], [link]
- [Two bullets, same shape.]

### [Project name], [stack], [link]
- [One or two bullets.]

## Experience
### [Role, e.g. Software Engineering Intern], [Company], [City]
[Mon YYYY] to [Mon YYYY]
- [What you built, what it changed, which tools you used.]
- [Second bullet.]

### [Teaching Assistant / Research Assistant / Part-time role], [Organisation]
[Mon YYYY] to [Mon YYYY]
- [One bullet.]

## Skills
Languages: [the ones you can solve interview problems in]
Frameworks and libraries: [...]
Tools: [Git, Docker, Linux, a cloud provider, a database]

## Activities and awards
- [Hackathon name, Year: placement out of N teams, what you built]
- [Open-source contribution: project, what you changed, link to the PR]
- [Scholarship, dean's list, competitive programming rating]

Three rules for filling it in. Education goes first until you have a full-time job. Every project needs a link that works. The Skills list only holds things you could use in an interview this week.

Computer science resume example (fictional): new grad

The candidate below is invented. The university, the companies and every number are fictional, chosen to show what a complete one-page computer science resume looks like in the final year.

ANANYA DESHMUKH
Pune, India · ananya.deshmukh@example.com · +91 98XXX XXXXX
github.com/ananyad-dev · linkedin.com/in/ananyad-dev

EDUCATION
B.Tech in Computer Science and Engineering
Meridian Institute of Technology, Pune
Expected May 2027 · CGPA 8.6/10
Relevant coursework: Data Structures and Algorithms, Operating Systems,
Database Systems, Computer Networks, Distributed Systems, Machine Learning

PROJECTS
Shelfwise, Flask + PostgreSQL + React, github.com/ananyad-dev/shelfwise
- Library seat-booking app used by 1,200 students during two exam
  seasons; replaced a paper sign-up sheet at the campus library.
- Built the booking engine with row-level locks to stop double bookings
  under concurrent requests; load-tested to 200 requests a second with
  Locust.

tinygrep, Rust, github.com/ananyad-dev/tinygrep
- Command-line search tool implementing Boyer-Moore and parallel file
  walking; runs 3x faster than naive grep on a 2 GB test corpus.
- 140 GitHub stars; packaged for Homebrew and crates.io.

Campus Bus Tracker, Kotlin + Firebase, github.com/ananyad-dev/bustracker
- Android app showing live positions of 6 campus shuttles from driver
  phones; 800 installs through the student union.

EXPERIENCE
Software Engineering Intern, Halden Logistics, Pune
May 2025 to Jul 2025
- Built an internal dashboard in React and FastAPI that replaced a weekly
  Excel report on late deliveries; the operations team of 14 now checks
  it daily.
- Wrote 60 integration tests for the shipment API with pytest, raising
  coverage on that module from 40% to 85%.

Teaching Assistant, Data Structures, Meridian Institute of Technology
Aug 2025 to Dec 2025
- Ran weekly lab sessions for 45 second-year students and graded
  assignments on linked lists, trees and graphs.

SKILLS
Languages: Python, Rust, Java, SQL, JavaScript
Frameworks and libraries: Flask, FastAPI, React, pytest
Tools: Git, Docker, Linux, PostgreSQL, Firebase, AWS (EC2, S3)

ACTIVITIES AND AWARDS
- HackMeridian 2025: 2nd of 48 teams; built a 36-hour prototype that
  matches hostel students with shared cab rides.
- Open source: merged a fix to an open-source Python HTTP client that
  corrected timeout handling on retried requests (PR linked on GitHub
  profile).
- Dean's list, 2024 and 2025.

Read the projects section again and notice that each project has a user count, a scale, or a comparison. “Used by 1,200 students” and “3x faster on a 2 GB corpus” are the student equivalents of a working engineer’s “cut latency by 60%”. The internship bullets describe a thing that still exists after the intern left. The open-source line names the project and the change, so a recruiter can click through and verify it.

How to write each section when you have no experience

Education

Degree, university, expected graduation month, and your CGPA or GPA if it helps you. The Tech Interview Handbook suggests listing a GPA only above 3.5 on a 4-point scale; a comparable bar on a 10-point CGPA scale is about 8. Below that, leave it off and let the projects speak. Add a “Relevant coursework” line with five to eight courses that match the posting. A backend internship wants Databases, Operating Systems and Networks; a machine learning role wants Linear Algebra, Probability and ML. Swap the list for each application.

Leave high school off after your first year of university unless you are applying for a first-year internship and have nothing else.

Projects: your experience section

Pick two to four projects and give each one or two bullets. A strong project bullet has the same shape as a work bullet: what you built, what it changed or who used it, and the technical method. “Built a chat app in Node.js” is a title. “Built a chat app in Node.js with Socket.IO that 90 classmates used for a semester; added message persistence in Redis after the first outage” is evidence.

Course projects count if you describe your part and the project did something. Group projects count if you name what you built. Tutorial clones do not count; a recruiter has seen the same Netflix clone many times before. If you only have tutorial projects, extend one until it does something the tutorial did not, then write about the extension.

Every project needs a public link with a README that says what it does and how to run it. A recruiter who clicks through to a repo with one commit named “initial” learns that the project is a placeholder.

Internships, research and part-time work

List every internship, including the one where you fixed CSS for ten weeks. Write two bullets: what you built, and what it changed for the team. Numbers come from the team you worked with; ask your mentor before you leave for the figures you can quote.

Research assistant work goes here too, with the lab, the professor’s area and your technical contribution. Teaching assistant work shows you can explain things and manage a room. A part-time job outside tech gets one line if you have space, and none if you do not.

Hackathons and open-source contributions

A hackathon line needs the event, the year, your placement if you placed, and what the team built in a short phrase. An open-source line needs the project name, what your change did, and a link. One merged pull request to a project people recognise outranks five hackathons with no result.

If you have not contributed yet, pick a library you use, find an issue labelled “good first issue”, and fix it. The pull request takes a weekend and gives you a bullet with a verifiable link.

Skills

List languages first, then frameworks, then tools. Include only what you could use in an interview this week. Skip proficiency bars, percentages and “beginner / intermediate / advanced” labels; interviewers decide your level by asking questions, and a self-rating invites the hard ones.

Match the spelling in the posting. If the role says “PostgreSQL”, write “PostgreSQL”. Our resume keywords guide shows how to pull the right terms from a posting without padding the list.

What to leave off

An objective statement, because the posting already knows your objective. A list of soft skills, because a project bullet proves teamwork better than the word “teamwork”. A photo, for applications in the US, UK and Canada. “References available on request”. A long “Hobbies” section; one line is fine if it says something specific.

Internship resume, new grad resume and fresher resume

The three differ in how much the Experience section carries.

Internship resume (first or second year). You may have no internships yet. Coursework and projects do the work, and a course project with a clear description beats an empty Experience section. Aim for two projects and one activity, and keep the page to a comfortable two-thirds full rather than padding.

New grad resume (final year, or graduated within the last year). Internships move up, right after Education, and projects follow. If you had two internships, one of them might outrank your best project; put the stronger evidence first.

Fresher resume. In India, the word covers the same final-year and recent-graduate applicants. The structure is identical. Campus placement portals and some companies ask for a specific format; follow the form you are given, but keep the one-page version for applications you send yourself, and keep the content the same between the two.

One rule covers all three: one page, education at the top, every project linked.

Mistakes students make on a computer science resume

A two-page resume at graduation. Cut to one page by removing the weakest project and the hobbies section before touching the font size.

Projects without links or numbers. “Built a weather app” tells the reader nothing. A link lets her look; a number tells her it worked.

A skills list longer than the projects section. Fourteen languages and two projects reads as a list of lecture titles. Three languages with evidence beats fourteen without.

Coursework as the main event. A list of twenty courses is a transcript, and the recruiter can request that. Pick the courses that match the posting and move on.

No months on dates. “2025” on an internship reads as either three weeks or a full year. Write “May 2025 to Jul 2025”.

Hiding the GitHub link. Put it on the contact line as plain text, and make sure the profile has pinned repositories with READMEs.

One resume for every posting. A backend internship and a data science internship ask for different courses, projects and skills. The master stays the same; the one-page cut changes.

Tailor the computer science resume for each posting

Keep a master document with every project, course, hackathon and job you have, then cut a one-page version for each application that leads with the evidence that posting asks for. The six-step method, with a worked engineering example, is in our guide to tailoring your resume to a job description.

If you apply to many roles, Resume Matcher, the free open-source tool I maintain, does the cut for you. You run it on your own laptop, connect an AI model, and it rewrites your bullets in the posting’s wording while code checks keep your university, dates and project names unchanged. For a student budget, a free local model through Ollama costs nothing per request, with the caveat that small local models can struggle with the structured edits; a low-cost cloud model is the alternative. It exports a text-based PDF from one of seven templates, and over 200,000 job seekers have used it.

If this helped

The first resume is the hardest one you will write, because you are proving you can do a job you have not had yet. If this guide or the tool helped, a star on Resume Matcher on GitHub helps other students find it, and you can follow me, Saurabh Rai, on GitHub, X and LinkedIn.