
What to take from this guide
- Show the code you owned, the decisions you made and how you tested it.
- Label course projects, personal work and internships accurately.
- Use technical skills you can explain, without invented users or results.
What should go first on a new graduate developer resume?
Choose the order from your strongest evidence. With a relevant internship, try education, technical skills, experience, then selected projects. Without one, try education, technical skills, projects, then other experience. Keep dates and job titles visible in either version.
MIT Career Advising recommends selecting experience from the position description and explicitly includes class projects, competitions and personal projects. It also advises naming the language used when describing software work (MIT resume guidance). That is a useful starting point when your strongest evidence lives in a repository rather than an employment record.
Use the software engineer resume example for a familiar structure, then replace experienced-hire achievements with your own graduate evidence. If you need help organising the search itself, our first job after graduation guide covers that wider process.
Which projects deserve space?
Choose projects that let you discuss a technical decision, a failure and a fix. A small scheduling application with validation and tests can give you more to talk about than a large tutorial clone you cannot change without following the video again.
- For a backend vacancy, show a service, data model, API or integration you implemented. Explain how you handled an error or checked an edge case.
- For a frontend vacancy, show an interaction you built, the state it manages and how you handled loading, empty or error states.
- For a data role, identify the dataset, cleaning work and checks. Label public, synthetic or classroom data accurately.
- For a team capstone, name the component you owned and how it connected to other work. Separate your contribution from the overall team outcome.
Give the project a descriptive name and label its context: “Personal project”, “Course project” or “Team capstone”. Keep a client name only if you are allowed to disclose it. A university assignment is valid evidence without being called freelance work.
How do you write project bullets that survive an interview?
Use this pattern: what you implemented, the technical choice, and the behaviour you verified. The examples below are fictional. Copy the shape, then replace the details with code you actually wrote.
Backend implementation
Before
Created a booking app using Python.
After
Implemented booking endpoints in Python and PostgreSQL; added a transaction check and integration tests for overlapping reservation requests.
Why it works: The implementation names the stack and the edge case that was tested.
Frontend interaction
Before
Built a React website.
After
Built a React booking form with validation and keyboard navigation; kept entered details visible after a failed submission so users could retry.
Why it works: The interaction and its error state show what the developer actually built.
Regression testing
Before
Improved app performance and quality.
After
Added regression tests for expired sessions and duplicate submissions after reproducing both failures in the booking flow.
Why it works: Specific failure cases replace a broad claim about quality.
Team contribution
Before
Led development of an entire marketplace.
After
Owned the listing search API in a team capstone, documented its response shape and worked with a teammate to connect the filters.
Why it works: The component and integration work make individual ownership clear.
Do not attach a percentage improvement unless you measured it. If you did benchmark something, keep the before and after values, test conditions and measurement method in your notes. A local test is a local test; label it that way instead of implying production traffic.
What belongs in the technical skills section?
Group skills by what they are, using short headings such as Languages, Frameworks, Data and Development tools. List what you can use and explain. Avoid progress bars, star ratings and a collection of logos.
A fictional example might read: “Languages: Python, TypeScript, SQL. Frameworks: React, FastAPI. Data: PostgreSQL. Tools: Git, pytest.” Each item should connect to a project, internship or concrete task. Remove a framework if your only contact was watching someone use it.
Choose the skills relevant to this vacancy. Do not add Java to a Python project because the advert asks for Java. If the stack is different, explain the transferable work in your letter rather than changing the history. Our ATS-friendly resume checklist covers the document checks alongside the content.
How do you describe an internship without exposing confidential work?
Name the type of system and your contribution at a level your employer permits. For example, a fictional safe line is “Added validation and regression tests to an internal invoice import service.” You can explain the engineering without sharing customer data, internal URLs or proprietary code.
Keep the official internship title. Do not turn a supervised placement into a senior engineering role. If your change never shipped, describe the prototype or test work you completed rather than claiming a live result.
Keep unrelated part-time work brief, but retain a specific contribution if it shows reliability or collaboration. The resume with no experience walkthrough shows how to label nontechnical work without stretching it.
What should you check before submitting this week?
- Open repository and demo links while signed out. Make sure the intended work is accessible and the README explains what the project does and how to run it.
- Review the repository for credentials, personal data and material you do not have permission to publish. Keep private work private.
- Read every bullet aloud and explain how you would answer “What did you personally build?” Remove any claim you cannot support.
- Run the exported document through the free ATS score checker, then inspect the file yourself for broken links or missing text. See what an ATS does to your resume for the limits of automated screening advice.
Questions people ask
Yes. Label them as course projects, name your own contribution and describe the implementation. Do not present a class assignment as paid client work.
Yes, if it demonstrates relevant engineering work. Explain the problem, your implementation and how you tested it. Do not invent adoption or describe a local prototype as a production service.
Follow the vacancy requirements. If you share a repository, make sure it is readable, accessible and safe to publish. Never upload confidential internship code to fill a portfolio.
Prioritise languages you can use and discuss, especially those relevant to the vacancy. A short, defensible list is more useful than a long list you cannot support.
Your next step
Choose the project closest to the vacancy, rewrite its bullets around your implementation and tests, then check your graduate developer resume for vague claims before you submit it.
Put your own resume to the test
Find vague claims and work descriptions that need clearer evidence.
Check my resume