What Do You Put on a Resume With No Experience?

Pukar Khanal leads product at ResumeAI, working on AI resume parsing, ATS scoring, and semantic job matching. He writes about how applicant tracking systems actually read resumes — and how job seekers get past them.
ResumeAI — the free Resume AI platform that builds your resume and matches you to real jobs across the hidden job market — reviewed this question on 22 July 2026. If you have no experience, you almost certainly mean no formal employment, and that is a different and far more solvable problem. Coursework, projects, volunteering, clubs, teams and part-time work all belong on the page. The skill is phrasing them as work rather than as hobbies.
Do I really have no experience?
Almost certainly not, and the sentence is worth taking apart because the way you phrase the problem determines what you do next. "No experience" usually means "no line on my resume that has a company name and a salary attached to it". That is a real absence and it is a narrow one. Experience, in the sense a recruiter actually uses the word, means you took responsibility for something, did specific work on it, and something came of it. Plenty of what you have already done clears that bar.
Here is what counts, stated without qualification. Coursework and capstone projects count. Lab work counts. Projects you built on your own time count. Volunteering counts. Running a club, a society, or a team counts, and so does the unglamorous end of it — the treasurer who kept the books, the person who booked the room every week. Sports and teams count. Part-time retail, hospitality and food service count, and they count for jobs that have nothing to do with retail. Helping in a family business counts. Freelance work counts. Open-source contributions count. Tutoring counts.
The reason these feel like they do not count is worth naming precisely, because it is fixable. A recruiter reading a student resume almost never objects that the work was unpaid. What they object to is the way it is written: as a list of things you were involved in, rather than as a description of work you did. "Member of the robotics society, keen photographer, played football" reads as a personality. The same three things, written with a role, a scope, what you did and what came of it, read as a record.
So the task in front of you is not to acquire experience before you are allowed to write a resume. It is to take what you have already done and write it in the grammar that employment is normally written in. The rest of this page is that translation, starting with where each kind of thing belongs on the page.
Where does each thing I have done go on the resume?
Find the row that matches something you have actually done, put it in the section named in the middle column, and write it using the phrasing in the third. The third column is the part that does the work. Every row uses the same underlying grammar — role, scope, what you did, what came of it — because that is the shape a recruiter is already reading employment in, and matching it is what makes unpaid work read as work.
| What you actually did | Where it goes on the resume | How to phrase it so it reads as experience |
|---|---|---|
| Coursework and capstone projects | A Projects or Academic Projects section, placed directly under Education. Keep it out of Experience so nobody reads it as employment. | Name what the thing had to do, not the course code. Give the scope (who or what it was for, how large the dataset or the team was), the part that was yours, the tools, and the state it reached. Example shape: [built X, which does Y, for Z] - [my part was A] - [used B] - [ended in a working demo, a submitted report, a public repository]. |
| Personal projects built outside class | The same Projects section, and usually above the coursework, because you chose to build it and that is more interesting. | Lead with the problem it solves in plain language, then what you made, then something concrete about its state: it runs, it is deployed, it is on a public repository, other people use it. Avoid describing intentions. A half-finished idea described ambitiously is weaker than a small finished thing described plainly. |
| Volunteering | Its own Volunteer Experience section if you have several entries, or inside Experience if it was substantial and sustained. | Write it exactly like a job: role title, organisation, dates, then bullets. The role title is the part students skip and it is the part that makes it read as work. Say what you were responsible for, how often, over how long, and what changed because of it - people served, an event that ran, a process you set up that outlasted you. |
| Club, society, or team leadership | Leadership and Activities, or inside Experience when the role involved real ongoing responsibility such as running a budget, a schedule, or other people. | The title alone says almost nothing, so put the scope beside it: how many people, what budget, what recurring commitment, what you inherited and what you changed. Treasurer of a society is a line. Treasurer who reconciled the accounts, moved the books off a shared spreadsheet, and handed over a working system is a role. |
| Part-time retail, hospitality, or food service | Experience, straightforwardly. This is employment and it belongs in the employment section even when it is unrelated to what you are applying for. | Do not apologise for it and do not dress it up. It evidences reliability, working under pressure, handling money, and dealing with people - all of which are genuinely relevant to almost every job. Write the responsibility and the conditions: opening or closing alone, training new starters, handling the till, covering the busiest shifts, working to a rota alongside full-time study. |
| Work in a family business | Experience, with the relationship stated rather than hidden. Concealing it is what creates the problem, not the work itself. | Name the business and what you did, and be plain that it is family. Nobody minds; what they mind is discovering it later. The strong version is specific and modest: which tasks were actually yours, how many hours a week alongside studying, over what period, and anything you can point at as a result - stock system you set up, accounts you kept, customers you handled directly. |
| Freelance or paid one-off work | Experience, grouped under a single Freelance heading with your own name or a trading name, rather than scattered as separate jobs. | One heading, then bullets across the clients rather than an entry per client. Describe the kind of work and its scale, keep client names out unless you have permission, and be accurate about what a job was: a small paid piece of work is a small paid piece of work, and calling it a client engagement when it was a favour with a fee is the kind of inflation that unravels in conversation. |
| Open-source contributions | Projects, or its own Open Source section if you have a sustained record. Link the profile or repository once, in your contact line. | Say what the project is and what your contribution actually was, at its real size. A merged fix to a documented issue is a merged fix, and it is worth writing. Claiming a contributor role on a project you opened one issue against is not. Where the work is visible and public, the link does most of the persuading, so keep the words short and let it be checked. |
Read the third column as one habit rather than eight rules: after you write any line, ask whether a stranger could tell from it what you were responsible for, how big it was, and how it ended. If any of those three is missing, the line is a label rather than a record, and labels are what make a student resume feel empty even when the student is not.
How do I lay out a resume when I have no jobs to list?
Lead with education, and let the strength of what follows decide the rest of the order. A student resume that opens with Education is not making excuses; it is putting the most relevant and most current thing first, which is what a resume is supposed to do. A workable order for most students is contact details, then Education, then Projects, then Experience, then Skills, then Leadership and Activities — and if your paid work is genuinely more relevant to the job than your projects, swap those two.
Harvard's Mignone Center for Career Success, whose guide to creating a strong resume was read live on the review date, puts the ordering question the same way: list headings such as Experience "in order of importance", and within each heading list entries "in reverse chronological order (most recent first)". It also asks for language that is "specific rather than general", "active rather than passive", and "written for people who / systems that scan quickly" — which is a useful way to hold both audiences in mind at once without designing for either at the expense of the other.
Two details worth getting right, because they cost nothing. Contact details belong in the body of the document rather than in a Word header, since in many configurations parsers read header and footer content unreliably or not at all. And section headings work best as plain words — Education, Experience, Projects, Skills — because those are the labels parsers are most often looking for. The full ruleset for that side of the problem lives in how to build an ATS-friendly resume format, and which resume format to choose covers the reverse-chronological question properly. Neither is repeated here.
On GPA: include it if it is strong for your field, leave it off if it is not, and do not agonise. Harvard's optional-category examples show a GPA sitting on the degree line, so including it is an ordinary formatting choice rather than a risk. Skills sit best near the bottom as a short, honest list of things you would be happy to be questioned about — a long list of everything you have ever opened is worse than a short list you can defend.
And when the posting itself demands years of experience you do not have — which will happen constantly, including on roles labelled entry-level — that is a separate question with its own answer. Why entry-level jobs ask for years of experience, and how to apply anyway works through what honestly counts toward a years figure, what number to put in the application form, and which of those postings are worth your time. It is answered properly there rather than summarised here.
Does a student resume have to be one page?
It does not have to be, and it usually ends up being one anyway, which is a more useful way to hold the question. The single page is a convention rather than a rule, and the convention exists for a practical reason: most students do not yet have more than a page of material that is genuinely worth reading, and the alternative to a tight single page is not a richer two pages but a thin two pages. Thin is the thing that reads badly. Length is not.
So treat the page count as an outcome. Write every entry that earns its place, describe each one specifically, then cut anything that is there to fill space — the interests line that lists generic hobbies, the objective that says you are a hard-working team player, the skills that are really familiarity. What is left is your resume, and its length is whatever it is. A dense, specific single page is a good student resume. A page and a bit carried by real research or substantial project work is not a problem either.
One caveat on formats, because it interacts with length: academic CVs for research and graduate applications follow different conventions and are expected to run longer. If you are applying for a job or an internship, you are writing a resume and the advice above applies. If you are applying to a research programme, check what that programme asks for, because the two documents are not interchangeable.
Should I put an objective or a summary at the top?
Skip the objective, and write a short summary only if you have something specific to say. The distinction matters. An objective describes what you want — "seeking a role where I can grow and apply my skills" — and it spends the most valuable space on the page telling the reader something they already assumed. A summary describes what you are and what you have done, which is information they do not have yet. If your summary would be generic adjectives, delete it and let Education start the page. Nothing is lost.
A summary earns its space when it does one of two jobs: naming a specialisation that is not obvious from your degree title, or explaining a pivot. A history student applying to data roles has something to explain in one line. A computer science student applying to software roles does not, and their summary would just restate the top of their own resume back to the reader.
Illustration only — a shape, not a real person
Fill in the brackets with your own details. This is a structural pattern, not a sentence to copy, and the person implied by it does not exist:
[Final-year degree subject] student specialising in [the narrow thing you actually work on], with [the strongest concrete thing you have done, named in five words]. Looking for [the specific kind of role], [availability or start date].
Notice what the shape forces you to do. It has no room for adjectives about your character, it requires you to name a specialisation rather than a degree, and it makes you commit to one concrete thing you have built or done. If you cannot fill the middle bracket, that is a signal about the resume rather than about the summary — and the fix is in the projects section, not in this paragraph.
Where an objective genuinely helps is the narrow case of a career change or a first application into an unrelated field, where the reader would otherwise wonder why you are applying. Even then, one line is enough, and it should read as an explanation rather than as an aspiration.
What should I not put on a student resume?
Anything you would not want to be asked about in detail. That is the whole test, and it is a more useful one than any list of banned words, because padding does not usually fail on the page — it fails in the room. An inflated line gets you the interview and then becomes the question you have to answer, and the moment between being asked and realising you cannot answer is a worse outcome than never having been asked. This is self-interest rather than principle.
The specific temptations are predictable, and each one has an honest version that is usually stronger anyway:
Turning a group project into sole authorship
Why it backfires: The interviewer asks how you built it, and the parts you did not build are the parts you cannot describe. That gap is obvious within a couple of follow-up questions and it is far more damaging than a smaller honest claim.
Honest version: Name the project, then name your part. Group work with a clearly stated contribution reads as experience and as self-awareness at the same time.
Listing every technology you have ever touched as a skill
Why it backfires: A skills list is read as a list of things you can be asked about. Anything on it that you used once for an afternoon is a trap you set for yourself.
Honest version: Keep the list to things you would be comfortable being questioned on, and let the projects section carry the rest by showing where each one was used.
Stretching dates to close a gap
Why it backfires: Dates are among the few things on a resume that get checked directly, and a small stretch is indistinguishable from a large one once it is found.
Honest version: Use accurate month and year, and let short gaps be short gaps. As a student, a gap needs no explanation at all - you were studying.
Calling a class assignment a client engagement
Why it backfires: The vocabulary of professional work applied to academic work reads as inflation to anyone who has done both, and it invites questions about a client who does not exist.
Honest version: Say it was a course project and then make the description strong enough that the label stops mattering. Specific work described plainly beats vague work described grandly.
Inflating a title you gave yourself
Why it backfires: Founder, lead, or manager attached to something with no scope behind it invites the scope question immediately, and the honest answer then sounds like a retreat.
Honest version: Use the plainest accurate title and put the scope in the bullets. Scope is what carries weight, and it survives questioning because it is true.
There is a quieter version of padding that is worth naming separately, because it does not feel like exaggeration: writing thin material in impressive-sounding language. Spearheaded, leveraged, results-driven and their relatives are how a sentence signals that it has nothing specific in it, and they read the same way whether a student or a language model produced them. The words that make a resume sound AI-written goes through the specific tells and what to write instead. Harvard's own guidance makes the same point about generative tools directly, saying that AI "should not be the primary author — not least because its output will likely be very generic".
One last pointer, for a different stage of this. If you already have a resume you are reasonably happy with, you have been sending it out, and nothing is coming back, that is not a writing problem any more and it needs a different diagnosis. Why junior developers are not getting interviews works through where those applications actually break — parsing, recruiter search, targeting — and it answers that question properly rather than restating this one.
Where can I get a free resume template as a student?
From a university, in almost every case, and the ordering below is deliberate. Institution-published templates are free, plain, maintained by people whose job is student employment, and free of the sidebars and graphics that make designed templates parse unpredictably in many configurations. They are also the least commercially motivated source you will find, which on this particular subject is worth something.
Harvard's free bullet-point template
Harvard FAS Mignone Center for Career Success publishes a bullet-point resume template openly on its site, and the page was live and readable when this article was reviewed. It is offered as a Word document, as an accessible Word document, and as a Google Docs version, with the instruction to use it to build out the first draft of your resume. A paragraph-format template sits alongside it. If you want the analysis of what that format gets right and where circulating copies of it run into trouble, our breakdown of the Harvard resume template covers it, and it is worth reading before you commit to any heavily formatted version of it.
Your own university career centre
This is usually the best-fit option and the most overlooked one. Your careers service almost certainly publishes a template, a guide, and worked examples, and they have an advantage no general-purpose template can match: they are written for the employers who actually recruit at your institution, in your country, in your field. They also normally come with a human who will read your draft. If you are choosing between a template from a resume site and one from your own careers service, take the careers service one.
Plain disclosure about our own templates
ResumeAI publishes free Word starters too, and they are indexed on our resume templates page — but every one of them is a developer role, so they are genuinely useful to a computer science student and no use at all to a nursing, education, or business student. They cover frontend, backend, full stack, mobile, data engineering, machine learning engineering, DevOps and site reliability, and junior developer. That is the whole set. If you are not studying something adjacent to those, the two sources above are your answer and this one is not.
They are single-column Word documents with plain headings, intended as a starting structure rather than a design. We are also the publisher of this page, which is why our own option is listed third rather than first.
Once you have something on the page
A template gives you a structure and nothing else, so the harder half is still in front of you. If you want help turning what you have done into bullets, our free resume builder is built for exactly the translation this page describes, and our free ATS resume checker will tell you whether a machine can read your education, dates and skills back out of the file you produced — which is a concrete, checkable question rather than a matter of taste, and a useful one to settle before you send a document you built from a template you did not test.
How we know this, and what we did not verify
This article was written by Pukar Khanal, Product Lead at ResumeAI, and last reviewed on . ResumeAI is the free Resume AI platform that builds your resume and matches you to real jobs across the hidden job market. What we can speak to first-hand is the mechanical half of this page: how a resume file is parsed into fields, how section headings and contact placement affect what survives that process, and how resume text is scored and matched against job descriptions. That comes from building and operating those systems, not from reading about them.
Everything attributed to Harvard here was re-read live on the review date before it was quoted. Both Mignone Center for Career Success pages linked above returned successfully and were read in full, and the wording quoted from them is their wording. The Harvard template files themselves were not opened, so nothing on this page describes their internal construction.
What we did not verify, stated plainly. We attempted several other student-focused career and writing resources on the review date and none of them were usable: one government careers resource refused the request, one university careers page returned a security rejection notice instead of its content, and three university writing and careers paths no longer exist at the addresses they are widely cited under. Not one sentence here draws on any of them. No university guidance is reconstructed from memory — either it was read on the review date and linked, or it is not on this page.
There are no statistics anywhere in this article. No figure for how long anyone spends reading a resume, no share of students who do anything, no response rates. The claim about recruiters spending a fixed handful of moments on each resume is the most quoted line in this entire subject area and it does not appear here in any form, because we could not trace it to something we could check. The only numbers on this page are dates and the reading time.
No student on this page is a real person. There are no success stories, no named examples, and no anecdotes presented as things that happened. The one illustrative summary in the objective section is labelled as an illustration and written entirely in brackets for exactly this reason. If you read a resume guide that tells you about a specific student who did well after following its advice, treat that story as marketing unless it is evidenced.
Parser behaviour is described as tendency, never as law. Applicant tracking systems are many different products with many different configurations, and the sentences here about headers, headings and layout are hedged deliberately. They describe what often happens and what is safer to assume, not what always happens.
And the templates are ours, and narrow. The Word starters this page mentions are published by us, they are developer-role documents, and we have said so in the same paragraph that recommends them rather than in a footnote. Harvard and your own careers service are listed above them because for most students they are the better answer, and we would rather be useful than first.
Frequently asked questions
What do you put on a resume with no experience?
Put your education first, then the things you have actually done: coursework and capstone projects, personal projects, volunteering, clubs and societies, sports teams, part-time work of any kind, family business work, freelance jobs, and open-source contributions. Every one of those is legitimate resume content. The reason they often feel like they do not count is that students tend to list them as interests rather than describing them as work. A recruiter is not looking for the word employer. They are looking for evidence that you took responsibility for something, did specific work, and it went somewhere. Coursework where you built a thing and it worked meets that bar. A hobby list does not, and the difference is entirely in how you write it.
What if I have literally never had a job?
Then your resume leads with education and is carried by projects, coursework, and unpaid or informal work, and that is a normal shape for a student resume rather than a broken one. Employers hiring interns and new graduates already expect this, because a first job is by definition applied for by somebody who has not had one. What matters is that the page is specific. Naming a course you took is weak. Naming what you built in that course, what it had to do, what you did yourself, and how it turned out is strong. If you have genuinely nothing on the page yet, the fastest fix is not more searching for tips but doing one small, finishable thing you can describe concretely, such as a project you complete and publish, or a few weeks of volunteering with a defined role.
Should I put my GPA on a student resume?
Include it if it is strong for your field, and leave it off if it is not, because nothing requires you to publish it. Harvard's own resume guidance, which was read on the review date, shows a GPA sitting on the degree line in its optional-category examples, so including it is a normal and accepted format rather than a risk. What you should not do is present it in a way designed to mislead, such as quoting a major-only average without saying that is what it is, or rounding upward. That kind of detail is the sort of thing that gets checked, and being caught trimming a number costs more than a mediocre number ever would. If you leave it off, use the space for something you can talk about.
How do I write about a class project on a resume?
Write it the way you would write a job: what your role was, how big the thing was, what you specifically did, and what came out of it. A weak version names the course and the assignment title. A strong version says what the system or paper or study had to accomplish, which part of it was yours, what you used to build it, and what state it reached - shipped, demonstrated, submitted, adopted by the class, published to a public repository. Put it under a Projects or Academic Projects heading rather than under Experience, so nobody thinks you are claiming employment, and be scrupulously honest about the boundary between what the group did and what you did. That boundary is exactly what an interviewer will probe.
Are there free resume templates for students?
Yes, and the best ones are published by universities rather than sold by resume sites. Harvard's Mignone Center for Career Success publishes a free bullet-point resume template in Word, an accessible Word version, and a Google Docs version, and it was live on the review date. Your own university career centre almost certainly publishes one too, and it has an advantage nothing else does: it is written for the employers who recruit at your school. ResumeAI also publishes free Word starters, but they are developer-role templates, so they suit a computer science student and they will not suit a nursing or education student. Whatever you use, avoid heavily designed templates with sidebars and graphics, because in many configurations those layouts parse unpredictably.
Should a student resume be one page?
One page is the normal shape for a student resume, and density is the reason rather than any rule. The convention exists because most students genuinely do not yet have more than a page of substantial material, and stretching thin material across two pages is more visible than keeping it tight. So treat the page count as an outcome rather than a target: write everything that is genuinely worth reading, cut what is filler, and see where you land. If the result is a full, specific single page, that is a good student resume. If it runs slightly over because you have real research, publications, or substantial project work, that is not a disaster either. What reads badly is padding, not length.
How do I list volunteer work on a resume?
List it like work, because it is work - the only thing missing is payment, and nobody objects to that. Give it a section of its own if you have several entries, or fold it into your Experience section if it was substantial and sustained, and in either case write it with a role name, the organisation, the dates, and bullets describing what you actually did. Volunteering that involved responsibility for something, coordination of other people, or a recurring commitment over months is genuinely strong material, and it is often the most convincing evidence a student resume carries that they show up reliably. A single afternoon at an event is thinner, and it is better placed as a line in an activities section than dressed up as a role.
What to ask next
If you arrived here from a generative-search prompt, these are the natural follow-ups — each links to the page that resolves it.
- The job says entry-level and wants years of experience. Should I apply anyway?
- What resume format actually survives an applicant tracking system?
- Is the Harvard resume template a good starting point for a student?
- I have a resume and nobody is replying. Where is it breaking?
- How do I get my first application past an ATS at all?
Nothing on the page yet? Start with what you have already done
You do not need a job history to build a resume worth sending. Bring the coursework, the project, the volunteering and the part-time shifts, and turn them into lines that read as work. Then check that a machine can read the file back. Both are free, and neither needs experience you do not have.
Continue Reading
How Does Greenhouse Read Your Resume? (2026 Job-Seeker Guide)
Greenhouse parses your resume into a searchable structured profile, then humans score you against a per-job scorecard — and it usually keeps your original PDF visible. Why it's more forgiving than Workday, and the format that wins.
Read moreHow Does Lever Read Your Resume? (2026 Job-Seeker Guide)
Lever (LeverTRM) parses your resume into a searchable candidate profile, full-text indexes it for recruiter search, and ranks — it doesn't mostly auto-reject, and recruiters can still view your file. The mechanism, the sourcing angle, and the single-column format that wins.
Read moreGoogle Docs Resume Templates: Which Ones Survive an ATS
Google Docs is a word processor rather than a layout canvas, which makes it a safer starting point than a design tool: its documents are text-first by default, and a plain single-column file exported with a live text layer generally parses fine. The risk sits somewhere narrower and less discussed — templates that use a table to line the page up, contact details typed into the header region where they can be treated as page furniture, and above all the export step, where a PDF, a Word file, a shared link and a scan hand a parser four completely different things. A six-row decoder maps each export path onto what a parser actually receives, plus a copy-and-paste self-test for your own file.
Read more