Software engineer new grad resume example
A new grad software engineer resume has one job: show that you have built working software and can explain what you built. Projects and internships carry that proof, so they get the most space. Coursework and skills support it.
What this resume has to prove
The Bureau of Labor Statistics says software developers "design computer applications or programs", and that they typically need a bachelor's degree in computer and information technology or a related field, such as engineering or mathematics. It also notes that students can gain experience through an internship while in college.
So a hiring team reading a new grad resume looks for three things: code you wrote that does something, evidence you can work in a shared codebase, and a degree or path that fits. Everything else is supporting detail.
Sample resume
Sample resume (fictional)
B.S. Computer Science, Marlow State University · May 2026
GPA 3.5 · Coursework: Data Structures, Operating Systems, Databases, Software Engineering
Software Engineering Intern, Quillmark Logistics · Columbus, OH · June to August 2025
- Built a Python script that checks daily shipment files for missing fields and emails the operations team a summary
- Added unit tests to an internal Flask service and fixed the three failures they exposed
- Fixed 12 bugs from the team backlog, each shipped through code review
Teaching Assistant, Data Structures, Marlow State University · January 2025 to May 2026
- Hold two office-hour sessions a week for a class of about 120 students
- Wrote the test cases used to grade three programming assignments
CourseSlot, class scheduling web app · Software Engineering capstone, team of 4
- Built the REST API in Node.js and Express and designed the PostgreSQL schema for courses, sections and saved schedules
- Wrote the check that flags overlapping class times before a student saves a schedule
- Demoed the app to the department; 30 classmates used it during spring registration
tinyshell, a Unix shell in C · Operating Systems course
- Implemented pipes, input and output redirection and background jobs; passed all 48 course test cases
Languages: Python, Java, JavaScript, C, SQL
Frameworks and tools: React, Node.js, Express, Flask, PostgreSQL, Git, Linux, pytest
Notice the order. Education comes first because it is short and expected, then Experience because the internship is relevant, then Projects. With no internship, move Projects above Experience.
What to put in each section
Projects: what it does, what you built, what it runs on
Name each project, say in a few words what it does, and say whether it was solo or a team. Then write bullets about your part. Team projects are fine, as long as it is clear which piece was yours, because the interviewer will ask.
Experience: internships, TA work and other jobs
An internship bullet should name the change you made and who it helped. Teaching assistant work counts too: it shows you can read other people's code and explain problems clearly, and BLS lists communication among the important qualities for developers. A non-technical part-time job can stay as a single line.
Weak bullets, rewritten
Education
Degree, school and graduation month. Add your GPA if it helps you. List four or five courses that match the job, not your whole transcript.
Skills to list
Keep skills as plain text, grouped by type. Then mirror the job post: if it says "PostgreSQL" and you have used PostgreSQL, write PostgreSQL, not "SQL databases". The University of Maryland career center also suggests mirroring the job description's keywords. Only list what you could use in a technical interview tomorrow.
Tools
- Languages: Python, Java, JavaScript or TypeScript, C or C++, SQL
- Frameworks: React, Node.js, Spring, Flask or Django
- Tools: Git, the Linux command line, Docker, a cloud platform if you have deployed to one
- Testing: pytest, JUnit or Jest
Abilities
- Reading and changing an existing codebase
- Debugging and writing tests
- Code review, giving and receiving it
- Explaining technical choices to people who don't code
Common mistakes
- A wall of languages. Twelve languages from a week each makes the reader doubt all of them. List the ones you have written real programs in.
- Tech names with no outcome. "React, Node, MongoDB" is a stack, not a bullet. Say what the software does and what you built.
- No links. Put a GitHub or portfolio link in the contact line, and give the repositories it points to a short README.
- Claiming the whole team project. "Built a scheduling app" invites questions you can't answer if you only wrote the front end. Name your part.
FAQ
Should I include hackathons?
Yes, as a project, if you built something that runs. Say what it did and what your part was. A hackathon where nothing shipped belongs in activities, if anywhere.
Do I need a summary at the top?
Not usually. For a new grad engineer, the projects say more than a summary can. If you add one, keep it to two lines. See Resume objective or summary?
How long should it be?
One page. If you need to cut, drop the oldest non-technical job before you cut a project.
Check your resume free
Upload or paste your resume and see what to fix, in under a minute. Add a job post to see what's missing for that job. No sign-up.
Check my resumeMore resume examples
- Entry-level data analyst resume exampleBuilt around analysis projects, with bullets that show the question, the method and the finding.
- Entry-level UX designer resume exampleA plain, one-column resume that points to case studies: research, usability testing and an internship.
- Entry-level business analyst resume exampleRequirements, process mapping and stakeholder interviews, drawn from an internship, a help desk job and class work.
See all resume examples.