Resume example by job title
Entry-Level Software Developer Resume Example
In our view, a junior developer resume works best when a reviewer can check every claim: what you built, with which tools, and, where you can share it, a link to the code. This example is for a new graduate with one year of work and one internship.
General advice with a fictional example, not research and not a Yago customer result. What the advice says about hiring is our own reasoning, and employers differ.
The example
Fictional example. Priya Nair, the employers and the schools are invented, and any resemblance to a real person, employer or school is a coincidence. The numbers are made up.
Priya Nair
Software Developer
priya.nair@example.com · (919) 555-0151 · Raleigh, NC
Summary
Junior software developer with one year on a six-person web team. Works mostly in TypeScript and Python, and ships small changes with tests.
Experience
Software Developer, Tidewater Labs
Jul 2025 – Present- Built the order-history page in React and the API endpoint behind it, with unit and integration tests.
- Fixed more than 20 bugs from the support queue, most in the checkout flow.
- Replaced a flaky end-to-end test setup so the nightly run no longer fails on timing.
- Review teammates' pull requests and write the release notes for each deploy.
Software Engineering Intern, Brightwater Data
Jun 2024 – Aug 2024- Added CSV export to an internal reporting tool used by the finance team.
- Wrote the setup guide that the next intern used to get started in a day.
Education
Skills
TypeScript, Python, SQL · React, Node.js · PostgreSQL · Git and GitHub Actions · Unit and integration testing · Code review
Projects
- Open source: fixed a date-parsing bug in a small library used by a few hundred projects; the fix was merged after review.
- Personal: a command-line tool that renames photo files by the date they were taken.
Download this example as an editable Word file or a PDF, then replace each detail with your own. It is free, with no account; we ask for your email address before the first download in a visit.
What makes this example work
- Every claim can be checked. A page, an endpoint, a fix that was merged. Someone reading it can ask about each one and get an answer. In our view that is the point of a junior resume: claims that hold up when you are asked about them.
- Tools sit next to the work. React and the API appear inside the first bullet and again in the skills list. The reader sees the tool used for something, not just named.
- Tests and review are visible. Mentioning tests, a stabilised test run and pull request reviews tells the reader how this person works with a team.
- The internship has its own result. The CSV export and the setup guide are both finished things with a user: the finance team and the next intern.
- Projects are short and verifiable. One merged fix and one small tool. Both can be opened and read, which in our view matters more than the number of projects.
From a technology list to what you built with it
A bullet can list tools without saying what they were used for.
Weaker: Worked with React, Node.js and PostgreSQL on a web application.
Stronger: Built the order-history page in React and the API endpoint behind it, with unit and integration tests.
The stronger line says what was built, which layers you worked on and that you tested it. The weaker one names the stack and nothing else.
What to show on a developer resume
- What you built or fixed, written so it can be checked: a feature, an endpoint, a merged pull request.
- The languages and tools you used, placed inside the bullets and again in a short skills list.
- How you work with others: code review, tests, release notes, documentation.
- A link to code if you can share it: your GitHub profile or a repository.
- Projects with a clear scope, not a long list.
Leave out skill ratings and bars, and any language you could not write a small program in without looking it up.
Mistakes to avoid
- Listing twenty technologies. Pick the ones used in the bullets and the ones the posting asks for.
- Describing a team project as your own. Say what part you built.
- Linking to a profile that is empty or full of unfinished repositories. Pin two repositories you are happy to be asked about.
- Leaving out the dates of an internship. We would give the months and the length, so a reader can place it.
Skills to consider, if they are true for you
Group them if you like, but keep the list short and match the posting.
- Programming languages you use at work
- A front-end framework such as React
- A back-end runtime or framework
- A database and SQL
- Git and a CI tool
- Unit and integration testing
- Code review and documentation
Write yours
- Download the example and open it in Word, or copy its structure into your own file.
- Replace every line with something you did, keeping the pattern: what you did, for whom, and one detail.
- Delete anything you cannot back up in an interview, then ask someone to read it.
When your own version is ready, scan it in the CV Lab to see how it reads.
Which file type should you send? The one the posting asks for. Our guide to applicant tracking systems sets out what three vendors say about PDF and Word.
Want a different look? The CV templates come in eight layouts, as Word and PDF.
Frequently asked questions
Should I list every language I know?
No. List the ones you have used in real work or a real project, and be ready to talk about them. A long list invites questions you may not want.
Do side projects matter?
They can, especially when you have little work experience. One project with a clear purpose and code a reviewer can open is better than five unfinished ones.
How long should a junior developer resume be?
We suggest one page. If you have a lot of projects, link to your profile instead of listing them all.
Should I put my GitHub link on it?
Yes, if what is pinned there is something you are happy to discuss. Tidy the profile first. The example has no link because its developer is invented; yours would go in the contact line.