Students & Career Changers · Entry-Level (0–2 yrs)

Computer Science Entry-Level / New Graduate Resume

This new graduate sample pairs a computer science degree and internship work with an early-career software engineer role. A strong resume for this job connects coding skills to shipped features, tested changes, and the tools used to build and maintain software.

Resume check

What recruiters and tracking systems look for. A guide, not a prediction.

100 / 100Complete

100%
  • Contact20 / 20
  • Summary20 / 20
  • Experience30 / 30
  • Skills20 / 20
  • Education10 / 10

Contact details

Put these at the top; recruiters and tracking systems look for them first.

Optional. In the US, UK and Canada resumes usually have no photo.

45 words

One job per paragraph; start each achievement on a new line with “-”.

10 skills

Separate skills with commas, for example: Excel, SQL, project planning.

More sections

Projects, certifications, languages or anything else that supports your application.

Selected projects
Tools

Alex Morgan

Entry-Level Software Engineer

  • alex.morgan@example.com
  • +1 555 0100
  • Denver, CO

Summary

Early-career software engineer with about one year of combined internship and full-time experience in B2B SaaS. Builds Java and Python services, writes SQL queries, and tests REST APIs. Experienced with code reviews, Git-based workflows, and shipping small product improvements with clear documentation.

Experience

Software Engineer I at Juniper Arc Software, Denver, CO (2026 – Present) - Built Java endpoints for subscription settings and added input validation, reducing support tickets about failed updates from 14 to 9 per month. - Wrote Python scripts to reconcile test data across staging environments, cutting manual setup by about 2 hours per release. - Added unit and API tests to the CI pipeline and fixed flaky cases, reducing reruns from 6 to 3 per sprint. Software Engineering Intern at Mesa Lantern Systems, Boulder, CO (2025 – 2025) - Implemented React components for an internal account dashboard using existing design patterns, helping staff review 40–50 customer records per day. - Added SQL queries and documented test steps for a reporting feature, helping the team resolve 8 defects before release.

Education

Bachelor of Science in Computer Science — Front Range State University, Fort Collins, CO (2025)

Skills

  • Java
  • Python
  • SQL
  • REST API development
  • Git
  • React
  • Unit testing
  • CI/CD
  • Docker
  • AWS

Selected projects

• Campus Room Finder — Built a React and Java application that lets students filter campus study rooms by building and available equipment. • Budget Tracker API — Created a Python REST API with SQL storage, input validation, and tests for transaction and monthly summary routes.

Tools

• Java, Python, React, SQL, Git, Docker • JUnit, pytest, Postman, GitHub Actions

How to write a Entry-Level Software Engineer resume

Lead with shipped work

Put your degree and most relevant technical experience near the top, then use the first few bullets to show features or fixes that reached users. For each bullet, name the language or tool, your contribution, and a measured effect such as fewer support requests or less setup time. If a result was shared across a team, describe your part accurately.

Make internship work concrete

Internships count when the resume explains what you delivered. Identify the product area, code you changed, tests you added, and how the work fit a release. Use modest counts or time saved only when you can explain where they came from. Avoid presenting class assignments as paid production work or claiming ownership of a team’s full system.

Choose relevant projects

Include one or two projects if they show skills the job posting asks for or fill a gap in professional experience. Give each a short name, stack, and specific feature or engineering decision; link to a clean repository or demo when available. Remove unfinished tutorials, copied coursework, and projects whose code or documentation you cannot discuss.

List tools with evidence

Use a compact skills section for languages, frameworks, databases, cloud tools, and testing methods that you can discuss in an interview. Match the posting’s wording when it accurately describes your experience. Include relevant coursework only when it helps explain a foundation, and leave out proficiency bars, unsupported claims, and certifications unrelated to software development.

Common keywords

Skills and tools often listed for this role. Use only the ones you have, in the job advert's wording. Click one to copy it.

Action verbs

BuiltAutomatedReducedFixedTestedDocumentedDeployed

Questions about this role

How long should an entry-level software engineer resume be?

For a new graduate with an internship and a few relevant projects, one page is usually enough. Use two pages only if you have substantial relevant work, research, or technical projects that add useful detail. Keep the most relevant experience and skills easy to find, and trim older or unrelated work before shrinking the type.

Should I include class projects on my resume?

Yes, when a project shows skills relevant to the role and you can explain your contribution. Describe what it does, the tools you used, and a concrete technical detail such as an API, database design, test suite, or deployment. Clearly label academic or personal projects, and link to a repository only if it is readable and does not expose private data.

Do software engineers need certifications or a license?

Software engineering roles in the United States generally do not require a professional license or a standard certification. Some employers value specific cloud or platform credentials, but include one only if it is relevant and current. If an application asks about a credential, follow that employer’s instructions; requirements can vary by role and jurisdiction.

How can I move into software engineering from another field?

Lead with programming coursework, practical projects, bootcamp work, or technical responsibilities from your prior job that match the target role. Explain transferable experience through evidence, such as automating a report or maintaining a database, and distinguish it from professional software engineering work. Tailor the skills and projects to each posting, and include your degree or training clearly.