Junior Software Engineer Resume Example

A complete, annotated resume for a junior software engineer with one internship and strong projects. See exactly how to make thin experience look compelling enough to land interviews.

Scroll down to see the full resume, then read why each section works.

Sam Rivera
sam.rivera@email.com | (805) 555-0312 | linkedin.com/in/samrivera | github.com/samrivera
Summary

Software engineer with production experience in full-stack web development and a background in systems programming. Built and shipped features used by 11M+ merchants during a Shopify internship, and independently developed two applications with a combined 2,800+ active users. Currently building internal tooling at Plaid.

Experience
Junior Software Engineer
Plaid San Francisco, CA (Remote)
  • Built an internal dashboard for monitoring bank connection health across 12,000+ financial institutions, reducing the support team’s triage time for integration failures from 25 minutes to under 4 minutes
  • Wrote a migration script to consolidate three legacy institution-mapping tables into a single normalized schema, eliminating 340+ duplicate entries that were causing silent connection failures for 1.2% of Link sessions
  • Added end-to-end integration tests for the OAuth token refresh flow, catching a race condition in the token rotation logic that had been causing intermittent 401 errors for ~200 users per week
Software Engineering Intern
Shopify Toronto, ON (Remote)
  • Shipped a bulk inventory update feature for Shopify Admin that let merchants update up to 500 SKUs in a single action, adopted by 23,000+ stores within the first month and reducing average inventory management time by 65%
  • Optimized a slow GraphQL query in the product variant resolver by adding a DataLoader batch layer and composite index, cutting p95 response time from 2.8s to 340ms for merchants with 1,000+ variants
  • Wrote and presented the intern cohort’s technical deep-dive on Shopify’s approach to database sharding, which was later adapted into onboarding documentation for the Commerce team
Projects
studyboard
  • Full-stack study planner app that generates spaced-repetition schedules from uploaded lecture notes using GPT-4. Built with Next.js, PostgreSQL, and deployed on Vercel. 1,900+ registered users, 380+ weekly active users across 14 universities.
gitdiff-tui
  • Terminal-based Git diff viewer with syntax highlighting and side-by-side split mode. Written in Rust using the ratatui framework. 210+ GitHub stars, featured in the Rust subreddit’s monthly showcase.
Skills

Languages: TypeScript, Python, Ruby, Rust, SQL   Frameworks: React, Next.js, Rails, Node.js, GraphQL   Infrastructure: PostgreSQL, Redis, Docker, AWS (S3, Lambda), Vercel   Tools: Git, GitHub Actions, Datadog, Figma

Education
B.S. Computer Science
California Polytechnic State University, San Luis Obispo San Luis Obispo, CA

What makes this resume work

Seven things this junior resume does that most new-grad resumes don’t.

1

The projects section does the heavy lifting

With only one internship and a few months at Plaid, Sam’s experience section is thin by design. The projects section compensates — not with course assignments, but with real applications that have real users. A study planner with 1,900+ users and an open-source tool with 210+ GitHub stars tells a hiring manager this person builds things because they want to, not because a professor assigned it.

“1,900+ registered users, 380+ weekly active users across 14 universities.”
2

The internship reads like a full-time role

Most intern resumes say “assisted the team with feature development.” Sam’s says “shipped a bulk inventory update feature adopted by 23,000+ stores.” The difference isn’t exaggeration — it’s framing. The work was real, but instead of describing it as an intern task, it’s framed as a shipped feature with measurable adoption. That’s what hiring managers actually care about.

“Shipped a bulk inventory update feature...adopted by 23,000+ stores within the first month.”
3

The summary avoids every new-grad cliché

No “seeking an opportunity to grow,” no “passionate about technology,” no “quick learner.” Instead, it opens with a specific domain (“full-stack web development and systems programming”), drops a credibility marker (“11M+ merchants”), and closes with what Sam is doing right now. It reads like someone who already has a career, not someone begging for their first break.

“Built and shipped features used by 11M+ merchants during a Shopify internship...”
4

Skills separate production tools from academic ones

