How to List Personal and Class Projects on a Resume When You Have Little Experience

Include a project when it proves a relevant skill your paid work does not show. Choose the strongest one or two, name your own contribution, and describe the work and its outcome without inflating the result. If a project happened as part of a job or volunteer role, put it under that role unless it needs separate space to make its relevance clear.

A project earns space by proving something

A project belongs on your resume when it gives the reader useful evidence for the work you want to do. Its source matters less than what you did, how you did it, and whether that work connects to the role. A course assignment can show research or analysis. A personal project can show initiative and sustained practice. A volunteer project can show service delivery or coordination. A project at work can show ownership inside a real organization.

The useful question is not “Was this project impressive?” It is “What relevant ability can someone see here that they cannot already see elsewhere on this page?” A project that answers the question adds evidence. A project that repeats the same skill, without a stronger example or useful detail, adds length instead.

That is the best default for a resume with little paid experience: select projects for new evidence, not to fill a section. Do not turn every assignment into a credential. Do not hide paid, volunteer, caregiving, campus, or community responsibilities just because they were not called projects. A resume describes relevant experience, not only payroll history.

University career guidance supports this practical flexibility. James Madison University says a significant course project can explain skills and knowledge, and suggests placing it under a course-project heading, education, or experience. It also advises using a course name rather than a course number. James Madison University Career Center’s resume content guidance gives examples of project descriptions and broader experience categories, including volunteer work and academic experience.

The University of Pennsylvania Career Services page named in the research plan was unavailable to open during this review, so this article does not rely on it as a verified source. The recommendations below use the accessible JMU guidance as a structural reference and clearly labeled hypothetical examples as original illustrations, not evidence about real candidates.

Start with the job, not your project list

Read the job description before deciding which projects to include. Mark the tasks, tools, and skills that appear central to the role. Then look for a project that demonstrates one of those things in a concrete way. This keeps the resume focused on the reader’s question: can you do relevant work, and what evidence supports that claim?

Make a simple evidence map before drafting:

This map is a thinking aid, not a section that belongs on the resume. One project may support several requirements, but choose the most important one or two angles. If you describe every task, the entry becomes a compressed project diary. If you describe one relevant contribution and its context, the reader can understand why it is there.

Be selective even when your resume feels short. A weak project does not become useful because a page has white space. It can make the stronger evidence harder to find. If a project is relevant but underdeveloped, consider finishing, documenting, or revising it before listing it. Do not imply it is complete if it remains in progress.

A project does not need to be paid or launched to be worth including. It does need a clear connection to the work and enough detail to support the skill you claim. “Built an app” is a label. “Built a small inventory tracker as a course exercise, using spreadsheet formulas to flag low-stock items” gives the reader a task, context, and method. The second is easier to assess even if it had no users and produced no business result.

Compare class, personal, volunteer, and work projects

Different project types offer different kinds of evidence. They do not deserve equal weight by default. Choose the type that best shows the target skill, then place it where its context remains honest and clear.

Class projects: useful evidence, clearly labeled

A course project can show that you applied concepts to a task. It is especially useful when you have limited work history, when the course is relevant to the role, or when the deliverable shows a skill that your job history does not. Describe the assignment as coursework. Do not make a classroom simulation sound like a client engagement, commercial launch, or operational result.

Use the course title or subject, institution if helpful, and a date or term. Then describe your contribution. If it was a group assignment, say what you owned. “Worked on a marketing plan” hides the difference between conducting research, writing copy, building a budget, and presenting the plan. Name your part.

A class project may fit under Education when it is closely tied to a degree and there is only one relevant example. A separate “Selected Projects” or “Course Projects” section makes more sense when you have multiple examples worth scanning independently. JMU explicitly describes both options and recommends using the course name rather than its course number. Its project-placement guidance is specific to resume content advice; it does not mean that every student should add a projects section.

Personal projects: initiative with boundaries

A personal project can show that you pursued a skill outside a formal assignment. That is valuable only when the work itself is relevant and you can explain what you did. A practice website, a small data-cleaning exercise, a neighborhood newsletter, a language-learning resource, or a repaired device might all provide evidence for particular roles. The title alone proves little.

State whether the project was personal, independent, or self-directed. Do not imply that a hobby project had customers, sponsors, users, or organizational approval if it did not. If the work is public, a portfolio link can help a reader inspect it, but a link is optional. Keep the resume entry understandable without requiring a click.

