11 min read
You've got solid work in a bootcamp repo, a freelance site, or a capstone no one outside your class has seen. Your Experience section is thin or silent on the tools this posting keeps repeating. That's when a projects section on your resume stops being optional and starts carrying the interview.
Recruiters don't need a novel. They need proof you can do the job before they spend twenty minutes on a phone screen. Before you add another bullet, check your resume for free against the posting you're targeting tonight. Parsers in Workday and Greenhouse read plain text first. Fancy layout won't save a projects block that reads like a hobby list.
This guide covers what belongs in a resume projects section, what to cut, and copy-paste shapes you can adapt for software, marketing, and pivot roles. You won't need a separate portfolio essay. You'll need two to four entries with titles, tools, and numbers a hiring manager can repeat back to their team.
Quick Wins
- Open one target posting and highlight three required skills your Experience section never mentions.
- Pick two projects that prove those skills and draft a title line plus three bullets each.
- Paste the job description into score your job match and confirm project keywords appear in plain text.
What is a projects section on a resume?
A projects section is a labeled block where you show work that proves skills when paid roles, internships, or education lines do not tell the full story. It can hold capstones, freelance builds, open-source contributions, volunteer tech work, case studies, and internal initiatives you led outside your formal job title.
I've screened stacks where the Experience tab looked empty and the Projects block got the candidate to a screen because it named React, SQL, and a shipped outcome in the first three lines. ATS tools index that text the same way they index job bullets. Humans read it when they're deciding whether you understand the role or just applied everywhere.
This is not a link dump to Behance with no context. It is not every class assignment from 2019. It is not a second copy of your job description when the project was just your day job with a new header.
Recruiter filter: If I cannot tell your role, the stack, and one result in ten seconds, the project does not belong on page one.
Pair the section with a tailored summary and a Skills block that uses the same language as the posting. Read how to write a resume with no experience when Projects is doing most of the heavy lifting on your file.
Step-by-step: build a projects section recruiters actually read
Step 1: Choose projects that answer the posting
Pull the job description into a doc. Circle nouns and verbs the employer repeats: stack names, customer types, deliverables. Your projects section should echo at least two of those per entry without stuffing keywords into a skills cloud.
Before: "Built various websites and apps using modern tools."
After: "E-commerce inventory dashboard | Personal build | Jan 2026 to Mar 2026" followed by bullets naming Next.js, PostgreSQL, and a concrete outcome.
Keep two to four entries for most candidates. Senior hires might need one strong side project when pivoting. New grads can run three if each shows a different skill the role needs.
Step 2: Format each entry for ATS parsers
Use a single-column layout. Header the block Projects or Selected Projects. Each project gets one title line, then bullets. No tables, icons, or progress bars parsers cannot read.
Title line pattern: Project name | Your role | Start Month Year to End Month Year. If ongoing, write "Present" once, not a blank end date.
File type matters when you upload to Workday. A clean DOCX or text-selectable PDF beats a Canva export where bullets live inside shapes. Same content, different parse result.
Step 3: Write bullets with tools, scope, and proof
Lead with what you built, name two to three tools, close with an outcome. Numbers can be users, time saved, error rate, revenue, or class grade only when you have nothing else and the role is entry level.
Software developer composite:
Before: "Worked on a team project for school."
After: "Led API design for a capstone scheduling app used by 120 campus tutors; cut double-bookings 18% using Node.js, Express, and PostgreSQL with Jest test coverage on core routes."
Marketing coordinator composite:
Before: "Ran social media for a local business."
After: "Freelance launch campaign for a regional bakery; grew Instagram engagement 34% in six weeks using Meta Ads Manager, Canva assets, and weekly UTM-tagged offers tracked in Google Analytics 4."
Copy-paste project entry templates
Technical project block:
"[Project Name] | [Role] | [Month Year] to [Month Year]
• Built [deliverable] with [Tool 1], [Tool 2], and [Tool 3] for [user or client type]
• Implemented [feature] that [measurable outcome]
• Deployed via [hosting or CI] with [testing or monitoring note]"
Non-technical project block:
"[Initiative Name] | [Role] | [Month Year] to [Month Year]
• Researched [audience or problem] and delivered [asset]
• Partnered with [stakeholder type] to [action] resulting in [metric]
• Presented findings to [audience size or role] using [tool]"
Step 4: Place the section where skimmers will see it
Entry-level and bootcamp grads: Projects often sits under Education or Skills, above unrelated part-time jobs. Career changers: put Projects before older unrelated Experience so the pivot story lands on page one. Tenured professionals: keep Projects after Experience unless you are proving a new stack for a promotion or internal transfer.
Do not bury proof on page two when the posting asks for portfolio work in the first screen. Recruiters in Greenhouse rarely scroll that far on a first pass.
Edge case: career change with unrelated job titles
When your last three roles are in retail and you're applying for business analysis, Projects carries your pivot. Title the project line with the function you're targeting: "Sales forecasting model | Independent study | Jun 2025 to Aug 2025." Bullets should sound like the new field, not like homework unless the role is explicitly entry level.
Trim retail bullets that do not transfer. One line on customer volume is enough. Spend the rest of the page on Excel models, SQL queries, or dashboards you can demo on a call.
Edge case: NDA or confidential client work
You can still list the project without naming the client. Write "Fortune 500 fintech client" or "Series B healthtech startup" and describe the problem class, stack, and outcome. Never paste proprietary metrics if your contract forbids it; use ranges or percentages approved by your manager.
If legal blocks even that, move the work into Skills with a neutral line in Experience: "Delivered analytics tooling under NDA; details available on request." Do not invent a fake company name.
Edge case: overlapping dates with full-time work
Side projects during employment are normal. List real months even when they overlap a job. Add "nights and weekends" only in the interview, not on the resume. Bullets should clarify scope: "Built MVP in 8 weeks while employed full time" is honest and shows bandwidth.
Parsers sometimes stack overlapping dates oddly in Workday. Keep one date per line, Month Year format, and avoid multi-column timelines that scramble import order.
Edge case: title mismatch between project and target role
Your project role can be "Contributor" or "Builder" when you had no formal title. Match language from the posting in the first bullet instead of inventing "CEO" on a solo repo. Hiring managers notice inflated titles fast.
Read resume keywords for ATS to align project bullets with how Lever and iCIMS index skill phrases, then mirror the same terms in your summary.
Common projects section mistakes
Listing every project you ever touched. Volume reads unfocused. Cut anything older than three years unless it is your only proof for a must-have skill. Fix: keep two to four entries tied to this week's posting.
Bullets with no numbers and no tools. "Collaborated on a group project" tells me nothing I can sell to a hiring manager. Fix: name the stack and one outcome per bullet.
Duplicating paid work under Projects. If it was your job, it belongs in Experience. A second header looks like padding and confuses parsers mapping employment dates.
Graphics and link-only portfolios. ATS does not click GitHub. Put the languages and frameworks in text. Save the repo link for humans after the screen.
Wrong section headers. Cute labels like "Cool Stuff I Built" fail keyword maps. Use Projects. Boring wins in automated screening.
Check your projects section before you submit
Upload the same PDF or DOCX you will send through Workday or Greenhouse. HireFlow flags formatting issues, thin keyword alignment, and sections parsers often skip. Fix project bullets first when the match score says skills are missing but you know you built them. They are probably buried in a link or image.
After the resume passes, draft a short cover letter that names one project outcome the posting cares about. Use the cover letter generator with the job text so paragraph two echoes the same proof line recruiters will see on page one.
You can also rebuild the file in the free resume builder if your old template uses tables that break every time you add a project block.
Your projects section should sell proof, not hobbies
- Pick two to four projects that mirror the posting's must-have skills.
- Format title lines and bullets so Workday and Greenhouse can read them as plain text.
- Place the block where skimmers see it first when experience is thin or you're pivoting.
A tight projects section on your resume is how you turn "maybe" into a screen when your job titles do not tell the whole story. Stop guessing whether parsers see your stack. Check your resume for free, fix one project bullet tonight, and submit with the same file you tested.
Continue reading
Frequently asked questions
Aim for two to four projects that directly support the role you are applying for. Each entry should have a clear title, your role, dates or duration, and three to four bullets with tools and outcomes. More than five projects usually dilutes the signal and pushes stronger experience off page one.
Yes when the project proves a skill the job posting asks for and your paid roles do not show it clearly. Side builds, open-source contributions, and freelance gigs belong here when they are recent and relevant. Drop hobby projects that do not map to the employer's stack or customer problem.
Entry-level and career-change candidates often place Projects directly under Skills or Education so recruiters see proof before employment history. Experienced hires can put Projects after Experience when the section backs a pivot or fills a gap. Use the plain header Projects or Selected Projects so parsers in Workday and Greenhouse recognize the block.
Yes for new grads and bootcamp alumni when the capstone used production-grade tools and produced a measurable outcome. Label it clearly as academic work, name the stack, and describe what you built in recruiter language. Move it lower or remove it once you have twelve months of paid experience in the same field.
ATS parsers rarely follow URLs, so the bullet text must stand alone. A clean https link on the line is fine for human reviewers. Do not hide keywords only inside image-based portfolio screenshots. Spell the technologies in plain text bullets so keyword search still finds them.