Sam lists TypeScript, Ruby, and Rust — languages used in actual shipped products and open-source work. There’s no Java or C++ from a data structures course that Sam hasn’t touched since sophomore year. Every skill on this resume has a corresponding bullet point that proves it was used in a real context. That’s the difference between a skills section and a keyword dump.

5

The current role shows growth trajectory

The Plaid bullets don’t just list tasks — they show someone who went from intern to catching production race conditions and consolidating database schemas. Three months into a junior role, Sam is already writing migration scripts and integration tests that fix real user-facing issues. That growth signal is exactly what a hiring manager at the next company is looking for.

“...catching a race condition in the token rotation logic that had been causing intermittent 401 errors for ~200 users per week.”
6

Education takes two lines, not half the page

Cal Poly SLO is a strong CS program, but the resume doesn’t lean on it. No “Relevant Coursework: Data Structures, Algorithms, Operating Systems” padding that every other new-grad resume has. The experience and projects already prove Sam can write production code. The degree is a checkbox — listed at the bottom, exactly where it belongs once you have real work to show.

7

Metrics are specific, not inflated

“1.2% of Link sessions” and “~200 users per week” are small, precise numbers. That’s more credible than rounding up to “improved reliability for thousands of users.” Hiring managers have a finely tuned BS detector, especially for junior candidates. Specificity signals honesty, and honesty builds trust before the interview even starts.

“...eliminating 340+ duplicate entries that were causing silent connection failures for 1.2% of Link sessions.”

Common resume mistakes vs. what this example does

Experience bullets

Weak
Assisted the engineering team with building new features. Helped fix bugs and participated in code reviews during my internship at Shopify.
Strong
Shipped a bulk inventory update feature for Shopify Admin that let merchants update up to 500 SKUs in a single action, adopted by 23,000+ stores within the first month.

The weak version describes participation. The strong version describes ownership. Interns ship features too — frame yours like you owned it, because you did.

Summary statement

Weak
Recent computer science graduate seeking an entry-level software engineering position. Passionate about coding and eager to learn new technologies in a collaborative environment.
Strong
Software engineer with production experience in full-stack web development. Built and shipped features used by 11M+ merchants during a Shopify internship, and independently developed two applications with 2,800+ active users.

The weak version is interchangeable with every new grad on earth. The strong version has numbers, named companies, and evidence of initiative — it could only describe one person.

Projects section

Weak
Built a to-do list application using React and Node.js for my web development class. Implemented CRUD operations and user authentication.
Strong
Full-stack study planner app that generates spaced-repetition schedules from uploaded lecture notes using GPT-4. Built with Next.js, PostgreSQL, deployed on Vercel. 1,900+ registered users, 380+ WAU.

The weak version describes homework. The strong version describes a product. If your project has real users, say so. If it doesn’t, build one that does — it matters more than your GPA.

Frequently asked questions

How do I write a resume with no experience?
Focus on what you’ve built, not where you’ve worked. A strong projects section with real applications — deployed, used by real people, or open-sourced with actual downloads — can outweigh a thin experience section. Lead with your internship or any part-time dev work, frame each bullet around impact (not tasks), and include 2–3 projects with tech stacks and measurable traction. Coursework alone won’t cut it, but a side project with 500 users says more than most internships.
Should I include my GPA?
Only if it’s above 3.5 and you graduated within the last two years. After that, nobody cares. If your GPA is below 3.5, leave it off entirely — no hiring manager will penalize you for omitting it, but a 2.9 on the page gives them a reason to pass. Use that space for a project or skill that actually demonstrates your ability to write production code.
How many projects should I list?
Two to three is the sweet spot. One is too few to show range, and four or more starts to look like padding. Pick projects that demonstrate different skills — one full-stack app, one CLI tool or library, one data or systems project. Each should have a one-line description of what it does, the tech stack, and at least one metric (users, downloads, performance improvement). Course projects are fine only if they went beyond the assignment requirements.
1 in 2,000

This resume format gets you hired

This exact resume template helped our founder land a remote data scientist role — beating 2,000+ other applicants, with zero connections and zero referrals. Just a great resume, tailored to the job.

Try Turquoise free