Entry-level software engineer resume: example and writing guide

If you are a new grad applying for a junior developer role, start by reading one real posting before deciding what belongs near the top. A frontend role might need evidence of interface work, accessibility and collaboration. A backend role might call for APIs, data modelling and testing. The same project can demonstrate different things, but its underlying facts must stay the same.

List your contributions separately from the team's result. If a teammate built the API and you built the interface, describe your interface work. You can explain the system you worked within without claiming ownership of the whole application.

The sample below is for a fictional applicant targeting a junior frontend role. Its projects and employment are invented for teaching. Replace every identity, date and experience with your own; choose a different structure if your strongest evidence is an internship rather than coursework.

A technology list does not explain what you can do. Pair the tool with a concrete action, such as adding validation, designing a query or writing a regression test. Describe the scope honestly: a local prototype is a local prototype, not a production system serving customers.

You do not need a percentage in every bullet. A working feature, a resolved defect or clear documentation can be a concrete outcome. If you report performance, keep the test conditions and measurements so you can explain where the number came from.

Give each project its own short entry under a Projects heading: a name, the tools you actually used, one to three bullets on what you built and, if there is one, a link a reader can open. A recruiter may not run your code, so the bullets have to stand on their own.

Link to a repository only if someone else could understand it: a README that says what the project does, how to run it and which parts you built. A profile link on its own tells a reader little; link to the repositories that match the role.

Put the most relevant evidence where it is easy to find. Education may lead when you are a recent graduate; a relevant internship may deserve the earlier position. Use clear section headings and consistent dates rather than adding decorative labels that obscure the content.

Open the exported file, check line breaks and select the text to inspect its reading order. Follow the employer's requested format. Keep links accurate and make sure any repository you share has enough instructions for another person to understand it.