On this page
- Resume guide for an entry-level software engineer resume
- How to write an entry-level software engineer resume
- Choosing the best resume format for an entry-level software engineer resume
- Include your contact information
- Make use of a summary
- Right vs wrong: the same entry-level software engineer summary, twice
- Outline your experience
- What stands in for experience, ranked by what a screener can verify
- Build a snapshot of your key skills
- List your education and certifications
- Choose the right layout and design
- Entry-level software engineer job market and outlook
- What salary you can expect as an entry-level software engineer
- Key takeaways for an entry-level software engineer resume
- Related information technology resume examples
- FAQ
An entry-level software engineer resume is a one page document that puts your most checkable evidence first, because checkability is the only thing a first reader can act on.
First, there is a strange fact underneath this whole page. Specifically, the Bureau of Labor Statistics lists the entry requirement for software developers, quality assurance analysts and testers as a bachelor's degree with no work experience in a related occupation and no on-the-job training (BLS Occupational Outlook Handbook, 2025-35 cycle). In other words, on paper nothing is required except the degree. In practice, however, every posting asks for experience, and what fills that gap is a set of substitutes that vary enormously in how much a stranger can confirm. That is why ordering them correctly is most of the work of writing this resume.
Resume guide for an entry-level software engineer resume
In short, this guide and the corresponding entry-level software engineer resume example will cover:
- How to write an entry-level software engineer resume, section by section
- The five things that stand in for experience, ranked by verifiability
- What makes each of the five checkable, and what makes it worthless
- Three adaptable summaries: finishing study, first role and second promotion
- What the occupation pays at entry, and what it pays later
How to write an entry-level software engineer resume
First, use five blocks on one page: contact header, summary, evidence, education, and skills. Evidence goes above education, whatever your instinct says, because evidence is what differs between you and the other applicants and education mostly does not.
SectionThe question it answersWhere it goes
- SummaryWhat have you actually built, and where does it run?Top, three or four lines
- EvidenceWhich of your claims can I open right now?Above education, ranked
- EducationDegree, program or both, and when it finishedBelow evidence, three lines
- SkillsWhat could you be asked about on Monday?Bottom, grouped, honest
Write the block, then delete anything a stranger cannot confirm
Draft the page normally, then read every line back as a skeptical stranger with thirty seconds and no way to contact you. For each line, ask what they could do to check it.
Some lines survive easily: a merged pull request in a repository other people use, an internship at a named company with dates, a package with a download count, a deployed service with a URL and a user number. Some lines survive only as claims: a project described without saying where it runs, a course completed, a technology "used".
Anything that cannot be checked is not wrong to include, but it must not take the top of the page. The ranking is the whole technique, and most entry-level resumes get it backwards by leading with coursework.
Run the finished file through the ATS resume checker before you send it. Graduate pipelines run high volumes and parse first.
Choosing the best resume format for an entry-level software engineer resume
Reverse chronological, single column, one page. Not two, not one and a bit.
The one structural liberty worth taking at this level is putting a projects or evidence block above employment, because your strongest material is usually not a job. Keep the block itself in date order and keep the employment section, even if it holds a coffee shop and a campus help desk. After all, a reader is checking that you have held a commitment, not that it was technical.
Include your contact information
Rhiannon Castellanos
Software Engineer, Python and Go, first production change shipped 2025github.com/rcastellanos, 2 merged contributions to a package with 40,000 weekly downloads(210) 555-1034, rhiannon.castellanos@example.com, San Antonio, TXRhiannon Castellanos
Aspiring software engineer seeking an entry-level opportunityPassionate about coding and eager to learn(210) 555-1034, rhi.codes.2026@example.comAlso, the word "aspiring" does measurable damage, because it tells the reader to grade you on potential rather than on what is written below. Instead, drop it and let the evidence set the level.
Make use of a summary
Then write three or four lines: what you have built, where it runs, one number, and the honest statement of what stage you are at.
Finishing study adaptable resume summary example
First role adaptable resume summary example
Approaching second promotion adaptable resume summary example
Right vs wrong: the same entry-level software engineer summary, twice
By contrast, the right column is made of things that happened on a date and left a trace. The left column is made of adjectives about things that may also have happened, which is why it reads as weaker even when the underlying work was the same.
Outline your experience
If you have held a technical role, write it like any other job: company, title, dates, three to five bullets with numbers. If you have not, write the non-technical jobs briefly and let the evidence block carry the page.
- Instead of
Completed a software engineering internship
UseShipped a retry and dead-letter path for the billing webhook consumer in week 7; it is still in production
- Instead of
Gained experience with Python and SQL
UseWrote the reconciliation query that found 1,900 unmatched billing events, now run nightly
- Instead of
Contributed to open source
UseTwo merged pull requests to a date parsing package with 40,000 weekly downloads, including one bug fix with a regression test
- Instead of
Worked on a team project at university
UseBuilt the availability solver in a 4-person capstone; 3 departments used the result for one term
- Instead of
Built a personal portfolio project
UseDeployed a bus arrival tracker used by 340 distinct people a month over six months, at $4 a month in hosting
Adaptable resume employment history example
Software Engineer I, Terracourt Systems, San Antonio, TX, February 2025 to Present. Go services, Python jobs, PostgreSQL.
Own the notification service end to end, 1.2 million messages a month across email and push.
Rewrote its retry policy with exponential backoff and a dead-letter queue, taking the failure rate from 0.9% to 0.1% and removing a weekly manual replay task.
Added 64 tests to the billing consumer during an incident follow-up, including the four duplicate-delivery cases that had caused it.
Carry the pager for two services in a rotation of six, and wrote the replay runbook the rest of the team now uses.
What stands in for experience, ranked by what a screener can verify
At this level, five things generally stand in for professional experience. However, they are not equal, and the order below is the order they should appear on your page.
| Rank | Substitute | What makes it checkable | What makes it worthless |
|---|---|---|---|
| 1 | Internship with a change that reached production | A named company, exact dates, a specific change, and a manager who can confirm it | "Shadowed the team", no shipped change, or a description that never says whether it went live |
| 2 | Merged open source contribution | A link to a merged pull request in a repository other people depend on, with a diff and a review thread a stranger can read | A README typo, a still-open pull request, or a repository with one contributor and no users |
| 3 | Capstone or sponsored course project | A named sponsor, the team size, your specific part, and what the sponsor did with it afterwards | The assignment 200 classmates also submitted, with no deviation from the brief named |
| 4 | Personal project with real users | A user count with the window it was measured over, where it is deployed, and the support you had to do | A to-do app, a tutorial followed to completion, or "users" that means three classmates |
| 5 | Coursework alone | A transcript, which nobody opens at screening | Listing course titles as though they were achievements |
Entry-level software engineer evidence ladder
The gap between rank 2 and rank 3 is bigger than it looks. For example, a screener can open a merged pull request and form a judgment in thirty seconds. Nobody can open a capstone. That difference decides what goes at the top of the page, regardless of which piece of work you are proudest of.
Adaptable resume evidence block example
Internship, Quillmark Software, San Antonio, TX, twelve weeks, summer 2025. Shipped a retry and dead-letter path for the billing webhook consumer in week 7. It is still in production and reduced the manual replay queue from about 40 events a week to under 5. Manager can confirm; reference on request.
Open source: 2 merged pull requests to an open source date parsing package with roughly 40,000 weekly downloads, one a timezone bug fix with a regression test, one a documentation correction. Both merged within a week.
Capstone, 4-person team, autumn 2025, sponsored by the university registrar. Built the availability solver. 3 departments used the resulting schedule for one term and the registrar kept the code.
Personal project: a bus arrival tracker for two San Antonio routes, deployed and used by roughly 340 distinct people a month over six months, hosting $4 a month. Ran it through one API deprecation and two outages.
Next, list four entries, ordered by how fast a stranger can confirm them, and every entry saying plainly where the work ended up. Notice that the internship is not the largest piece of work on that list, and it is still first.
Say where it ended up, in every entry
The single most common omission on an entry-level engineering resume is the ending. Applicants describe what they built and stop, leaving the reader to guess whether it shipped, whether anyone used it, and whether it is still running.
Add one clause to every evidence entry: still in production, merged in a week, kept by the registrar, ran for six months, retired when the course ended. Even a negative ending is useful, because it is specific and it shows you know the difference.
This is also the fastest way to shorten the page. Once every entry has an ending, the entries without one are visibly weaker and can be cut without argument.
If your top rung is a capstone, say so and give it the room. On the other hand, padding a thin ladder with five weak entries makes the strong one harder to find, and a reader who works out that you have listed everything you have ever done will assume the top entry is the best you can do.
Build a snapshot of your key skills
Later, in skills, use two groups, ten to fourteen entries, and nothing you could not be asked about on Monday.
Adaptable resume skills example
Languages and tools I would be interviewed on now: Python, TypeScript, SQL, Git, pytest, Docker, PostgreSQL, REST APIs
Used in a real project, still learning: Go, message queues and retry design, Terraform, GitHub Actions
Not claimed: front-end frameworks beyond basic React, Kubernetes, distributed systems design
Splitting the list into what you can defend now and what you have touched once is unusual at this level, but it works. As a result, it removes the interviewer's main worry about an entry-level resume, which is that the skills section was assembled from job postings.
List your education and certifications
Then give the institution, credential, field and the year it finished. Then a program or bootcamp if you did one, with its length. Then stop.
Adaptable resume education example
Bachelor of Arts, Mathematics, The University of Texas at San Antonio, San Antonio, TX, 2026
Software Engineering Program, Bellrose Code Institute, San Antonio, TX, 2025 to 2026. 24 weeks part-time, capstone project used by 3 university departments.
Coursework worth a line while it is recent: data structures, linear algebra, probability, databases.
Keep this block to four lines. The temptation at entry level is to expand it, because it is the part of the page with the most material, but a reader spends almost no time here once the evidence block has done its job.
Choose the right layout and design
Finally, keep the format simple: single column, 11 or 12 point, one page, no photograph, no skill bars, no graduation date hidden in a sidebar. Export to PDF.
Do
- Rank your evidence by how fast a stranger could check it.
- Put the internship with a shipped change first, even if it was not your biggest project.
- Give every entry an ending: shipped, merged, kept, retired.
- Put a number and a window on every user claim.
- Say which skills you could be interviewed on this week.
- Keep it to one page.
Don’t
- Do not use the word aspiring, which invites grading on potential.
- Do not list a still-open pull request as a contribution.
- Do not describe a project without saying where it runs.
- Do not write "users" without a number and a period.
- Do not lead with coursework, which is the least checkable thing on the page.
- Do not claim a language you learned last week.
Entry-level software engineer job market and outlook
Meanwhile, the occupation you are entering is published by the BLS as software developers, quality assurance analysts, and testers, and its Quick Facts are unusually favorable for a new entrant.
| Measure | Value |
|---|---|
| Jobs, 2025 | 1,905,400 |
| Projected change, 2025-35 | 10% (much faster than average), +185,400 |
| Projected annual openings | About 106,100 |
| Typical entry-level education | Bachelor's degree |
| Work experience in a related occupation | None |
| On-the-job training | None |
| Median annual wage, May 2025 | $134,040 combined; software developers $135,980, QA analysts and testers $104,300 |
The published entry requirement is a degree and nothing else
The Handbook records the typical entry-level education for software developers, quality assurance analysts and testers as a bachelor's degree, with work experience in a related occupation recorded as none and on-the-job training recorded as none (BLS Occupational Outlook Handbook, 2025-35 cycle). That is the formal position for an occupation holding 1,905,400 jobs in 2025 with about 106,100 openings projected a year and 10 percent growth to 2035 (BLS, 2025-35 projections).
No employer is bound by that, and most postings ask for more. But it tells you what the gap between the published requirement and the advertised one is made of: not a qualification, since none exists beyond the degree, but proof that you have done the work somewhere.
That is why the ranking on this page matters more than any other decision you make. Every substitute is filling the same hole, and the ones a screener can open are worth several times the ones they cannot.
Also, where the openings sit is worth one more line. For instance, about 106,100 openings a year in an occupation of 1,905,400 means roughly one opening for every eighteen people already in the job, every year. Therefore, volume is not your problem at entry level. Being legible in that volume is.
What salary you can expect as an entry-level software engineer
Even so, the published medians are not entry numbers, and treating them as one is the commonest mistake in a first salary conversation.
Instead, the useful figure is the bottom of the published distribution. Across software developers, quality assurance analysts and testers, the lowest 10 percent earned less than $82,460 and the highest 10 percent more than $214,670 as of May 2025, a spread of $132,210 (BLS, May 2025). A first offer sits near the bottom of that range, not near the $134,040 group median or the $135,980 median for software developers specifically.
Title matters too, because at entry level it is often the only lever available. For example, quality assurance analysts and testers had a median of $104,300 against $135,980 for software developers, a difference of $31,680 (BLS, May 2025). A QA or test automation role is a legitimate and common entry point, and it is much easier to enter, but the resume you write in year two decides whether the gap closes.
Industry shifts the number as well. For software developers the published medians run from $164,550 in software publishers down to $132,050 in computer systems design and related services; for quality assurance analysts and testers they run from $129,930 in manufacturing to $99,960 in computer systems design and related services (BLS, May 2025).
In the end, what you can control at entry is which end of the distribution your file reads as. The evidence ranking is the mechanism: a resume where the first thing a reader can open is a production change or a merged contribution reads as someone already inside the occupation, not someone applying to join it.
Key takeaways for an entry-level software engineer resume
- First, rank your evidence by how fast a stranger could check it, not by how proud you are of it.
- That means an internship with a shipped change outranks a bigger project nobody can open.
- Similarly, a merged pull request in a repository people use is the second strongest thing on the page.
- Give every entry an ending: shipped, merged, kept, retired.
- Also, put a number and a measurement window on every user claim.
- Then split your skills into what you could defend now and what you have touched once.
- One page, evidence above education, and never the word aspiring.
Related information technology resume examples
- Software engineer resume
- Software developer resume
- Computer science resume
- Computer science internship resume
- Java developer resume
- Google resume
- QA tester resume
- Software tester resume
- Full stack developer resume
- Front-end developer resume
- Web developer resume
- Data analyst resume
Entry-level software engineer resume questions, answered
How long should an entry-level software engineer resume be?
One page. There is no version of an early career that needs two, and a second page at this stage reads as material that could not be ranked. If you are overflowing, the cut is the weakest evidence entry and half the coursework line.
I have no internship. What goes at the top?
Whatever is next on the ladder that a stranger can open. A merged contribution to a repository with real users, then a sponsored capstone with a named sponsor and an afterwards, then a deployed project with a user count and a window. Write the strongest one as a full block with an ending, and give the weaker ones a line each.
Are personal projects worth putting on the page?
Yes, when they have users and you say how many over what period. A deployed tool used by 340 people a month for six months, run through an API deprecation and two outages, is real evidence of operating software. A tutorial finished is not, and a reader can tell the difference immediately.
Should I include my grade point average?
Only if it is strong and recent, on one line inside the education block, and only in your first year or two. It is not checkable at screening and it is not what the evidence ranking is built on, so it should never take space from an entry with an ending.
What if my degree is not in computer science?
Write it plainly with the field, add the program or self-directed study that closed the gap with its length, and then let the evidence block do the work. The published entry requirement is a bachelor's degree, and the substitutes above are what a reader is judging. A mathematics graduate with a shipped production change is in a stronger position than a computer science graduate without one.
How do I describe an internship where I did not ship anything?
Honestly and briefly, and then rank it below your open source or project work. Say what you were assigned, what you built, and why it did not ship if you know. An internship written accurately and placed second is far better than one dressed up and placed first, because the follow-up question at interview is always what happened to it.