Personal projects vary in completeness. “In progress” can be fair when the project is active and the current work is meaningful. Explain the stage if it changes how a reader should interpret the claim. For example, a prototype is not a deployed service; a draft guide is not a published guide; a sample analysis is not a client recommendation. Use the accurate noun.

Volunteer projects: experience is still experience

Volunteer work may belong in an experience section, a volunteer section, or a projects section depending on its shape. If you held an ongoing role with an organization, use the organization and role as the entry. Put the relevant project beneath it if that keeps the responsibility clear. If you completed a one-off project, a project entry may be easier to understand.

Describe what you contributed, not what the entire organization achieved. If a group organized a food drive, for example, do not claim you personally served every visitor or raised all the funds. State your part: coordinated sign-up shifts, designed an information sheet, tracked donated items, or scheduled collection times, if those actions are true. The fact that the work was unpaid does not make it less real, and it does not justify overstating it.

Work-based projects: usually keep them with the role

A project completed as part of a job usually belongs under that job. The employer and role explain the setting, authority, and responsibilities. A separate projects section can detach the achievement from that context and make the reader wonder whether it was paid work, freelance work, or a personal effort.

The strongest exception is a project that deserves a short, distinct spotlight. For example, if one initiative directly matches the target role while the rest of the job was unrelated, a labeled “Selected Project” subheading under the job can make that contribution easier to see. A separate portfolio case study may also help when the work requires more context than the resume can hold. Keep the relationship to the employer clear, and do not disclose confidential information.

Choose a section heading that tells the truth

Use a heading that describes the work and helps the reader scan it. “Selected Projects” is a flexible option when the section includes course and personal work. “Course Projects” is clearer if everything listed came from school. “Volunteer Experience” is stronger when the work was a defined volunteer role rather than a collection of unrelated project assignments. “Relevant Projects” can work, but the label should not substitute for relevance; the entries still need to prove it.

Avoid a heading that implies a status you did not have. “Professional Experience” is a poor place for a class simulation unless the heading includes and clearly separates academic experience. “Client Projects” is inaccurate if no client asked for the work. “Product Launches” overstates a prototype or classroom presentation. A reader should not have to decode the section to figure out what kind of work happened.

A separate section is not mandatory. Put one course project under Education if that is the most natural place. Put work-based project bullets under the job. Create a distinct section when two or more projects have enough relevance to be useful as a group, or when one strong independent project would otherwise be buried. The best layout is the shortest one that preserves context and makes the evidence easy to find.

Build an entry from six facts

A useful project entry answers six questions: what was the project, when did it happen, where did it happen, what was your role, what did you do, and what came out of the work? Not every entry needs six separate lines. But you should know the answers before writing.

1. Name the project or deliverable. Use a descriptive title, not an inside joke or vague label. If the project has no formal title, create a plain one such as “Course Data Analysis” or “Community Event Scheduling Plan.”
2. Give the context. Identify the course, organization, team, or personal setting. Context tells the reader whether the work was academic, paid, volunteer, or independent.
3. Add a date or period. A term, month and year, or year can locate the work. Use a consistent format across the resume. For a long-running personal project, use the period that reflects substantial work, not a range that implies constant activity if you only touched it occasionally.
4. State your role. Say “individual project,” “team of four,” “volunteer coordinator,” or your actual role. If you had one defined responsibility inside a group, name that responsibility.
5. Describe the method or action. Show the work: compared, interviewed, drafted, coded, tested, organized, calculated, mapped, or presented. Pick verbs that match the actions you actually took.
6. Report the result or deliverable. Name what existed at the end: a report, prototype, plan, cleaned dataset, event schedule, presentation, or working demonstration. Include a measured result only when you have a sound basis and it is relevant.

A compact pattern is:

Project title | Context | Date

Action + method or tool + scope + deliverable or verified result.

For a group project, add your specific contribution before the team outcome. “As one of four students, analyzed survey responses and drafted the findings section for a course report” is more precise than “Led a team research project” if you did not lead the team. If you did lead a defined workstream, say so and describe its boundaries.

The JMU guidance recommends brief descriptions, strong action verbs, and quantification when possible for experience statements. The same Career Center page also uses project examples that identify the course, term, and work area. Treat quantification as an option, not a command to invent a number. A useful, verifiable scope detail is better than a decorative statistic.

Describe ownership without taking too much credit

Ownership is not the same as being the only person involved. It means making your part visible. In a group, say what you personally completed, decided, analyzed, designed, tested, documented, or presented. Then describe the shared deliverable without making it sound like your solo work.

Weak: “Created a full business plan for a start-up.”

