Skip to content
RoleframeRoleframe

How to List a Capstone Project on Your Resume (With Examples)

Where a capstone project goes on your resume, how to format it under Experience or Education, and two worked examples with STAR bullets that pass ATS scans.

Larbi Sahli
· Founder, Roleframe
Updated · 10 min read
How to List a Capstone Project on Your Resume (With Examples)
On this page

List your capstone under Experience if it is your strongest qualification, which is usually the case when you have little or no work history. List it under Education if you already have internships or jobs to show. Both placements parse fine in an applicant tracking system (ATS). Format it like a job: a clear title, dates, the tools you used, and two to four bullets that lead with results.

Why your capstone counts as real experience

A capstone is the closest thing to a work sample most new grads have. You scoped a problem, worked with a team over months, hit deadlines, presented to stakeholders, and shipped something. That is exactly the behavior a hiring manager is trying to predict when they screen an entry-level candidate, and it is far more predictive than your course list.

Recruiters know this. When a resume has no internships, the first thing a screener looks for is evidence you can do the actual work, and a well-described capstone provides it. The mistake students make is burying it as a one-line mention under their degree ("Completed senior capstone project") instead of describing it the way they would describe a job.

The rule: if the capstone is relevant to the role you are applying for, it earns real estate on your resume. If it is not relevant, a one-line mention under your degree is enough, or cut it entirely.

Where should a capstone project go on your resume?

There are three legitimate placements, and the right one depends on what else is on the page.

  • Under Experience, formatted like a job entry: choose this when you have zero or one relevant work entries. Label it honestly ("Capstone Project" or "Academic Project") so nobody feels misled, but give it the same structure as a job: title, organization, dates, bullets.
  • Under Education, as a sub-entry beneath your degree: choose this when you have internships or jobs that should own the Experience section. The capstone still gets two or three bullets, just lower on the page.
  • In a dedicated Projects section: choose this when you have several strong projects (capstone plus personal or open-source work) and want them grouped. Place it directly below Experience for career changers and new grads, or below Education if your degree is the headline.

What you should not do is list the capstone in two places, or inflate it into a job with an employer name that does not exist. If the capstone was sponsored by a real company, name the company as the sponsor ("Capstone Project, sponsored by Acme Logistics"), which is accurate and reads well. Never list the sponsor as your employer.

Placement is really a question of section order, and the logic is the same one covered in our guide to the best resume section order for your experience level: whatever best proves you can do this job goes highest.

Formatting a capstone under the Experience section

Treat it structurally like a job entry so both the recruiter and the ATS read it correctly. The four lines you need:

  1. Title line: your role plus a descriptive project name, e.g. "Backend Developer, Capstone Project: Clinic Scheduling Platform". The role label matters because ATS keyword matching often weighs job titles.
  2. Organization line: your university and department, plus the sponsor company if there was one.
  3. Date range: use the same format as your other entries (e.g. "Aug 2024 – May 2025"). ATS parsers expect dates on every experience entry, and a missing date can flag the entry as malformed.
  4. Three to five bullets: outcomes first, tools and scope woven in. More than five and you are diluting; fewer than three and it looks thin next to real jobs.

The label is not optional. A screener who realizes mid-interview that your "experience" was coursework will trust nothing else on the page. "Capstone Project" in the title line costs you nothing and protects everything.

Formatting a capstone under the Education section

Under Education, the capstone becomes a sub-entry beneath your degree. Keep it tight: a bolded label, a one-line description, and two or three bullets for your strongest results.

B.S. Computer Science, University of Washington (2021 – 2025)

  • Capstone: Clinic Scheduling Platform (team of 4, sponsored by a regional health network)
  • Built the appointment-matching service in Python and PostgreSQL; cut simulated double-booking errors from 8% to under 1% in testing
  • Presented the final system to the sponsor's IT director; the sponsor adopted two of the team's schema recommendations

