New Grad Resume With No Internship Experience

Most resume advice assumes you have internships. You don’t, and that’s a real constraint — but not a disqualifying one. Recruiters reviewing entry-level roles know that not every candidate had access to internships. What they’re actually scanning for in those first 6-7 seconds is evidence that you can do the work. Projects, coursework, and open-source contributions can provide that evidence if you frame them correctly.

This guide covers exactly how to structure each section of your resume when internships aren’t part of your story.

Lead With a Summary That Sets Expectations

Skip the objective statement. Write a 2-3 line summary that names your degree, your technical focus, and one or two concrete things you’ve built or studied. Something like: “Computer Science graduate with hands-on experience building full-stack web applications using React and Node.js. Contributed to two open-source repositories and completed a capstone project processing 50K+ records with Python and PostgreSQL.”

This framing tells the recruiter immediately what you bring, without apologizing for what you lack.

Projects Section: Structure and What to Include

For a new grad without internships, the Projects section is your most important section — more important than Education, and often more important than Skills. Place it directly after your summary, before Education.

For each project, include:

• Project name and a one-line description of what it does and who it’s for
• Tech stack listed inline (not in a separate bullet)
• 2-3 achievement-oriented bullets using the same verb-metric-context pattern you’d use for job experience
• A link to the live demo or GitHub repo

A weak bullet: “Built a web app using React.”

A strong bullet: “Developed a React/Node.js expense tracker with JWT authentication, deployed on Heroku, used by 30+ classmates during beta testing.”

The difference is specificity. Name the tools, name the scale, name the outcome. Even small numbers (30 users, 500ms response time improvement, 95% test coverage) signal engineering discipline.

Aim for 3-4 projects. If you only have one strong project, build more before you apply — a weekend is enough to ship a small but complete project that demonstrates a specific skill.

Open-Source Contributions as Professional Experience

Open-source contributions belong in your Projects section or in a dedicated “Open-Source Contributions” subsection. Either placement works; the key is not to bury them.

Even small contributions count: fixing a documentation error, resolving a bug labeled “good first issue,” adding a test case. What matters is that you can point to a pull request that was reviewed and merged by someone other than yourself. That’s peer review — the same thing that happens in a professional engineering team.

Write it like this:

• [Project Name] — [Repository URL]
• Submitted 3 merged pull requests fixing edge-case bugs in the CSV parsing module (Python)
• Reduced test suite runtime by 12% by replacing redundant fixture calls

If you haven’t contributed to open source yet, start with repositories that match the tech stack of roles you’re targeting. Filter GitHub issues by “good first issue” or “help wanted.”

Relevant Coursework: Placement and Framing

Relevant coursework goes in your Education section, not as a standalone section. List 4-8 courses that map directly to the job description’s required skills. Use the official course names, not abbreviations your school uses internally.

For example: “Relevant coursework: Data Structures & Algorithms, Database Systems, Machine Learning, Operating Systems, Software Engineering.”

Don’t list every course you took. If you’re applying for a data analyst role, listing “Introduction to Marketing” adds noise. If a course involved a significant project, you can mention it briefly — but move the project itself to your Projects section where it gets proper space.

For more on how to tailor your resume content to specific job descriptions, see how to tailor your resume for each job.

Writing Bullets for Academic Team Projects

Team projects are tricky because you need to describe your individual contribution without underselling the collaborative context. The formula: start with what you personally owned, then reference the team outcome.

Weak: “Worked with a team of 4 to build a mobile app.”

Strong: “Designed and implemented the REST API layer (Flask) for a 4-person team’s mobile health tracking app; integrated with Google Fit API and reduced data sync latency by 40% during load testing.”

Always use first-person implied verbs (“Designed,” “Implemented,” “Led”) rather than “We” or “Helped.” Recruiters read hundreds of resumes; passive or collective language makes your contribution invisible.

If you were the team lead, say so: “Led sprint planning and code reviews for a 3-person agile team building a real-time chat application.”

Skills Section: Entry-Level ATS Optimization

Your Skills section exists primarily to pass ATS keyword filtering. Structure it by category rather than dumping a flat list:

Languages: Python, JavaScript, SQL, Java Frameworks & Libraries: React, Node.js, Flask, Pandas, NumPy Tools & Platforms: Git, Docker, PostgreSQL, AWS (S3, EC2), Jira Concepts: REST APIs, Agile/Scrum, Object-Oriented Design, Unit Testing

Match the exact terminology in the job description. If the posting says “PostgreSQL,” don’t just write “SQL.” If it says “agile methodology,” include that phrase. ATS systems often do exact or near-exact string matching before a human ever sees your resume.

For a deeper look at how ATS systems parse resume content, read what is ATS and check the ATS-friendly resume template for formatting guidance that won’t trip up parsers.

Don’t list skills you can’t discuss competently in an interview. Listing “Kubernetes” because you ran one tutorial will backfire in a technical screen.

Resume Format and Length

One page. No exceptions at the new grad level. If you’re struggling to fit everything, cut the coursework list to 4 courses and trim project bullets to 2 each.

Use a clean, single-column layout. Tables and multi-column formats cause parsing errors in many ATS systems — a problem covered in detail in how ATS parses resume columns and tables.

Font size 10-12pt, standard fonts (Calibri, Arial, Georgia), 0.5-1 inch margins. File format: PDF unless the application explicitly requests .docx.

Tailoring Each Application

Sending the same resume to every job is the single biggest mistake new grads make. A generic resume that lists everything you’ve done performs worse than a targeted resume that mirrors the specific language of one job description.

Before each application, read the job description and identify the 5-7 most important technical and functional requirements. Then check your resume: does each requirement appear at least once, in the same terminology? If not, adjust. This doesn’t mean fabricating experience — it means surfacing the relevant parts of what you already have.

Tools that automate this comparison, like TailorMyJob, can flag keyword gaps between your resume and a specific job description before you submit.

For a systematic approach to resume optimization that goes beyond keyword matching, the AI resume optimization guide covers the full workflow.

What to Do If You Have Almost Nothing

If your projects section is thin, spend two to four weeks before your job search building one substantial project end-to-end. Pick a problem you actually have (a budget tracker, a study scheduler, a local event aggregator), build it with a tech stack that matches your target roles, deploy it publicly, and write a README that explains the architecture decisions you made.

That single well-documented project, described with specific metrics and linked to a live deployment, is worth more on a new grad resume than three vague bullet points about coursework.

Open-source contributions can be built up in parallel — one merged PR per week over a month gives you four concrete contributions to list.

The resume you submit six weeks from now can look substantially different from the one you have today. That’s the actual strategy.