Clearer, if accurate: “Built the market-research section for a four-person course business plan, comparing three customer segments and presenting the findings to the class.”

The second example distinguishes individual work from team work. It also avoids claiming that the hypothetical business launched, found customers, or earned revenue. Those results are absent because the example does not establish them.

Use verbs carefully. “Led” means you guided people or work, not merely that you participated. “Designed” means you made design decisions or produced a design, not just that you used a template. “Developed” can be broad, so follow it with what you actually developed. “Managed” needs something to manage: tasks, schedule, budget, people, or a process. If you were responsible for one piece, “owned the survey analysis” or “drafted the final section” can be stronger and more truthful than a grander title.

For a shared outcome, make the relationship explicit: “The team presented a prototype; I implemented the data-entry screen and wrote its setup notes.” Do not say “delivered a client solution” when the assignment was a classroom simulation. Do not say “improved retention” when you built a demo but did not observe users over time. A modest, accurate result is more credible than a large unsupported one.

When you cannot remember exactly who did what, check your files, notes, or group records before writing. If the division of labor remains unclear, use a broader but honest description, such as “contributed to the research and presentation,” and do not claim sole ownership. If you cannot defend a statement in an interview, revise it now.

Use numbers only when they clarify the work

Numbers can make scope concrete, but they are not automatically proof of impact. Include counts you can explain: number of interviews conducted, records analyzed, event shifts scheduled, pages drafted, or team members. State what the number measures. A number with no context is a decoration.

Separate three kinds of numbers:

• Scope: “Reviewed 24 survey responses.” This describes the amount of material handled.
• Output: “Produced a 10-page course report.” This describes what you made.
• Outcome: “Reduced average processing time by 15%.” This describes a change and needs a credible basis, such as a defined before-and-after measurement.

Do not turn scope into impact. An analysis of 24 responses does not prove that an organization changed its policy. A 10-page report does not prove that the recommendations were adopted. If a result was hypothetical, modeled, or forecast, label it that way. If it was observed but not measured systematically, use a qualitative description rather than an exact percentage.

There is no penalty for leaving out numbers when the project did not produce a meaningful measure. A clearly named deliverable and method can carry the entry. If a number requires a long explanation to avoid misleading the reader, it may not belong on the resume.

Choose the right level of detail

A project entry should be easy to scan, but it should not be so compressed that the reader cannot tell what happened. For most early-career resumes, one or two bullets per project are enough. Give the project a title and context, then spend the bullet on the most relevant contribution. More bullets are justified when the project is substantial, the role calls for several distinct skills, and the extra details are not repetitive.

Compare these versions. They are hypothetical and do not describe a real candidate:

Too vague

Campus sustainability project

This tells the reader almost nothing about the task, role, method, or result.

Too broad

Led a major campus sustainability initiative that transformed waste management, increased awareness, and delivered lasting environmental impact.

This version makes large claims without identifying the work or supporting the outcomes. It uses “led” and “transformed” as substitutes for evidence.

More useful, if accurate

Waste-Sorting Signage Review | Environmental Studies course | Spring 2026

Compared signage at three campus recycling stations, recorded visible label differences, and presented a redesign proposal as part of a four-person class project.

This entry identifies the setting, timeframe, scope, individual activity, and deliverable. It does not claim the proposal was adopted or that recycling rates changed. If the hypothetical student also designed a tested prototype, they could state that. If not, they should not imply it.

A second hypothetical example for a personal project:

Local Bus Route Guide | Independent project | 2025

Organized publicly available route and stop information into a plain-language guide for personal practice; documented the source dates and update limits.

This example demonstrates organization and communication, not public adoption. If the guide was never shared, call it a personal project rather than saying it helped passengers. If route details can change, note the date in the work or portfolio and refresh it before showing it to an employer.

The aim is not to make every project sound consequential. It is to make the actual work legible. Readers can judge a modest but clear project. They cannot judge a dramatic claim with no visible support.

Write bullet points that show the work

A strong project bullet often combines an action, a method, and a deliverable. You can add scope or outcome if it is both true and useful. This is a drafting pattern, not a rigid formula.

• Action: What did you do? “Mapped,” “tested,” “drafted,” or “analyzed.”
• Method: How did you do it? Name a tool, source, process, or comparison when useful.
• Scope: How much or what part? Use a count or boundary if you can explain it.
• Deliverable: What did the work produce? A plan, report, prototype, event, or presentation.
• Outcome: What changed? Include only a verifiable result, not an assumed benefit.

