New Grad Software Engineer Resume With No Internship

No internship? That's normal for new grads. Recruiters understand you're starting your career. Here's how to build a resume that gets interviews using projects, coursework, and open source contributions.

Projects > Experience

When you don't have internship experience, your projects section becomes the most important part of your resume. Every CS student builds projects — class assignments, hackathons, personal apps, open source contributions. The trick is presenting them the right way.

Which Projects to Include

• Class projects that went beyond requirements — Did you add extra features? Handle edge cases? Deploy it somewhere? That counts.
• Hackathon projects — Even a weekend hackathon shows you can build something real under time pressure.
• Open source contributions — Fixing bugs or adding features to real projects shows you can work with existing codebases.
• Personal projects — Apps you built because you wanted to. These often show the most initiative.
• Senior capstone or thesis — These are real engineering projects. Treat them as such.

How to Frame Each Project (STAR Method)

Don't just list what you built. Explain the impact. Use the STAR framework:

Built a to-do app with React and Firebase

Developed a collaborative task management app (Situation: needed to coordinate group projects) using React and Firebase (Action). Implemented real-time sync across 15+ users, reducing missed deadlines by 40% (Result).

Coursework Section

Include 4-6 relevant courses that demonstrate CS fundamentals. Don't list every course — pick the ones that show depth in areas relevant to the roles you're targeting.

• Data Structures & Algorithms
• Operating Systems
• Database Systems
• Computer Networks
• Software Engineering
• Machine Learning / AI (if relevant)

Complete No-Internship Resume Structure

1. Contact — Name, email, GitHub, LinkedIn, phone (optional)
2. Education — School, degree, GPA (if 3.0+), graduation date, relevant coursework
3. Projects — 3-5 projects with STAR bullets (this is your main section)
4. Skills — Languages, frameworks, tools. Group by category if you have many
5. Activities / Leadership (optional) — CS clubs, hackathons, tutoring, TA roles

Before/After Example (Fictionalized)

Project: Weather App
- Made a weather app using Python
- Used an API to get weather data
- Displays temperature and forecast

Project: Real-Time Weather Dashboard
- Developed a Python weather dashboard processing data from 3 APIs (OpenWeatherMap, WeatherStack, AccuWeather) for 200+ cities (Situation/Task)
- Built a Flask backend with Redis caching to reduce API call latency by 60% (Action)
- Achieved 99.2% uptime over 3 months and served 1,800+ unique users (Result)

Common Mistakes to Avoid

• Listing every class project — Pick 3-5 strongest. Quality over quantity.
• Vague descriptions — "Worked on a team project" tells recruiters nothing. What did YOU do?
• No GitHub links — Recruiters check GitHub. Make sure your project repos are clean and have READMEs.
• Overcompensating with fluff — Don't add an "Objective" or "Summary" section that says nothing. Your projects speak louder.

All examples on this page are fictionalized for educational purposes. Replace with your actual projects and details.