Entry-Level Software Engineer resume example

• Entry level

  Computer science senior graduating in May with one software engineering internship and two shipped projects. Built a course-planning web app in React and Flask used by 600 students, and wrote integration tests for a payroll API during the internship. Comfortable in Java, Python, TypeScript and SQL, and looking for a new-graduate role on a team that reviews code.

• Mid level

  Software engineer graduate with two internships and a year of part-time contract work, now seeking a first full-time role. Shipped a scheduling feature to production for a transit app, contributed three merged pull requests to an open source testing library, and maintains a TypeScript side project with 1,200 monthly users. Strong in Python, TypeScript and PostgreSQL.

• Senior

  Career changer moving into software after six years as a lab manager, with a coding bootcamp, a year of freelance development and a published inventory tool used by four labs. Brings experience writing procedures, managing budgets and training staff, and pairs it with solid Python, Django and SQL skills. Seeking an entry-level engineering role where domain knowledge helps.

• Listing class assignments as projects

  Fix: A to-do app built from a tutorial will not stand out, because many applicants show the same thing. Pick projects you designed yourself or extended well past the assignment. Say what problem it solves, who used it and what was hard. If a course project was substantial, such as a compiler or a distributed key-value store, describe the design choices you made.

• A skills section longer than your experience

  Fix: Twenty languages and frameworks on a new graduate's resume suggest shallow exposure. Keep the ones you could be interviewed on and that the posting lists. For each skill you keep, make sure a project or internship bullet shows you using it. Interviewers often pick something from your skills list and ask you to code in it.

• Writing internship bullets about meetings and learning

  Fix: "Attended standups and learned Agile" says nothing about your work. Describe what you shipped: the feature, the bug you fixed, the test suite you added, and what happened after it merged. Even a small change counts if it went to production, for example "added input validation that cut form errors 30% for 4,000 weekly users."

• No links, or links to empty repositories

  Fix: Reviewers often click a GitHub link on an entry-level resume. Pin your best two or three repositories, write a README with screenshots and setup steps, and make sure the commit history looks like steady work rather than one upload. If a project is private because of a class policy, say so and offer a walkthrough.

Match these against the job posting you are applying to: the free resume checker shows which keywords your resume is missing.

• Built a course-planning web app with React and Flask that 600 students used to map prerequisites during registration week.
• Shipped a seat-availability filter to production during an internship, used by 9,000 riders in its first month.
• Implemented integration tests for a payroll API with pytest, raising coverage on the module from 48% to 76%.
• Debugged a race condition in a shared calendar feature by adding database locking, ending duplicate bookings reported by users.
• Contributed 3 merged pull requests to an open source testing library, including a fix for a flaky timezone test.
• Tested a mobile check-in screen on 12 device sizes and fixed 15 layout bugs before the club's public launch.
• Wrote a Python scraper and dashboard that tracked campus dining wait times for 1,100 daily visitors.
• Led a team of 4 in a 36-hour hackathon to build a food bank inventory app, placing second of 40 teams.
• Reduced page load time on a personal portfolio site from 3.8 seconds to 0.9 seconds by compressing images and lazy loading.
• Tutored 25 first-year students a semester in Java and data structures through a peer coding club.

• Tailor which projects come first

  With limited experience, the order of your projects is your main tailoring tool. For a web role, lead with the full-stack app. For a backend or data role, lead with the API or the pipeline. Use the posting's language and framework names in the project bullets when they are accurate, and drop projects that do not fit. Tailor your new-grad resume

• Write a short, specific cover letter

  New graduates often write about passion. Write about evidence instead: one project or internship result that matches the team, why the company's product interests you in concrete terms, and when you can start. Three short paragraphs is plenty. If you have a referral or met the team at a career fair, say so first. Draft an entry-level cover letter

• Practice coding out loud

  Early-career interviews often include timed algorithm problems and a walkthrough of a project from your resume. Practice explaining your approach before you code, testing with edge cases and stating time and space complexity. For your projects, be ready to say what you would change and why you chose that stack. Prepare for new-grad interviews

• See what the next level looks like

  Compare your draft with a software engineer resume to see how experienced engineers describe scope and impact. You will not have the same numbers yet, but you can borrow the structure: what you built, for whom, and what changed. That helps your internship bullets read like engineering work. See a software engineer resume example