Hypothetical examples, to adapt only when they describe your actual work:

• Course research: “Compared two public policy approaches using a stated set of criteria; summarized the trade-offs in a class presentation.”
• Data exercise: “Cleaned a practice dataset in a spreadsheet, documented duplicate and missing-value decisions, and produced a summary table for a course report.”
• Personal website: “Built a three-page portfolio site as an independent practice project, adding project descriptions and checking navigation across the pages.”
• Volunteer event: “Scheduled volunteer shifts for a neighborhood information event and prepared a one-page arrival guide for participants.”
• Team design task: “Created wireframes for the booking flow in a four-person class team and revised the screens after peer feedback.”
• Writing project: “Researched and drafted a short explainer for a student publication, using primary documents and linking claims to their sources.”

These examples are not templates for borrowed accomplishments. Replace their methods, numbers, setting, and deliverables with your own facts. If a bullet implies a result you cannot support, remove or narrow the result. If the action sounds interchangeable with any candidate’s, add a concrete detail about the work.

Put the project where its context is strongest

Placement affects how a reader interprets the same project. The right section preserves the relationship among the work, the organization, and your role.

Put a course project under Education when it is closely tied to study

If one project is the best evidence from your degree, place it beneath the relevant education entry. That keeps the academic context visible and avoids creating a one-item section that adds more heading than information. Name the course, term, or project clearly enough to distinguish it from a class title alone.

For example, a biology graduate applying to technical writing roles might include a project that required translating a technical topic into a clear report. The relevant evidence is not simply “Biology coursework.” It is the communication task, the audience, and the deliverable. JMU notes that relevant coursework can be useful when applying outside one’s major or when a course is specialized for the target field, and separately recommends describing significant course projects. JMU Career Center’s guidance supports those placement options.

Create a projects section when projects form a real group

Use a separate section when you have at least a couple of relevant projects, or one substantial independent project that would otherwise be hard to find. Order entries by relevance first if the resume is targeted to a specific opening; within a similarly relevant group, reverse date order is easy to follow. Do not keep a project near the top just because it is recent if it is weak evidence for the role.

A “Selected Projects” section can include coursework and personal work, but label each entry’s setting. If you mix types without context, the reader may assume all projects were completed in the same professional capacity. A heading should make scanning easier, not flatten meaningful differences.

Keep work projects under the job that gave them context

When the project was part of a job, describe it beneath the employer and role. That makes your employment relationship explicit and lets the project support the wider experience entry. If it deserves a distinct label, use a subheading such as “Selected Project” without detaching it from the role.

The exception is not “the project sounds impressive.” It is “the project’s specific relevance would be lost among the role’s other responsibilities.” Even then, preserve the employer context and any confidentiality limits. Do not name a client, reveal private data, or publish internal results without authorization.

Treat volunteer work as experience, not a lesser category

A sustained volunteer role often belongs in Experience or Volunteer Experience. A one-time project can sit in a project section. Choose based on what the entry needs to explain: an ongoing role and organization, or a distinct deliverable and task. Either way, identify that it was volunteer work where the context could otherwise be misunderstood.

Decide whether to include a link

A link helps when it gives a reader access to a safe, relevant sample that supports the resume claim. It hurts when it is broken, private, confusing, or too broad. Link to the specific artifact or portfolio page if you can. Check it in a private browser window or while signed out, so you know whether an outside reader can open it.

Before linking, ask:

• Does the artifact show the skill named in the bullet?
• Can a reader understand what the work is without an explanation from you?
• Have you removed private, sensitive, or third-party information?
• Does the link still work and go to the intended page?
• Does the artifact match the version you describe on the resume?

A link is not a substitute for an explanation. Some readers will never open it. Put the project’s purpose and your contribution in the resume itself. If the work is confidential or cannot be shared, describe it at a safe level without disclosing protected details. Do not make a public repository or portfolio a requirement for every kind of project.

Avoid five project-listing mistakes

Listing everything you have ever completed

A long list of unrelated assignments makes the reader do the selection work you should have done. Keep the projects that add distinctive evidence for the target role. Remove duplicates and weak examples, even if you spent a lot of time on them.

Calling participation leadership

Being part of a group is not the same as leading it. Use “led” only when you directed people, decisions, or a workstream. Otherwise, name your specific contribution. Clear ownership reads stronger than a title you cannot defend.

Giving a classroom exercise a commercial outcome

A simulated business plan is not a launched company. A mock interface is not a product used by customers. A modeled forecast is not revenue. Name the work as coursework, prototype, simulation, or model when that distinction matters.