Resist the urge to pad the Education section with coursework lists around it. A focused capstone entry beats ten course titles, the same way a strong GPA beats a weak one (and if yours is borderline, see whether to put your GPA on your resume).

How to write STAR bullets for academic projects

STAR stands for Situation, Task, Action, Result. On a resume you compress it: the bullet leads with the action and the result, and the situation is implied by the entry header. The formula that works for academic projects is verb + what you built or did + tool or method + measurable outcome.

Academic projects have a specific weakness: students describe the assignment instead of their contribution. "Worked on a machine learning project for course credit" tells a recruiter nothing. Compare:

  • Weak: "Participated in a team capstone project involving data analysis."
  • Strong: "Cleaned and merged 3 public datasets (120K rows) in pandas, then built a churn model that beat the baseline by 14 points of recall."
  • Weak: "Responsible for the frontend of the application."
  • Strong: "Built the React frontend (12 components, TypeScript) and cut page load time 40% by lazy-loading the reporting dashboard."

Where do numbers come from when nothing was "real"? Scope and measurement. Rows of data processed, test coverage, users in your pilot, load-time improvements, error rates before and after, the size of your team, the number of stakeholder demos. Academic projects generate real numbers constantly; students just don't think to write them down. If you genuinely have none, quantify scope ("across 6 hospital departments") rather than inventing impact.

One more habit worth stealing from experienced candidates: every bullet should answer "so what?" If a bullet ends at the action ("built an API"), append the consequence ("that served 3 downstream team features").

Highlighting teamwork, leadership, and your tech stack

Most capstones are group projects, and that is an asset, not a problem to hide. Entry-level job postings ask for collaboration and communication constantly, and a group capstone is your proof. Three ways to make it count:

A collaborative team of young professionals brainstorms over diagrams and devices in a bright, modern workspace.
  • Name your role and the team size in the header or first bullet ("team of 5, owned the data pipeline"). This tells the reader exactly what to credit you for and preempts the "but was it really you?" question.
  • Claim leadership specifically, not vaguely. "Led the team" is weak if you were one of four equals. "Ran weekly sprint planning for a 4-person team and coordinated the sponsor demo" is credible and checkable.
  • Put the tech stack where machines and humans both find it. Weave tools into the bullets (that is where an ATS keyword match against the posting happens) and mirror the most relevant ones in your skills section. If the job posting says PostgreSQL and your bullet says "SQL," fix the bullet.

That last point is where most capstone entries quietly fail. Recruiters filter on the exact terms from the posting, so the tools you name should match the tools they name. Our guide to ATS resume keywords covers how that matching actually works.

Example 1: software engineering capstone (Experience section)

Full-Stack Developer, Capstone Project: Campus Event Discovery App

University of Texas at Austin, Department of Computer Science | Jan 2025 – May 2025

  • Built a React Native app with a Node.js/Express backend that let students filter 200+ weekly campus events; 340 students installed it during the 6-week pilot
  • Designed the PostgreSQL schema and REST API (14 endpoints); wrote integration tests that held coverage above 80% through three feature releases
  • Ran the team's Git workflow (feature branches, PR reviews) for 4 developers, cutting merge conflicts to near zero after week two
  • Presented architecture and pilot results to a panel of faculty and two industry engineers; graded top project in a cohort of 18 teams

Notes on why this works: the title names a role an ATS can match, every bullet has a number, the stack appears inside the bullets rather than in a naked tool list, and the group-work bullets name what this person specifically owned. If you have more projects like this, our guide on how to list coding projects on a resume shows how to stack them, and a linked GitHub repo makes every claim verifiable (see where to put your GitHub link).

Example 2: data analytics capstone (Education section)

B.S. Statistics, Purdue University | Aug 2021 – May 2025

  • Capstone: Retail Demand Forecasting (team of 3, sponsored by a regional grocery chain)
  • Cleaned and joined 18 months of point-of-sale data (2.1M transactions) in Python and SQL, resolving inconsistent SKU codes across 40 stores
  • Built a gradient-boosted forecasting model that reduced mean absolute error 22% versus the sponsor's existing spreadsheet method
  • Delivered a Tableau dashboard and a written recommendation memo; the sponsor's analytics lead requested the codebase for internal use

