Student and Graduate Resume Templates

This category is empty. No student-specific templates ship in the gallery right now, so there is nothing to browse here. That is deliberate honesty, not a bug you are missing.

Start from a general single-column template instead. ATS Clean is the safest pick: one column, recruiter-friendly, nothing for a parser to trip on. Modern Minimal works too if you want a little more structure with clean typography. You will find both on the ATS templates page and the software engineer templates page. Pick one, then follow the layout advice below.

Put education first. When you have no full-time roles yet, your degree, school, graduation date, and relevant coursework are the strongest signal, so they belong at the top under your contact line.

Treat projects and coursework as experience. A class project, a hackathon build, or a personal repo counts. Give each one a title, a one-line context, and two or three bullets on what you built and the result. Link the repo or the live demo.

List internships and part-time work honestly. A summer internship, a teaching assistant role, or a campus job all show you can hold responsibility. Use the same bullet format you would for a full job.

Skip the objective statement. 'Seeking a challenging role where I can grow' tells a reader nothing. Use a two-line summary of what you build and the stack you know, or use nothing and let the projects speak.

Keep it to one page. You do not have the history to justify two, and a tight page reads as focused, not thin.

Single column is the rule here for the same reason it is everywhere: an older parser reads left to right across the full width, so a two- column layout can splice your skills list into the middle of a project description. With little content to spare, that scramble hurts more.

Name sections plainly: Education, Projects, Experience, Skills. A parser maps standard headings to fields. A clever label like 'Things I have shipped' can land your projects in the wrong bucket or nowhere.

Spell out your graduation date as a month and year, and mark it 'expected' if you have not finished. Put your tech stack in a real Skills section as plain text, not inside a graphic or a skills bar, since the parser cannot read an image.

Run the result through the ATS score in Roleframe before you send it, and tailor the base resume to each posting so the keywords that matter for that job are actually present.