Claiming team results as your own

If a result belonged to a team or organization, distinguish the shared result from your individual action. “Contributed to” is sometimes accurate, but it needs a specific object: contributed research, a design, an analysis, or a defined workstream. Avoid both extremes: claiming all the credit and hiding your contribution in a vague team statement.

Keeping stale, unfinished, or uncheckable work

Remove a project if you can no longer explain the tools or methods you used, if the link is broken, if the artifact exposes private information, or if the work no longer helps your application. Update a project that is still active. Label a meaningful work-in-progress honestly; otherwise, wait until there is a complete deliverable worth describing.

A practical selection and writing process

Use this sequence for each application. It will usually produce a tighter section than trying to write a generic projects inventory first.

1. Identify the job’s central requirements. Choose a few duties or capabilities that appear important, rather than collecting every phrase in the posting.
2. List candidate evidence. Include paid work, volunteer roles, coursework, student activities, personal projects, research, and other relevant responsibilities. Do not assume that only a formal project counts.
3. Find gaps in your current resume. Ask what the experience section, skills section, and education section already prove. A project should add something, not restate a claim in a different heading.
4. Rank candidate projects. Put the clearest, most relevant evidence first. Prefer completed work with a defined contribution over a project title with no visible result.
5. Choose placement. Keep work-based projects with the job, a single course project with Education, and a group of independent examples in a clearly labeled section.
6. Write the facts before the sales language. Record context, dates, your role, actions, methods, scope, and deliverable. Cross out anything you cannot confirm.
7. Draft one concise bullet. Start with the strongest truthful action. Explain the method or scope. Name a deliverable or measured outcome if relevant.
8. Check ownership and claims. Mark every “I,” “we,” and “team” implication. Verify that the sentence gives you no more credit than you earned.
9. Tailor and trim. Bring forward the evidence that answers this role’s needs. Cut redundant or weak projects.
10. Check the final document. Read the PDF or printed version at normal size. Confirm headings, dates, links, and bullets are easy to scan and do not split awkwardly across pages.

If the result feels thin, do not inflate it. Add the missing context or choose a stronger example. A small, honest project can be useful when the bullet reveals the work. A grand title cannot rescue an empty description.

Example: deciding between three projects

Imagine a hypothetical applicant seeking an entry-level operations assistant role. The applicant has a short retail job, a group course assignment, and a personal spreadsheet used to organize a community club’s event sign-ups. The descriptions below are illustrative only; they are not real accomplishments.

The job asks for accurate record handling, organization, and clear communication. The applicant’s retail role already shows customer service and routine cash handling. The course assignment involved a broad management presentation, but the applicant cannot identify a distinct contribution beyond attending team meetings. The club spreadsheet is personal work used with permission by a volunteer group, and the applicant can explain the fields and update process.

Which project should make the resume?

The spreadsheet project is the strongest candidate if the applicant can substantiate the work and the organization permitted its use. It potentially adds evidence of organizing information and maintaining a simple process. The course project may be omitted because it adds little beyond a generic team label. The retail job remains more important than either project if it provides stronger evidence of reliability or customer interaction.

A truthful hypothetical entry might read:

Event Sign-Up Tracker | Volunteer club support | 2025

Organized sign-up information in a shared spreadsheet and documented the update steps for event volunteers; used with the group’s permission.

This version does not say the tracker reduced errors, saved time, or improved attendance. Those claims would need actual evidence. If the tracker was never shared or used by volunteers, the entry must say it was a personal practice project instead. If the applicant merely entered data into someone else’s tracker, “organized” may overstate the contribution; a more accurate verb is needed.

The decision changes if the job is for a communications assistant. Then the applicant might prefer a writing sample or class presentation that shows audience-aware communication. The same project does not have one fixed resume value. Its value depends on what it proves for this application, and whether another entry proves it better.

Check the claims before you send the resume

Read each project entry as if an interviewer will ask, “What exactly did you do?” Prepare a plain answer. If you wrote “analyzed,” be ready to explain the material and method. If you wrote “tested,” explain what you tested and under what conditions. If you listed a result, explain how it was measured and who observed it.

Use a claim check:

If you cannot answer, revise the verb or narrow the claim. “Proposed a change” is not the same as “implemented a change.” “Presented findings” is not the same as “persuaded the organization.” “Created a prototype” is not the same as “launched a product.” Precision protects both the reader and your credibility.