This version is deliberately shorter than Example 1 because it sits under Education, where the candidate presumably has internships filling the Experience section above it. The third bullet is the one that gets interviews: an external stakeholder valued the work enough to keep it. Always hunt for that kind of external validation in your own project, because it converts "student assignment" into "work someone used."

Test your capstone bullets against a real job posting

The placement question (Experience or Education?) often has a different answer per application. A posting that screams "hands-on Python" wants your capstone up top; a posting that emphasizes prior internships wants your internship leading. In Roleframe's resume editor, sections and entries are drag and drop, so moving the capstone between Experience and Education takes seconds and the exported PDF stays cleanly parseable either way. You are not fighting a rigid form builder to restructure the page per job.

The more useful check is the fit report. Duplicate your resume for a specific posting and Roleframe scores it against that job: which keywords from the posting your capstone bullets already cover, which are missing, and a concrete plan for what to rewrite. If the posting asks for "data pipelines" and your bullet says "merged datasets," the gap shows up before a recruiter's filter finds it. You make the edits yourself, with the assistant suggesting rewrites bullet by bullet, so every claim on the page stays yours to defend in the interview.

Frequently asked questions

Does a capstone project count as work experience?

Not literally, and you should never present it as employment. But it counts as relevant experience, which is what entry-level screening actually looks for. Label it clearly as a capstone or academic project, format it with the structure of a job entry, and recruiters will weigh it seriously. The honesty of the label is what makes the placement work.

Is a capstone like an internship?

It overlaps more than most students think: a real deliverable, deadlines, teamwork, and often a real external sponsor. What it lacks is an employer vouching for you and the messiness of a real workplace. On a resume, a sponsored capstone with measurable results sits close to an internship in credibility; an unsponsored class project sits a step below. If you have both, the internship leads and the capstone supports.

Does a capstone project count as a thesis?

No. A thesis is a research document defended academically; a capstone is an applied project, usually built for or with an outside stakeholder. On a resume the distinction matters because they sell different things: a thesis signals research depth and belongs under Education, while a capstone signals applied, job-like skills and can carry an Experience entry. If you did a thesis, list it under your degree with its title and one bullet on findings or methods.

Should I put my capstone on my resume if I already have work experience?

Only if it adds something your jobs do not. If your capstone used a technology the target role requires and your work history does not show it, keep the capstone as a short Education sub-entry or in a Projects section. Once your work experience covers everything the capstone proves, cut it. Most people should drop the capstone within two to three years of graduating.

How do I claim credit for a group capstone without overstating my role?

State the team size and your specific ownership in the same breath: "team of 5; owned the ETL pipeline and the sponsor demos." Then write bullets only about the parts you owned, in first-person-implied voice ("built," "designed," not "we built"). Interviewers will probe exactly these bullets, so the safest resume is one where every line is something you can whiteboard on request.

How many bullet points should a capstone entry have?

Three to five when it sits in your Experience section, two to three as an Education sub-entry. If you are trimming, keep the bullets with numbers and external validation and cut the ones that describe the assignment. The same logic applies to every entry on the page, and we break it down in how many bullet points per job on a resume.

Larbi Sahli
Written by
· Founder, Roleframe

Larbi is a self-taught software engineer and the founder of Roleframe. He built it after getting tired of rewriting his resume for every single application. Having built ATS software himself, he knew exactly what those filters do to resumes on the other side. He writes about what actually gets you past ATS and in front of recruiters, based on thousands of real job descriptions, not recycled advice.

Was this helpful?

Ready when you are

Send the tailored resume, not the generic one.

Paste a job posting and Roleframe tailors your resume for it in about a minute, so you apply while the role is still fresh.