A Projects Section for Non-Technical Roles

A projects section is a short list of specific pieces of work you did, each with a name, a one-line description of what it was, and one or two bullets about what you did and what came of it. It’s the most useful section on a resume for anyone whose best work doesn’t map neatly onto a job title — and it is not just for software developers. A teacher who redesigned a curriculum, a coordinator who ran an event, an analyst who built a reporting workflow all have projects worth their own space.

Who benefits most

People early in their careers. With one or two jobs to your name, a project is often the strongest evidence you have that you can execute something start to finish. A capstone, a student organization campaign, a freelance piece of work, a volunteer initiative — each shows initiative that a part-time job description doesn’t.

Career changers. The gap between your history and your target is usually bridged by things you’ve done outside a job title. A project section lets you put relevant work in front of the reader before they reach the unrelated employers, which is the same logic behind reordering sections in choosing the right resume format.

People whose employers don’t sound impressive. A small company nobody’s heard of undersells work that was genuinely substantial. Naming the project makes the work visible independently of the logo.

Anyone whose best work was a one-off. The cross-department initiative you ran in 2024 is buried as one bullet among nine in your current role. Promoted to its own entry, it gets read.

What counts as a project

Wider than most people assume:

Something you built or produced. A handbook, a training program, a report series, a website, a database, a curriculum, a filing system.
An event you ran. A conference, a fundraiser, a hiring fair, a community program. Events are projects with hard deadlines, which is a useful thing to have demonstrated.
A process you designed. A new intake workflow, a reconciliation procedure, an onboarding sequence.
Freelance or contract work. Especially if the client isn’t listed as an employer.
Substantial volunteer initiatives. Where the work, not the cause, is the point — see when volunteer work belongs on your resume for how to decide which section it goes in.
Academic work with real output. A thesis, a research project, a client-facing student consultancy.

What doesn’t count: things you consumed rather than made (courses taken, books read, conferences attended), vague ongoing interests, and work so small that describing it takes longer than doing it did.

How to write an entry

Three lines is the target shape:

Line 1: A plain name and a context tag. “Volunteer Onboarding Handbook — Riverside Food Bank, 2025.” Name the thing so it reads as a real object, and give the setting and year so a reader can place it.
Line 2: One bullet on what you did. Same rules as any experience bullet: lead with a verb, be specific. “Wrote and illustrated a 12-page handbook covering shift procedures and food safety basics.”
Line 3 (optional): One bullet on what came of it. “Now given to every new volunteer; cut the number of first-shift questions the coordinators fielded.”

That’s it. Two bullets maximum per project, three projects maximum in the section for most people. A projects section that runs longer than your experience section has become the resume, which is fine only if you deliberately chose that.

The bullet craft is identical to the rest of the page — action verb, specific object, real consequence — and the same honesty rules apply. If a project didn’t produce a measurable outcome, describe what it was and who used it rather than reaching for a number. How to quantify achievements without inventing numbers covers the alternatives.

Where to put it

Early-career: directly after education, before or instead of a thin experience section. If your projects are stronger than your jobs, they go first.

Mid-career: after experience and skills, near the bottom. Here the section is supporting evidence, not the main case.

Career changer: immediately after the summary, so the relevant work lands before the unrelated job history.

One placement warning: don’t run a projects section and repeat the same work as bullets inside your experience section. Pick one home for each project. Duplicated content makes a resume feel longer than it is and makes the reader wonder if you have less material than they thought — a version of the padding problem covered in what to cut from your resume first.

Naming, honesty, and links

Name the project the way you’d name it out loud, not with an internal code. “Atlas Phase 2” is invisible; “the customer database migration” is legible.

Be exact about your role. If you were one of four people on it, say so: “One of four organizers.” If you led it, say you led it. If you contributed a specific piece, name the piece. Overstating your share of a group project is the most common honesty failure in this section, and it’s also the easiest one to expose — an interviewer will ask what you personally did.

Don’t include work you can’t discuss. Confidential client work can be described generically (“a reporting overhaul for a regional healthcare client”) but if you can’t say anything meaningful about it, it isn’t earning its space.

Link only if the link works and helps. A live handbook, a published article, a public dashboard, a portfolio page — good, as long as it’s current and you’d be happy for a hiring manager to spend a minute there. Same rules as the resume header: every link must work, and dead links are worse than no links.

Tailoring the section

Projects are the easiest section to swap per application, because entries are self-contained. Keep every project you’ve ever done in your long source document and select the two or three that fit each posting — the workflow in keep a master resume. A resume for a data-heavy role leads with the reporting project; the same resume for a communications role leads with the handbook.

The test for whether a project belongs

Ask whether you could talk about it for five minutes with genuine interest, and whether that conversation would make an interviewer more likely to hire you. If both are yes, it belongs. If you’d have to reconstruct the details from memory before the interview, it’s probably too old or too small.

Projects work on a resume for the same reason accomplishments beat duties: they describe something that actually happened, with your fingerprints on it. Two well-chosen entries do more than a paragraph of self-description ever will.