Dates deserve the same care. Use the term, month, or year that reflects when the substantial work occurred. Do not extend a short project across several years just because the file remained on your computer. For work that is ongoing, use an “in progress” label only when it is genuinely active. An old project can remain relevant, but do not present it as recent practice if you have not used the skill since.

Keep project evidence readable on the page

Projects are often detail-heavy, so their formatting needs restraint. Use the same heading style, date alignment, bullet punctuation, and spacing as the rest of the resume. Put the project name where the eye finds it quickly. Keep context close to the title. Do not use a dense paragraph to squeeze in every tool and step.

A simple layout might be:

SELECTED PROJECTS

Course Data Summary | Introductory Statistics, North Valley College | Fall 2025

• Cleaned a practice dataset in a spreadsheet, documented missing-value decisions, and produced a summary table for a course report.

Community Information Sheet | Volunteer project | 2024

• Drafted a one-page event guide and revised it after feedback from the volunteer coordinator.

These are hypothetical examples. The sample college name and work are illustrative, not claims about an actual applicant. In your own document, use your real institution, context, and contribution. If the page is crowded, cut a weak item before shrinking type until the resume is hard to read.

Check the exported document, not only the editor. Look for a project heading stranded at the bottom of a page, bullets split in an unhelpful place, inconsistent date formats, and links that are too small or unclear. If you print to PDF from a browser, inspect the resulting PDF before sending it. Formatting is not evidence of skill, but poor formatting can make good evidence harder to find.

A resume builder can help you arrange sections, but it cannot decide whether a claim is true or a project is relevant. If you use the free resume editor, make the selection and wording yourself, then review the exported PDF. You can also compare layouts in the resume template gallery; choose a design that keeps project titles, context, and bullets easy to read rather than one that hides them in decorative elements.

When a project should stay off the resume

Leave a project out when it does not support the target role, duplicates stronger evidence, or cannot be described clearly. Also leave it out when you cannot verify your contribution, when the work exposes confidential information, or when you would need to imply outcomes that never happened to make it sound worthwhile.

A project can be meaningful to you and still be wrong for this resume. It may have taught you something, helped a friend, or taken months of effort. Those facts do not automatically make it useful evidence for this opening. Keep a master record for yourself if you want; select only the relevant pieces for the application.

Do not omit a strong project simply because it was unpaid, academic, small, or imperfect. A modest completed task can demonstrate a method, judgment, or deliverable. But do not keep a weak project just because it is the only one available. You can describe other genuine experience: customer service, caregiving, tutoring, student activities, community work, research, or responsibilities that show the same capabilities. The category is less important than the evidence.

The strongest exception to a separate projects section is a work or volunteer project that belongs inside a role. In that case, a distinct bullet under the role usually gives better context than a detached entry. A project section is a tool, not a badge of seriousness.

Frequently asked questions

How many projects should I list?

List as few as you need to show relevant evidence that the rest of the resume does not show. One strong project is better than five interchangeable assignments. There is no fixed number that works for every resume; the page space and the role’s needs set the practical limit.

Should I put projects above work experience?

Put projects above work experience only when they are the strongest, most relevant evidence for the role and your paid experience is less relevant. Otherwise, keep the established experience section prominent. The heading order should help a reader find your best evidence, not conceal your history.

Can I include an unfinished project?

Yes, if it is active and already demonstrates meaningful work. Label it as in progress and describe what exists now. Do not list future plans as completed results. If the current work is only an idea, wait until there is something concrete to describe.

Do personal projects count as experience?

They count as experience in the ordinary sense that they are work you have done, but they are not paid employment unless they were paid employment. Label the context accurately. A personal project can support a skill claim without being presented as a job.

What if I only contributed one small part to a group project?

Name that part. A bounded contribution can still demonstrate a useful skill. Avoid implying that you owned the whole deliverable. The reader needs to understand both the group result and your individual work.

Should I include a grade?

Usually include a grade only when it is specifically relevant or requested and you can state it accurately. A grade is not a substitute for describing the work. A clear project entry often tells the reader more about what you can do.

Choose evidence, then make it easy to see

When work experience is thin, projects can fill an evidence gap. They cannot turn practice into employment, a team result into a solo achievement, or a forecast into a measured outcome. Use the project that shows a relevant skill most clearly. Put it where its context remains obvious. Describe what you personally did, and stop at what you can defend.

Before you send the resume, compare the project section with the job description and remove anything that adds no new evidence. Then check the dates, ownership, links, and PDF. For a simple next step, open the resume template gallery, choose a readable layout, and draft the strongest project entry before adding the rest of the section.