Writing a resume with limited work experience is a design problem, not a content problem. The trick is structuring the page so that your strongest signals (projects, internships, relevant coursework, leadership roles) get the same visual weight that a senior hire's job titles would. These templates do exactly that.
Recommended templates
Modern
Clean sans-serif type with a left-aligned header and quietly bold section rules. Designed for engineers, designers, and PMs at startups.
Use this template → Best for fitting projects + courseworkCompact
Pure single column, standard section names, dense bullet spacing. Looks plain on purpose — lets your content do the talking.
Use this template → Best for traditional industries & financeClassic
Serif headings, generous margins, a Harvard-business-school feel that ages well across industries and seniority levels.
Use this template →
A clean, ATS-ready resume built with LuckyResume — ready to customize.
Try it free — pick a template and start writing
Start in seconds. Fill the form, export a clean one-page PDF. No watermarks, no paywall.
Open the editor →Section order: education first or experience first?
For new graduates, the section order question has a simple answer: put your strongest section first. If you had a meaningful internship at a recognizable company, lead with Experience. If your strongest signal is a 3.8 GPA from a strong program with relevant coursework, lead with Education.
Most new grads should lead with Education if they graduated within the past 12 months and their internship experience is limited. Once you have one full-time role under your belt, Experience moves to the top and stays there for the rest of your career.
The template handles this gracefully — you can reorder sections in the editor without breaking the layout. But the decision of what goes first is yours, and it should be deliberate.
Making projects look like real experience
The Projects section is the most underutilized section on new grad resumes. Most candidates list their projects as afterthoughts — a title and a one-line description. This is a mistake. A well-written project entry can be just as impressive as an internship.
Structure project entries the same way you'd structure a job: Project Name — Technologies Used — Date Range, followed by 2-3 bullets using the Action → Context → Result pattern. "Built a real-time chat application using React, Node.js, and WebSockets that handles 500 concurrent users" is a bullet that demonstrates real engineering judgment.
The key is specificity. "Built a web app" is forgettable. "Built a course registration system that replaced a manual spreadsheet process for 200 students, reducing registration time from 3 days to 2 hours" tells a story with a real user, a real problem, and a measurable improvement.
CourseMatch — React, Python, PostgreSQL (Jan-Apr 2026)
Built a course registration system that replaced a manual spreadsheet process for 200 students, reducing registration time from 3 days to 2 hours. Deployed on AWS with CI/CD via GitHub Actions.
Web App Project
Built a web application using React and Node.js for a class project. Implemented CRUD operations and user authentication.
GPA, coursework, and honors: what to include
The GPA question has a clear threshold: 3.5 and above, always include it. Between 3.0 and 3.5, include it only if the job posting mentions a GPA requirement. Below 3.0, leave it off. No employer will ask "why didn't you list your GPA?" — but a low GPA listed voluntarily raises questions.
Relevant coursework is valuable when it directly maps to the role. If you're applying for a data science position and you took Machine Learning, Statistical Inference, and Database Systems, list them. If you're applying for a frontend role, those courses are less relevant — list Human-Computer Interaction or Web Development instead.
Honors, dean's list, and scholarships belong in the Education section if they're meaningful. "Dean's List (6 semesters)" is a strong signal. "Member of XYZ Honor Society" is filler unless the society is widely recognized (Phi Beta Kappa, Tau Beta Pi).
A new grad resume with 60% content and 40% whitespace looks more confident than one that's 95% content with tiny margins. Don't pad your resume with filler to fill the page — let the whitespace signal that you're selective about what you include.
Ready to build your resume?
Pick a template, fill in your details, and export a clean PDF. Free, no account required.
Frequently asked questions
Which template is best for a new grad?
Modern is the most versatile — it works for tech, consulting, and general applications. Compact is better if you have a lot of projects and coursework to fit. Classic is the safe pick for finance, law, or government roles.
Should I include my GPA?
If it's 3.5 or above, yes. If it's between 3.0 and 3.5, include it only if the job posting mentions a GPA requirement. Below 3.0, leave it off — your projects and internships will speak louder.
How do I fill a resume with no experience?
You have more experience than you think. Class projects, hackathons, open-source contributions, campus leadership, tutoring, and freelance work all count. Structure them with the same Action → Context → Result bullet pattern used for jobs.
Should I include high school achievements?
Only if you're a college freshman or sophomore with very limited college experience. By junior year, high school should be off your resume entirely.
Is an objective statement necessary for new grads?
No. Objective statements ("Seeking a challenging position in software engineering...") are outdated and waste space. If you want to frame your candidacy, use a 1-2 line summary instead — but only if you can say something specific.